1 <!-- All security issues affecting OpenSSL since the release of:
8 <!-- The updated attribute should be the same as the first public issue,
9 unless an old entry was updated. -->
10 <security updated="20171102">
11 <issue public="20171207">
12 <impact severity="Moderate"/>
13 <cve name="2017-3737"/>
14 <affects base="1.0.2" version="1.0.2b"/>
15 <affects base="1.0.2" version="1.0.2c"/>
16 <affects base="1.0.2" version="1.0.2d"/>
17 <affects base="1.0.2" version="1.0.2e"/>
18 <affects base="1.0.2" version="1.0.2f"/>
19 <affects base="1.0.2" version="1.0.2g"/>
20 <affects base="1.0.2" version="1.0.2h"/>
21 <affects base="1.0.2" version="1.0.2i"/>
22 <affects base="1.0.2" version="1.0.2j"/>
23 <affects base="1.0.2" version="1.0.2k"/>
24 <affects base="1.0.2" version="1.0.2l"/>
25 <affects base="1.0.2" version="1.0.2m"/>
26 <fixed base="1.0.2" version="1.0.2n" date="20171207"/>
27 <problemtype>Unauthenticated read/unencrypted write</problemtype>
28 <title>Read/write after SSL object in error state</title>
30 OpenSSL 1.0.2 (starting from version 1.0.2b) introduced an "error state"
31 mechanism. The intent was that if a fatal error occurred during a handshake then
32 OpenSSL would move into the error state and would immediately fail if you
33 attempted to continue the handshake. This works as designed for the explicit
34 handshake functions (SSL_do_handshake(), SSL_accept() and SSL_connect()),
35 however due to a bug it does not work correctly if SSL_read() or SSL_write() is
36 called directly. In that scenario, if the handshake fails then a fatal error
37 will be returned in the initial function call. If SSL_read()/SSL_write() is
38 subsequently called by the application for the same SSL object then it will
39 succeed and the data is passed without being decrypted/encrypted directly from
40 the SSL/TLS record layer.
42 In order to exploit this issue an application bug would have to be present that
43 resulted in a call to SSL_read()/SSL_write() being issued after having already
44 received a fatal error.
46 <advisory url="/news/secadv/20171207.txt"/>
47 <reported source="David Benjamin (Google)"/>
49 <issue public="20171207">
50 <impact severity="Low"/>
51 <cve name="2017-3738"/>
52 <affects base="1.1.0" version="1.1.0"/>
53 <affects base="1.1.0" version="1.1.0a"/>
54 <affects base="1.1.0" version="1.1.0b"/>
55 <affects base="1.1.0" version="1.1.0c"/>
56 <affects base="1.1.0" version="1.1.0d"/>
57 <affects base="1.1.0" version="1.1.0e"/>
58 <affects base="1.1.0" version="1.1.0f"/>
59 <affects base="1.1.0" version="1.1.0g"/>
60 <affects base="1.0.2" version="1.0.2"/>
61 <affects base="1.0.2" version="1.0.2a"/>
62 <affects base="1.0.2" version="1.0.2b"/>
63 <affects base="1.0.2" version="1.0.2c"/>
64 <affects base="1.0.2" version="1.0.2d"/>
65 <affects base="1.0.2" version="1.0.2e"/>
66 <affects base="1.0.2" version="1.0.2f"/>
67 <affects base="1.0.2" version="1.0.2g"/>
68 <affects base="1.0.2" version="1.0.2h"/>
69 <affects base="1.0.2" version="1.0.2i"/>
70 <affects base="1.0.2" version="1.0.2j"/>
71 <affects base="1.0.2" version="1.0.2k"/>
72 <affects base="1.0.2" version="1.0.2l"/>
73 <affects base="1.0.2" version="1.0.2m"/>
74 <fixed base="1.0.2" version="1.0.2n" date="20171207"/>
75 <fixed base="1.1.0" version="1.1.0h-dev" date="20171207"/>
76 <problemtype>carry-propagating bug</problemtype>
77 <title>bn_sqrx8x_internal carry bug on x86_64</title>
79 There is an overflow bug in the AVX2 Montgomery multiplication procedure
80 used in exponentiation with 1024-bit moduli. No EC algorithms are affected.
81 Analysis suggests that attacks against RSA and DSA as a result of this defect
82 would be very difficult to perform and are not believed likely. Attacks
83 against DH1024 are considered just feasible, because most of the work
84 necessary to deduce information about a private key may be performed offline.
85 The amount of resources required for such an attack would be significant.
86 However, for an attack on TLS to be meaningful, the server would have to share
87 the DH1024 private key among multiple clients, which is no longer an option
90 This only affects processors that support the AVX2 but not ADX extensions
91 like Intel Haswell (4th generation).
93 Note: The impact from this issue is similar to CVE-2017-3736, CVE-2017-3732
96 Due to the low severity of this issue we are not issuing a new release of
97 OpenSSL 1.1.0 at this time. The fix will be included in OpenSSL 1.1.0h when it
98 becomes available. The fix is also available in commit e502cc86d in the OpenSSL
101 <advisory url="/news/secadv/20171207.txt"/>
102 <reported source="David Benjamin (Google)/Google OSS-Fuzz"/>
104 <issue public="20171102">
105 <impact severity="Moderate"/>
106 <cve name="2017-3736"/>
107 <affects base="1.1.0" version="1.1.0"/>
108 <affects base="1.1.0" version="1.1.0a"/>
109 <affects base="1.1.0" version="1.1.0b"/>
110 <affects base="1.1.0" version="1.1.0c"/>
111 <affects base="1.1.0" version="1.1.0d"/>
112 <affects base="1.1.0" version="1.1.0e"/>
113 <affects base="1.1.0" version="1.1.0f"/>
114 <affects base="1.0.2" version="1.0.2"/>
115 <affects base="1.0.2" version="1.0.2a"/>
116 <affects base="1.0.2" version="1.0.2b"/>
117 <affects base="1.0.2" version="1.0.2c"/>
118 <affects base="1.0.2" version="1.0.2d"/>
119 <affects base="1.0.2" version="1.0.2e"/>
120 <affects base="1.0.2" version="1.0.2f"/>
121 <affects base="1.0.2" version="1.0.2g"/>
122 <affects base="1.0.2" version="1.0.2h"/>
123 <affects base="1.0.2" version="1.0.2i"/>
124 <affects base="1.0.2" version="1.0.2j"/>
125 <affects base="1.0.2" version="1.0.2k"/>
126 <affects base="1.0.2" version="1.0.2l"/>
127 <fixed base="1.0.2" version="1.0.2m" date="20171102"/>
128 <fixed base="1.1.0" version="1.1.0g" date="20171102"/>
129 <problemtype>carry-propagating bug</problemtype>
130 <title>bn_sqrx8x_internal carry bug on x86_64</title>
132 There is a carry propagating bug in the x86_64 Montgomery squaring procedure. No
133 EC algorithms are affected. Analysis suggests that attacks against RSA and DSA
134 as a result of this defect would be very difficult to perform and are not
135 believed likely. Attacks against DH are considered just feasible (although very
136 difficult) because most of the work necessary to deduce information
137 about a private key may be performed offline. The amount of resources
138 required for such an attack would be very significant and likely only
139 accessible to a limited number of attackers. An attacker would
140 additionally need online access to an unpatched system using the target
141 private key in a scenario with persistent DH parameters and a private
142 key that is shared between multiple clients.
144 This only affects processors that support the BMI1, BMI2 and ADX extensions like
145 Intel Broadwell (5th generation) and later or AMD Ryzen.
147 <advisory url="/news/secadv/20171102.txt"/>
148 <reported source="Google OSS-Fuzz"/>
150 <issue public="20170828">
151 <impact severity="Low"/>
152 <cve name="2017-3735"/>
153 <affects base="1.1.0" version="1.1.0"/>
154 <affects base="1.1.0" version="1.1.0a"/>
155 <affects base="1.1.0" version="1.1.0b"/>
156 <affects base="1.1.0" version="1.1.0c"/>
157 <affects base="1.1.0" version="1.1.0d"/>
158 <affects base="1.1.0" version="1.1.0e"/>
159 <affects base="1.1.0" version="1.1.0f"/>
160 <affects base="1.0.2" version="1.0.2"/>
161 <affects base="1.0.2" version="1.0.2a"/>
162 <affects base="1.0.2" version="1.0.2b"/>
163 <affects base="1.0.2" version="1.0.2c"/>
164 <affects base="1.0.2" version="1.0.2d"/>
165 <affects base="1.0.2" version="1.0.2e"/>
166 <affects base="1.0.2" version="1.0.2f"/>
167 <affects base="1.0.2" version="1.0.2g"/>
168 <affects base="1.0.2" version="1.0.2h"/>
169 <affects base="1.0.2" version="1.0.2i"/>
170 <affects base="1.0.2" version="1.0.2j"/>
171 <affects base="1.0.2" version="1.0.2k"/>
172 <affects base="1.0.2" version="1.0.2l"/>
173 <fixed base="1.0.2" version="1.0.2m" date="20171102"/>
174 <fixed base="1.1.0" version="1.1.0g" date="20171102"/>
175 <problemtype>out-of-bounds read</problemtype>
176 <title>Possible Overread in parsing X.509 IPAdressFamily</title>
178 While parsing an IPAdressFamily extension in an X.509 certificate,
179 it is possible to do a one-byte overread. This would result in
180 an incorrect text display of the certificate.
182 <advisory url="/news/secadv/20170828.txt"/>
183 <reported source="Google OSS-Fuzz"/>
185 <issue public="20170216">
186 <impact severity="High"/>
187 <cve name="2017-3733"/>
188 <affects base="1.1.0" version="1.1.0"/>
189 <affects base="1.1.0" version="1.1.0a"/>
190 <affects base="1.1.0" version="1.1.0b"/>
191 <affects base="1.1.0" version="1.1.0c"/>
192 <affects base="1.1.0" version="1.1.0d"/>
193 <fixed base="1.1.0" version="1.1.0e" date="20170216"/>
194 <problemtype>protocol error</problemtype>
195 <title>Encrypt-Then-Mac renegotiation crash</title>
197 During a renegotiation handshake if the Encrypt-Then-Mac extension is
198 negotiated where it was not in the original handshake (or vice-versa) then
199 this can cause OpenSSL to crash (dependent on ciphersuite). Both clients
200 and servers are affected.
202 <advisory url="/news/secadv/20170216.txt"/>
203 <reported source="Joe Orton (Red Hat)" />
205 <issue public="20170126">
206 <impact severity="Moderate"/>
207 <cve name="2017-3731"/>
208 <affects base="1.1.0" version="1.1.0"/>
209 <affects base="1.1.0" version="1.1.0a"/>
210 <affects base="1.1.0" version="1.1.0b"/>
211 <affects base="1.1.0" version="1.1.0c"/>
212 <affects base="1.0.2" version="1.0.2"/>
213 <affects base="1.0.2" version="1.0.2a"/>
214 <affects base="1.0.2" version="1.0.2b"/>
215 <affects base="1.0.2" version="1.0.2c"/>
216 <affects base="1.0.2" version="1.0.2d"/>
217 <affects base="1.0.2" version="1.0.2e"/>
218 <affects base="1.0.2" version="1.0.2f"/>
219 <affects base="1.0.2" version="1.0.2g"/>
220 <affects base="1.0.2" version="1.0.2h"/>
221 <affects base="1.0.2" version="1.0.2i"/>
222 <affects base="1.0.2" version="1.0.2j"/>
223 <fixed base="1.1.0" version="1.1.0d" date="20170126"/>
224 <fixed base="1.0.2" version="1.0.2k" date="20170126"/>
225 <problemtype>out-of-bounds read</problemtype>
226 <title>Truncated packet could crash via OOB read</title>
228 If an SSL/TLS server or client is running on a 32-bit host, and a specific
229 cipher is being used, then a truncated packet can cause that server or
230 client to perform an out-of-bounds read, usually resulting in a crash.
232 For OpenSSL 1.1.0, the crash can be triggered when using
233 CHACHA20/POLY1305; users should upgrade to 1.1.0d.
235 For Openssl 1.0.2, the crash can be triggered when using RC4-MD5; users
236 who have not disabled that algorithm should update to 1.0.2k
238 <advisory url="/news/secadv/20170126.txt"/>
239 <reported source="Robert Święcki of Google" />
241 <issue public="20170126">
242 <impact severity="Moderate"/>
243 <cve name="2017-3730"/>
244 <affects base="1.1.0" version="1.1.0"/>
245 <affects base="1.1.0" version="1.1.0a"/>
246 <affects base="1.1.0" version="1.1.0b"/>
247 <affects base="1.1.0" version="1.1.0c"/>
248 <fixed base="1.1.0" version="1.1.0d" date="20170126"/>
249 <problemtype>NULL pointer deference</problemtype>
250 <title>Bad (EC)DHE parameters cause a client crash</title>
252 If a malicious server supplies bad parameters for a DHE or ECDHE key
253 exchange then this can result in the client attempting to dereference a
254 NULL pointer leading to a client crash. This could be exploited in a
255 Denial of Service attack.
257 <advisory url="/news/secadv/20170126.txt"/>
258 <reported source="Guido Vranken" />
260 <issue public="20170126">
261 <impact severity="Moderate"/>
262 <cve name="2017-3732"/>
263 <affects base="1.1.0" version="1.1.0"/>
264 <affects base="1.1.0" version="1.1.0a"/>
265 <affects base="1.1.0" version="1.1.0b"/>
266 <affects base="1.1.0" version="1.1.0c"/>
267 <affects base="1.0.2" version="1.0.2"/>
268 <affects base="1.0.2" version="1.0.2a"/>
269 <affects base="1.0.2" version="1.0.2b"/>
270 <affects base="1.0.2" version="1.0.2c"/>
271 <affects base="1.0.2" version="1.0.2d"/>
272 <affects base="1.0.2" version="1.0.2e"/>
273 <affects base="1.0.2" version="1.0.2f"/>
274 <affects base="1.0.2" version="1.0.2g"/>
275 <affects base="1.0.2" version="1.0.2h"/>
276 <affects base="1.0.2" version="1.0.2i"/>
277 <affects base="1.0.2" version="1.0.2j"/>
278 <fixed base="1.1.0" version="1.1.0d" date="20170126"/>
279 <fixed base="1.0.2" version="1.0.2k" date="20170126"/>
280 <problemtype>carry-propagating bug</problemtype>
281 <title>BN_mod_exp may produce incorrect results on x86_64</title>
283 There is a carry propagating bug in the x86_64 Montgomery squaring
284 procedure. No EC algorithms are affected. Analysis suggests that attacks
285 against RSA and DSA as a result of this defect would be very difficult to
286 perform and are not believed likely. Attacks against DH are considered
287 just feasible (although very difficult) because most of the work necessary
288 to deduce information about a private key may be performed offline. The
289 amount of resources required for such an attack would be very significant
290 and likely only accessible to a limited number of attackers. An attacker
291 would additionally need online access to an unpatched system using the
292 target private key in a scenario with persistent DH parameters and a
293 private key that is shared between multiple clients. For example this can
294 occur by default in OpenSSL DHE based SSL/TLS ciphersuites. Note: This
295 issue is very similar to CVE-2015-3193 but must be treated as a separate
298 <advisory url="/news/secadv/20170126.txt"/>
299 <reported source="OSS-Fuzz project" />
301 <issue public="20161110">
302 <impact severity="High"/>
303 <cve name="2016-7054"/>
304 <affects base="1.1.0" version="1.1.0"/>
305 <affects base="1.1.0" version="1.1.0a"/>
306 <affects base="1.1.0" version="1.1.0b"/>
307 <fixed base="1.1.0" version="1.1.0c" date="20161110"/>
308 <problemtype>protocol error</problemtype>
309 <title>ChaCha20/Poly1305 heap-buffer-overflow</title>
311 TLS connections using *-CHACHA20-POLY1305 ciphersuites are susceptible to
312 a DoS attack by corrupting larger payloads. This can result in an OpenSSL
313 crash. This issue is not considered to be exploitable beyond a DoS.
315 <advisory url="/news/secadv/20161110.txt"/>
316 <reported source="Robert Święcki (Google Security Team)" date="20160925"/>
318 <issue public="20161110">
319 <impact severity="Moderate"/>
320 <cve name="2016-7053"/>
321 <affects base="1.1.0" version="1.1.0"/>
322 <affects base="1.1.0" version="1.1.0a"/>
323 <affects base="1.1.0" version="1.1.0b"/>
324 <fixed base="1.1.0" version="1.1.0c" date="20161110"/>
325 <problemtype>NULL pointer deference</problemtype>
326 <title>CMS Null dereference</title>
328 Applications parsing invalid CMS structures can crash with a NULL pointer
329 dereference. This is caused by a bug in the handling of the ASN.1 CHOICE
330 type in OpenSSL 1.1.0 which can result in a NULL value being passed to the
331 structure callback if an attempt is made to free certain invalid
332 encodings. Only CHOICE structures using a callback which do not handle
333 NULL value are affected.
335 <advisory url="/news/secadv/20161110.txt"/>
336 <reported source="Tyler Nighswander (ForAllSecure)" date="20161012"/>
338 <issue public="20161110">
339 <impact severity="Low"/>
340 <cve name="2016-7055"/>
341 <affects base="1.1.0" version="1.1.0"/>
342 <affects base="1.1.0" version="1.1.0a"/>
343 <affects base="1.1.0" version="1.1.0b"/>
344 <affects base="1.0.2" version="1.0.2"/>
345 <affects base="1.0.2" version="1.0.2a"/>
346 <affects base="1.0.2" version="1.0.2b"/>
347 <affects base="1.0.2" version="1.0.2c"/>
348 <affects base="1.0.2" version="1.0.2d"/>
349 <affects base="1.0.2" version="1.0.2e"/>
350 <affects base="1.0.2" version="1.0.2f"/>
351 <affects base="1.0.2" version="1.0.2g"/>
352 <affects base="1.0.2" version="1.0.2h"/>
353 <affects base="1.0.2" version="1.0.2i"/>
354 <affects base="1.0.2" version="1.0.2j"/>
355 <fixed base="1.1.0" version="1.1.0c" date="20161110"/>
356 <fixed base="1.0.2" version="1.0.2k" date="20170126"/>
357 <problemtype>carry propagating bug</problemtype>
358 <title>Montgomery multiplication may produce incorrect results</title>
360 There is a carry propagating bug in the Broadwell-specific Montgomery
361 multiplication procedure that handles input lengths divisible by, but
362 longer than 256 bits. Analysis suggests that attacks against RSA, DSA
363 and DH private keys are impossible. This is because the subroutine in
364 question is not used in operations with the private key itself and an
365 input of the attacker's direct choice. Otherwise the bug can manifest
366 itself as transient authentication and key negotiation failures or
367 reproducible erroneous outcome of public-key operations with specially
368 crafted input. Among EC algorithms only Brainpool P-512 curves are
369 affected and one presumably can attack ECDH key negotiation. Impact was
370 not analyzed in detail, because pre-requisites for attack are considered
371 unlikely. Namely multiple clients have to choose the curve in question and
372 the server has to share the private key among them, neither of which is
373 default behaviour. Even then only clients that chose the curve will be
376 <advisory url="/news/secadv/20161110.txt"/>
377 <reported source="Publicly reported" />
379 <issue public="20160926">
380 <impact severity="Critical"/>
381 <cve name="2016-6309"/>
382 <affects base="1.1.0" version="1.1.0a"/>
383 <fixed base="1.1.0" version="1.1.0b" date="20160926"/>
385 <problemtype>write to free</problemtype>
387 This issue only affects OpenSSL 1.1.0a, released on 22nd September 2016.
389 The patch applied to address CVE-2016-6307 resulted in an issue where if a
390 message larger than approx 16k is received then the underlying buffer to store
391 the incoming message is reallocated and moved. Unfortunately a dangling pointer
392 to the old location is left which results in an attempt to write to the
393 previously freed location. This is likely to result in a crash, however it
394 could potentially lead to execution of arbitrary code.
396 <advisory url="/news/secadv/20160926.txt"/>
397 <reported source="Robert Święcki (Google Security Team)" date="20160923"/>
399 <issue public="20160926">
400 <impact severity="Moderate"/>
401 <cve name="2016-7052"/>
402 <affects base="1.0.2" version="1.0.2i"/>
403 <fixed base="1.0.2" version="1.0.2j" date="20160926"/>
405 <problemtype>NULL pointer exception</problemtype>
407 This issue only affects OpenSSL 1.0.2i, released on 22nd September 2016.
409 A bug fix which included a CRL sanity check was added to OpenSSL 1.1.0
410 but was omitted from OpenSSL 1.0.2i. As a result any attempt to use
411 CRLs in OpenSSL 1.0.2i will crash with a null pointer exception.
413 <advisory url="/news/secadv/20160926.txt"/>
414 <reported source="Bruce Stephens and Thomas Jakobi" date="20160922"/>
416 <issue public="20160922">
417 <impact severity="High"/>
418 <cve name="2016-6304"/>
419 <affects base="1.0.1" version="1.0.1"/>
420 <affects base="1.0.1" version="1.0.1a"/>
421 <affects base="1.0.1" version="1.0.1b"/>
422 <affects base="1.0.1" version="1.0.1c"/>
423 <affects base="1.0.1" version="1.0.1d"/>
424 <affects base="1.0.1" version="1.0.1e"/>
425 <affects base="1.0.1" version="1.0.1f"/>
426 <affects base="1.0.1" version="1.0.1g"/>
427 <affects base="1.0.1" version="1.0.1h"/>
428 <affects base="1.0.1" version="1.0.1i"/>
429 <affects base="1.0.1" version="1.0.1j"/>
430 <affects base="1.0.1" version="1.0.1k"/>
431 <affects base="1.0.1" version="1.0.1l"/>
432 <affects base="1.0.1" version="1.0.1m"/>
433 <affects base="1.0.1" version="1.0.1n"/>
434 <affects base="1.0.1" version="1.0.1o"/>
435 <affects base="1.0.1" version="1.0.1p"/>
436 <affects base="1.0.1" version="1.0.1q"/>
437 <affects base="1.0.1" version="1.0.1r"/>
438 <affects base="1.0.1" version="1.0.1s"/>
439 <affects base="1.0.1" version="1.0.1t"/>
440 <affects base="1.0.2" version="1.0.2"/>
441 <affects base="1.0.2" version="1.0.2a"/>
442 <affects base="1.0.2" version="1.0.2b"/>
443 <affects base="1.0.2" version="1.0.2c"/>
444 <affects base="1.0.2" version="1.0.2d"/>
445 <affects base="1.0.2" version="1.0.2e"/>
446 <affects base="1.0.2" version="1.0.2f"/>
447 <affects base="1.0.2" version="1.0.2g"/>
448 <affects base="1.0.2" version="1.0.2h"/>
449 <affects base="1.1.0" version="1.1.0"/>
450 <fixed base="1.0.1" version="1.0.1u" date="20160922"/>
451 <fixed base="1.0.2" version="1.0.2i" date="20160922"/>
452 <fixed base="1.1.0" version="1.1.0a" date="20160922"/>
454 <problemtype>memory leak</problemtype>
456 A malicious client can send an excessively large OCSP Status Request extension.
457 If that client continually requests renegotiation, sending a large OCSP Status
458 Request extension each time, then there will be unbounded memory growth on the
459 server. This will eventually lead to a Denial Of Service attack through memory
460 exhaustion. Servers with a default configuration are vulnerable even if they do
461 not support OCSP. Builds using the "no-ocsp" build time option are not affected.
463 Servers using OpenSSL versions prior to 1.0.1g are not vulnerable in a default
464 configuration, instead only if an application explicitly enables OCSP stapling
467 <advisory url="/news/secadv/20160922.txt"/>
468 <reported source="Shi Lei (Gear Team, Qihoo 360 Inc.)" date="20160829"/>
470 <issue public="20160922">
471 <impact severity="Moderate"/>
472 <cve name="2016-6305"/>
473 <affects base="1.1.0" version="1.1.0"/>
474 <fixed base="1.1.0" version="1.1.0a" date="20160922"/>
477 OpenSSL 1.1.0 SSL/TLS will hang during a call to SSL_peek() if the peer sends an
478 empty record. This could be exploited by a malicious peer in a Denial Of Service
481 <advisory url="/news/secadv/20160922.txt"/>
482 <reported source="Alex Gaynor" date="20160910"/>
484 <issue public="20160824">
485 <impact severity="Low"/>
486 <cve name="2016-6303"/>
487 <affects base="1.0.1" version="1.0.1"/>
488 <affects base="1.0.1" version="1.0.1a"/>
489 <affects base="1.0.1" version="1.0.1b"/>
490 <affects base="1.0.1" version="1.0.1c"/>
491 <affects base="1.0.1" version="1.0.1d"/>
492 <affects base="1.0.1" version="1.0.1e"/>
493 <affects base="1.0.1" version="1.0.1f"/>
494 <affects base="1.0.1" version="1.0.1g"/>
495 <affects base="1.0.1" version="1.0.1h"/>
496 <affects base="1.0.1" version="1.0.1i"/>
497 <affects base="1.0.1" version="1.0.1j"/>
498 <affects base="1.0.1" version="1.0.1k"/>
499 <affects base="1.0.1" version="1.0.1l"/>
500 <affects base="1.0.1" version="1.0.1m"/>
501 <affects base="1.0.1" version="1.0.1n"/>
502 <affects base="1.0.1" version="1.0.1o"/>
503 <affects base="1.0.1" version="1.0.1p"/>
504 <affects base="1.0.1" version="1.0.1q"/>
505 <affects base="1.0.1" version="1.0.1r"/>
506 <affects base="1.0.1" version="1.0.1s"/>
507 <affects base="1.0.1" version="1.0.1t"/>
508 <affects base="1.0.2" version="1.0.2"/>
509 <affects base="1.0.2" version="1.0.2a"/>
510 <affects base="1.0.2" version="1.0.2b"/>
511 <affects base="1.0.2" version="1.0.2c"/>
512 <affects base="1.0.2" version="1.0.2d"/>
513 <affects base="1.0.2" version="1.0.2e"/>
514 <affects base="1.0.2" version="1.0.2f"/>
515 <affects base="1.0.2" version="1.0.2g"/>
516 <affects base="1.0.2" version="1.0.2h"/>
517 <fixed base="1.0.1" version="1.0.1u" date="20160922"/>
518 <fixed base="1.0.2" version="1.0.2i" date="20160922"/>
521 An overflow can occur in MDC2_Update() either if called directly or
522 through the EVP_DigestUpdate() function using MDC2. If an attacker
523 is able to supply very large amounts of input data after a previous
524 call to EVP_EncryptUpdate() with a partial block then a length check
525 can overflow resulting in a heap corruption.
527 The amount of data needed is comparable to SIZE_MAX which is impractical
530 <advisory url="/news/secadv/20160922.txt"/>
531 <reported source="Shi Lei (Gear Team, Qihoo 360 Inc.)" date="20160811"/>
533 <issue public="20160823">
534 <impact severity="Low"/>
535 <cve name="2016-6302"/>
536 <affects base="1.0.1" version="1.0.1"/>
537 <affects base="1.0.1" version="1.0.1a"/>
538 <affects base="1.0.1" version="1.0.1b"/>
539 <affects base="1.0.1" version="1.0.1c"/>
540 <affects base="1.0.1" version="1.0.1d"/>
541 <affects base="1.0.1" version="1.0.1e"/>
542 <affects base="1.0.1" version="1.0.1f"/>
543 <affects base="1.0.1" version="1.0.1g"/>
544 <affects base="1.0.1" version="1.0.1h"/>
545 <affects base="1.0.1" version="1.0.1i"/>
546 <affects base="1.0.1" version="1.0.1j"/>
547 <affects base="1.0.1" version="1.0.1k"/>
548 <affects base="1.0.1" version="1.0.1l"/>
549 <affects base="1.0.1" version="1.0.1m"/>
550 <affects base="1.0.1" version="1.0.1n"/>
551 <affects base="1.0.1" version="1.0.1o"/>
552 <affects base="1.0.1" version="1.0.1p"/>
553 <affects base="1.0.1" version="1.0.1q"/>
554 <affects base="1.0.1" version="1.0.1r"/>
555 <affects base="1.0.1" version="1.0.1s"/>
556 <affects base="1.0.1" version="1.0.1t"/>
557 <affects base="1.0.2" version="1.0.2"/>
558 <affects base="1.0.2" version="1.0.2a"/>
559 <affects base="1.0.2" version="1.0.2b"/>
560 <affects base="1.0.2" version="1.0.2c"/>
561 <affects base="1.0.2" version="1.0.2d"/>
562 <affects base="1.0.2" version="1.0.2e"/>
563 <affects base="1.0.2" version="1.0.2f"/>
564 <affects base="1.0.2" version="1.0.2g"/>
565 <affects base="1.0.2" version="1.0.2h"/>
566 <fixed base="1.0.1" version="1.0.1u" date="20160922"/>
567 <fixed base="1.0.2" version="1.0.2i" date="20160922"/>
570 If a server uses SHA512 for TLS session ticket HMAC it is vulnerable to a
571 DoS attack where a malformed ticket will result in an OOB read which will
574 The use of SHA512 in TLS session tickets is comparatively rare as it requires
575 a custom server callback and ticket lookup mechanism.
577 <advisory url="/news/secadv/20160922.txt"/>
578 <reported source="Shi Lei (Gear Team, Qihoo 360 Inc.)" date="20160819"/>
580 <issue public="20160816">
581 <impact severity="Low"/>
582 <cve name="2016-2182"/>
583 <affects base="1.0.1" version="1.0.1"/>
584 <affects base="1.0.1" version="1.0.1a"/>
585 <affects base="1.0.1" version="1.0.1b"/>
586 <affects base="1.0.1" version="1.0.1c"/>
587 <affects base="1.0.1" version="1.0.1d"/>
588 <affects base="1.0.1" version="1.0.1e"/>
589 <affects base="1.0.1" version="1.0.1f"/>
590 <affects base="1.0.1" version="1.0.1g"/>
591 <affects base="1.0.1" version="1.0.1h"/>
592 <affects base="1.0.1" version="1.0.1i"/>
593 <affects base="1.0.1" version="1.0.1j"/>
594 <affects base="1.0.1" version="1.0.1k"/>
595 <affects base="1.0.1" version="1.0.1l"/>
596 <affects base="1.0.1" version="1.0.1m"/>
597 <affects base="1.0.1" version="1.0.1n"/>
598 <affects base="1.0.1" version="1.0.1o"/>
599 <affects base="1.0.1" version="1.0.1p"/>
600 <affects base="1.0.1" version="1.0.1q"/>
601 <affects base="1.0.1" version="1.0.1r"/>
602 <affects base="1.0.1" version="1.0.1s"/>
603 <affects base="1.0.1" version="1.0.1t"/>
604 <affects base="1.0.2" version="1.0.2"/>
605 <affects base="1.0.2" version="1.0.2a"/>
606 <affects base="1.0.2" version="1.0.2b"/>
607 <affects base="1.0.2" version="1.0.2c"/>
608 <affects base="1.0.2" version="1.0.2d"/>
609 <affects base="1.0.2" version="1.0.2e"/>
610 <affects base="1.0.2" version="1.0.2f"/>
611 <affects base="1.0.2" version="1.0.2g"/>
612 <affects base="1.0.2" version="1.0.2h"/>
613 <fixed base="1.0.1" version="1.0.1u" date="20160922"/>
614 <fixed base="1.0.2" version="1.0.2i" date="20160922"/>
617 The function BN_bn2dec() does not check the return value of BN_div_word().
618 This can cause an OOB write if an application uses this function with an
619 overly large BIGNUM. This could be a problem if an overly large certificate
620 or CRL is printed out from an untrusted source. TLS is not affected because
621 record limits will reject an oversized certificate before it is parsed.
623 <advisory url="/news/secadv/20160922.txt"/>
624 <reported source="Shi Lei (Gear Team, Qihoo 360 Inc.)" date="20160802"/>
626 <issue public="20160722">
627 <impact severity="Low"/>
628 <cve name="2016-2180"/>
629 <affects base="1.0.1" version="1.0.1"/>
630 <affects base="1.0.1" version="1.0.1a"/>
631 <affects base="1.0.1" version="1.0.1b"/>
632 <affects base="1.0.1" version="1.0.1c"/>
633 <affects base="1.0.1" version="1.0.1d"/>
634 <affects base="1.0.1" version="1.0.1e"/>
635 <affects base="1.0.1" version="1.0.1f"/>
636 <affects base="1.0.1" version="1.0.1g"/>
637 <affects base="1.0.1" version="1.0.1h"/>
638 <affects base="1.0.1" version="1.0.1i"/>
639 <affects base="1.0.1" version="1.0.1j"/>
640 <affects base="1.0.1" version="1.0.1k"/>
641 <affects base="1.0.1" version="1.0.1l"/>
642 <affects base="1.0.1" version="1.0.1m"/>
643 <affects base="1.0.1" version="1.0.1n"/>
644 <affects base="1.0.1" version="1.0.1o"/>
645 <affects base="1.0.1" version="1.0.1p"/>
646 <affects base="1.0.1" version="1.0.1q"/>
647 <affects base="1.0.1" version="1.0.1r"/>
648 <affects base="1.0.1" version="1.0.1s"/>
649 <affects base="1.0.1" version="1.0.1t"/>
650 <affects base="1.0.2" version="1.0.2"/>
651 <affects base="1.0.2" version="1.0.2a"/>
652 <affects base="1.0.2" version="1.0.2b"/>
653 <affects base="1.0.2" version="1.0.2c"/>
654 <affects base="1.0.2" version="1.0.2d"/>
655 <affects base="1.0.2" version="1.0.2e"/>
656 <affects base="1.0.2" version="1.0.2f"/>
657 <affects base="1.0.2" version="1.0.2g"/>
658 <affects base="1.0.2" version="1.0.2h"/>
659 <fixed base="1.0.1" version="1.0.1u" date="20160922"/>
660 <fixed base="1.0.2" version="1.0.2i" date="20160922"/>
663 The function TS_OBJ_print_bio() misuses OBJ_obj2txt(): the return value is
664 the total length the OID text representation would use and not the amount
665 of data written. This will result in OOB reads when large OIDs are presented.
667 <advisory url="/news/secadv/20160922.txt"/>
668 <reported source="Shi Lei (Gear Team, Qihoo 360 Inc.)" date="20160721"/>
670 <issue public="20160601">
671 <impact severity="Low"/>
672 <cve name="2016-2177"/>
673 <affects base="1.0.1" version="1.0.1"/>
674 <affects base="1.0.1" version="1.0.1a"/>
675 <affects base="1.0.1" version="1.0.1b"/>
676 <affects base="1.0.1" version="1.0.1c"/>
677 <affects base="1.0.1" version="1.0.1d"/>
678 <affects base="1.0.1" version="1.0.1e"/>
679 <affects base="1.0.1" version="1.0.1f"/>
680 <affects base="1.0.1" version="1.0.1g"/>
681 <affects base="1.0.1" version="1.0.1h"/>
682 <affects base="1.0.1" version="1.0.1i"/>
683 <affects base="1.0.1" version="1.0.1j"/>
684 <affects base="1.0.1" version="1.0.1k"/>
685 <affects base="1.0.1" version="1.0.1l"/>
686 <affects base="1.0.1" version="1.0.1m"/>
687 <affects base="1.0.1" version="1.0.1n"/>
688 <affects base="1.0.1" version="1.0.1o"/>
689 <affects base="1.0.1" version="1.0.1p"/>
690 <affects base="1.0.1" version="1.0.1q"/>
691 <affects base="1.0.1" version="1.0.1r"/>
692 <affects base="1.0.1" version="1.0.1s"/>
693 <affects base="1.0.1" version="1.0.1t"/>
694 <affects base="1.0.2" version="1.0.2"/>
695 <affects base="1.0.2" version="1.0.2a"/>
696 <affects base="1.0.2" version="1.0.2b"/>
697 <affects base="1.0.2" version="1.0.2c"/>
698 <affects base="1.0.2" version="1.0.2d"/>
699 <affects base="1.0.2" version="1.0.2e"/>
700 <affects base="1.0.2" version="1.0.2f"/>
701 <affects base="1.0.2" version="1.0.2g"/>
702 <affects base="1.0.2" version="1.0.2h"/>
703 <fixed base="1.0.1" version="1.0.1u" date="20160922"/>
704 <fixed base="1.0.2" version="1.0.2i" date="20160922"/>
707 Avoid some undefined pointer arithmetic
709 A common idiom in the codebase is to check limits in the following manner:
712 Where "p" points to some malloc'd data of SIZE bytes and
715 "len" here could be from some externally supplied data (e.g. from a TLS
718 The rules of C pointer arithmetic are such that "p + len" is only well
719 defined where len <= SIZE. Therefore the above idiom is actually
722 For example this could cause problems if some malloc implementation
723 provides an address for "p" such that "p + len" actually overflows for
724 values of len that are too big and therefore p + len < limit.
726 <advisory url="/news/secadv/20160922.txt"/>
727 <reported source="Guido Vranken" date="20160504"/>
729 <issue public="20160607">
730 <impact severity="Low"/>
731 <cve name="2016-2178"/>
732 <affects base="1.0.1" version="1.0.1"/>
733 <affects base="1.0.1" version="1.0.1a"/>
734 <affects base="1.0.1" version="1.0.1b"/>
735 <affects base="1.0.1" version="1.0.1c"/>
736 <affects base="1.0.1" version="1.0.1d"/>
737 <affects base="1.0.1" version="1.0.1e"/>
738 <affects base="1.0.1" version="1.0.1f"/>
739 <affects base="1.0.1" version="1.0.1g"/>
740 <affects base="1.0.1" version="1.0.1h"/>
741 <affects base="1.0.1" version="1.0.1i"/>
742 <affects base="1.0.1" version="1.0.1j"/>
743 <affects base="1.0.1" version="1.0.1k"/>
744 <affects base="1.0.1" version="1.0.1l"/>
745 <affects base="1.0.1" version="1.0.1m"/>
746 <affects base="1.0.1" version="1.0.1n"/>
747 <affects base="1.0.1" version="1.0.1o"/>
748 <affects base="1.0.1" version="1.0.1p"/>
749 <affects base="1.0.1" version="1.0.1q"/>
750 <affects base="1.0.1" version="1.0.1r"/>
751 <affects base="1.0.1" version="1.0.1s"/>
752 <affects base="1.0.1" version="1.0.1t"/>
753 <affects base="1.0.2" version="1.0.2"/>
754 <affects base="1.0.2" version="1.0.2a"/>
755 <affects base="1.0.2" version="1.0.2b"/>
756 <affects base="1.0.2" version="1.0.2c"/>
757 <affects base="1.0.2" version="1.0.2d"/>
758 <affects base="1.0.2" version="1.0.2e"/>
759 <affects base="1.0.2" version="1.0.2f"/>
760 <affects base="1.0.2" version="1.0.2g"/>
761 <affects base="1.0.2" version="1.0.2h"/>
762 <fixed base="1.0.1" version="1.0.1u" date="20160922"/>
763 <fixed base="1.0.2" version="1.0.2i" date="20160922"/>
766 Operations in the DSA signing algorithm should run in constant time in order to
767 avoid side channel attacks. A flaw in the OpenSSL DSA implementation means that
768 a non-constant time codepath is followed for certain operations. This has been
769 demonstrated through a cache-timing attack to be sufficient for an attacker to
770 recover the private DSA key.
772 <advisory url="/news/secadv/20160922.txt"/>
773 <reported source="César Pereida (Aalto University), Billy Brumley (Tampere University of Technology), and Yuval Yarom (The University of Adelaide and NICTA)" date="20160523"/>
775 <issue public="20160822">
776 <impact severity="Low"/>
777 <cve name="2016-2179"/>
778 <affects base="1.0.1" version="1.0.1"/>
779 <affects base="1.0.1" version="1.0.1a"/>
780 <affects base="1.0.1" version="1.0.1b"/>
781 <affects base="1.0.1" version="1.0.1c"/>
782 <affects base="1.0.1" version="1.0.1d"/>
783 <affects base="1.0.1" version="1.0.1e"/>
784 <affects base="1.0.1" version="1.0.1f"/>
785 <affects base="1.0.1" version="1.0.1g"/>
786 <affects base="1.0.1" version="1.0.1h"/>
787 <affects base="1.0.1" version="1.0.1i"/>
788 <affects base="1.0.1" version="1.0.1j"/>
789 <affects base="1.0.1" version="1.0.1k"/>
790 <affects base="1.0.1" version="1.0.1l"/>
791 <affects base="1.0.1" version="1.0.1m"/>
792 <affects base="1.0.1" version="1.0.1n"/>
793 <affects base="1.0.1" version="1.0.1o"/>
794 <affects base="1.0.1" version="1.0.1p"/>
795 <affects base="1.0.1" version="1.0.1q"/>
796 <affects base="1.0.1" version="1.0.1r"/>
797 <affects base="1.0.1" version="1.0.1s"/>
798 <affects base="1.0.1" version="1.0.1t"/>
799 <affects base="1.0.2" version="1.0.2"/>
800 <affects base="1.0.2" version="1.0.2a"/>
801 <affects base="1.0.2" version="1.0.2b"/>
802 <affects base="1.0.2" version="1.0.2c"/>
803 <affects base="1.0.2" version="1.0.2d"/>
804 <affects base="1.0.2" version="1.0.2e"/>
805 <affects base="1.0.2" version="1.0.2f"/>
806 <affects base="1.0.2" version="1.0.2g"/>
807 <affects base="1.0.2" version="1.0.2h"/>
808 <fixed base="1.0.1" version="1.0.1u" date="20160922"/>
809 <fixed base="1.0.2" version="1.0.2i" date="20160922"/>
812 In a DTLS connection where handshake messages are delivered out-of-order those
813 messages that OpenSSL is not yet ready to process will be buffered for later
814 use. Under certain circumstances, a flaw in the logic means that those messages
815 do not get removed from the buffer even though the handshake has been completed.
816 An attacker could force up to approx. 15 messages to remain in the buffer when
817 they are no longer required. These messages will be cleared when the DTLS
818 connection is closed. The default maximum size for a message is 100k. Therefore
819 the attacker could force an additional 1500k to be consumed per connection. By
820 opening many simulataneous connections an attacker could cause a DoS attack
821 through memory exhaustion.
823 <advisory url="/news/secadv/20160922.txt"/>
824 <reported source="Quan Luo" date="20160622"/>
826 <issue public="20160819">
827 <impact severity="Low"/>
828 <cve name="2016-2181"/>
829 <affects base="1.0.1" version="1.0.1"/>
830 <affects base="1.0.1" version="1.0.1a"/>
831 <affects base="1.0.1" version="1.0.1b"/>
832 <affects base="1.0.1" version="1.0.1c"/>
833 <affects base="1.0.1" version="1.0.1d"/>
834 <affects base="1.0.1" version="1.0.1e"/>
835 <affects base="1.0.1" version="1.0.1f"/>
836 <affects base="1.0.1" version="1.0.1g"/>
837 <affects base="1.0.1" version="1.0.1h"/>
838 <affects base="1.0.1" version="1.0.1i"/>
839 <affects base="1.0.1" version="1.0.1j"/>
840 <affects base="1.0.1" version="1.0.1k"/>
841 <affects base="1.0.1" version="1.0.1l"/>
842 <affects base="1.0.1" version="1.0.1m"/>
843 <affects base="1.0.1" version="1.0.1n"/>
844 <affects base="1.0.1" version="1.0.1o"/>
845 <affects base="1.0.1" version="1.0.1p"/>
846 <affects base="1.0.1" version="1.0.1q"/>
847 <affects base="1.0.1" version="1.0.1r"/>
848 <affects base="1.0.1" version="1.0.1s"/>
849 <affects base="1.0.1" version="1.0.1t"/>
850 <affects base="1.0.2" version="1.0.2"/>
851 <affects base="1.0.2" version="1.0.2a"/>
852 <affects base="1.0.2" version="1.0.2b"/>
853 <affects base="1.0.2" version="1.0.2c"/>
854 <affects base="1.0.2" version="1.0.2d"/>
855 <affects base="1.0.2" version="1.0.2e"/>
856 <affects base="1.0.2" version="1.0.2f"/>
857 <affects base="1.0.2" version="1.0.2g"/>
858 <affects base="1.0.2" version="1.0.2h"/>
859 <fixed base="1.0.1" version="1.0.1u" date="20160922"/>
860 <fixed base="1.0.2" version="1.0.2i" date="20160922"/>
863 A flaw in the DTLS replay attack protection mechanism means that records that
864 arrive for future epochs update the replay protection "window" before the MAC
865 for the record has been validated. This could be exploited by an attacker by
866 sending a record for the next epoch (which does not have to decrypt or have a
867 valid MAC), with a very large sequence number. This means that all subsequent
868 legitimate packets are dropped causing a denial of service for a specific
871 <advisory url="/news/secadv/20160922.txt"/>
872 <reported source="OCAP audit team" date="20151121"/>
874 <issue public="20160921">
875 <impact severity="Low"/>
876 <cve name="2016-6306"/>
877 <affects base="1.0.1" version="1.0.1"/>
878 <affects base="1.0.1" version="1.0.1a"/>
879 <affects base="1.0.1" version="1.0.1b"/>
880 <affects base="1.0.1" version="1.0.1c"/>
881 <affects base="1.0.1" version="1.0.1d"/>
882 <affects base="1.0.1" version="1.0.1e"/>
883 <affects base="1.0.1" version="1.0.1f"/>
884 <affects base="1.0.1" version="1.0.1g"/>
885 <affects base="1.0.1" version="1.0.1h"/>
886 <affects base="1.0.1" version="1.0.1i"/>
887 <affects base="1.0.1" version="1.0.1j"/>
888 <affects base="1.0.1" version="1.0.1k"/>
889 <affects base="1.0.1" version="1.0.1l"/>
890 <affects base="1.0.1" version="1.0.1m"/>
891 <affects base="1.0.1" version="1.0.1n"/>
892 <affects base="1.0.1" version="1.0.1o"/>
893 <affects base="1.0.1" version="1.0.1p"/>
894 <affects base="1.0.1" version="1.0.1q"/>
895 <affects base="1.0.1" version="1.0.1r"/>
896 <affects base="1.0.1" version="1.0.1s"/>
897 <affects base="1.0.1" version="1.0.1t"/>
898 <affects base="1.0.2" version="1.0.2"/>
899 <affects base="1.0.2" version="1.0.2a"/>
900 <affects base="1.0.2" version="1.0.2b"/>
901 <affects base="1.0.2" version="1.0.2c"/>
902 <affects base="1.0.2" version="1.0.2d"/>
903 <affects base="1.0.2" version="1.0.2e"/>
904 <affects base="1.0.2" version="1.0.2f"/>
905 <affects base="1.0.2" version="1.0.2g"/>
906 <affects base="1.0.2" version="1.0.2h"/>
907 <fixed base="1.0.1" version="1.0.1u" date="20160922"/>
908 <fixed base="1.0.2" version="1.0.2i" date="20160922"/>
910 In OpenSSL 1.0.2 and earlier some missing message length checks can result in
911 OOB reads of up to 2 bytes beyond an allocated buffer. There is a theoretical
912 DoS risk but this has not been observed in practice on common platforms.
914 The messages affected are client certificate, client certificate request and
915 server certificate. As a result the attack can only be performed against
916 a client or a server which enables client authentication.
918 <advisory url="/news/secadv/20160922.txt"/>
919 <reported source="Shi Lei (Gear Team, Qihoo 360 Inc.)" date="20160822"/>
921 <issue public="20160921">
922 <impact severity="Low"/>
923 <cve name="2016-6307"/>
924 <affects base="1.1.0" version="1.1.0"/>
925 <fixed base="1.1.0" version="1.1.0a" date="20160922"/>
928 A TLS message includes 3 bytes for its length in the header for the message.
929 This would allow for messages up to 16Mb in length. Messages of this length are
930 excessive and OpenSSL includes a check to ensure that a peer is sending
931 reasonably sized messages in order to avoid too much memory being consumed to
932 service a connection. A flaw in the logic of version 1.1.0 means that memory for
933 the message is allocated too early, prior to the excessive message length
934 check. Due to way memory is allocated in OpenSSL this could mean an attacker
935 could force up to 21Mb to be allocated to service a connection. This could lead
936 to a Denial of Service through memory exhaustion. However, the excessive message
937 length check still takes place, and this would cause the connection to
938 immediately fail. Assuming that the application calls SSL_free() on the failed
939 conneciton in a timely manner then the 21Mb of allocated memory will then be
940 immediately freed again. Therefore the excessive memory allocation will be
941 transitory in nature. This then means that there is only a security impact if:
943 1) The application does not call SSL_free() in a timely manner in the
944 event that the connection fails
946 2) The application is working in a constrained environment where there
947 is very little free memory
949 3) The attacker initiates multiple connection attempts such that there
950 are multiple connections in a state where memory has been allocated for
951 the connection; SSL_free() has not yet been called; and there is
952 insufficient memory to service the multiple requests.
954 Except in the instance of (1) above any Denial Of Service is likely to
955 be transitory because as soon as the connection fails the memory is
956 subsequently freed again in the SSL_free() call. However there is an
957 increased risk during this period of application crashes due to the lack
958 of memory - which would then mean a more serious Denial of Service.
960 <advisory url="/news/secadv/20160922.txt"/>
961 <reported source="Shi Lei (Gear Team, Qihoo 360 Inc.)" date="20160818"/>
963 <issue public="20160921">
964 <impact severity="Low"/>
965 <cve name="2016-6308"/>
966 <affects base="1.1.0" version="1.1.0"/>
967 <fixed base="1.1.0" version="1.1.0a" date="20160922"/>
970 A DTLS message includes 3 bytes for its length in the header for the message.
971 This would allow for messages up to 16Mb in length. Messages of this length are
972 excessive and OpenSSL includes a check to ensure that a peer is sending
973 reasonably sized messages in order to avoid too much memory being consumed to
974 service a connection. A flaw in the logic of version 1.1.0 means that memory for
975 the message is allocated too early, prior to the excessive message length
976 check. Due to way memory is allocated in OpenSSL this could mean an attacker
977 could force up to 21Mb to be allocated to service a connection. This could lead
978 to a Denial of Service through memory exhaustion. However, the excessive message
979 length check still takes place, and this would cause the connection to
980 immediately fail. Assuming that the application calls SSL_free() on the failed
981 conneciton in a timely manner then the 21Mb of allocated memory will then be
982 immediately freed again. Therefore the excessive memory allocation will be
983 transitory in nature. This then means that there is only a security impact if:
985 1) The application does not call SSL_free() in a timely manner in the
986 event that the connection fails
988 2) The application is working in a constrained environment where there
989 is very little free memory
991 3) The attacker initiates multiple connection attempts such that there
992 are multiple connections in a state where memory has been allocated for
993 the connection; SSL_free() has not yet been called; and there is
994 insufficient memory to service the multiple requests.
996 Except in the instance of (1) above any Denial Of Service is likely to
997 be transitory because as soon as the connection fails the memory is
998 subsequently freed again in the SSL_free() call. However there is an
999 increased risk during this period of application crashes due to the lack
1000 of memory - which would then mean a more serious Denial of Service.
1002 <advisory url="/news/secadv/20160922.txt"/>
1003 <reported source="Shi Lei (Gear Team, Qihoo 360 Inc.)" date="20160818"/>
1005 <issue public="20160503">
1006 <impact severity="High"/>
1007 <cve name="2016-2108"/>
1008 <affects base="1.0.1" version="1.0.1"/>
1009 <affects base="1.0.1" version="1.0.1a"/>
1010 <affects base="1.0.1" version="1.0.1b"/>
1011 <affects base="1.0.1" version="1.0.1c"/>
1012 <affects base="1.0.1" version="1.0.1d"/>
1013 <affects base="1.0.1" version="1.0.1e"/>
1014 <affects base="1.0.1" version="1.0.1f"/>
1015 <affects base="1.0.1" version="1.0.1g"/>
1016 <affects base="1.0.1" version="1.0.1h"/>
1017 <affects base="1.0.1" version="1.0.1i"/>
1018 <affects base="1.0.1" version="1.0.1j"/>
1019 <affects base="1.0.1" version="1.0.1k"/>
1020 <affects base="1.0.1" version="1.0.1l"/>
1021 <affects base="1.0.1" version="1.0.1m"/>
1022 <affects base="1.0.1" version="1.0.1n"/>
1023 <affects base="1.0.2" version="1.0.2"/>
1024 <affects base="1.0.2" version="1.0.2a"/>
1025 <affects base="1.0.2" version="1.0.2b"/>
1026 <fixed base="1.0.1" version="1.0.1o" date="20160612"/>
1027 <fixed base="1.0.2" version="1.0.2c" date="20160612"/>
1030 This issue affected versions of OpenSSL prior to April 2015. The bug
1031 causing the vulnerability was fixed on April 18th 2015, and released
1032 as part of the June 11th 2015 security releases. The security impact
1033 of the bug was not known at the time.
1035 In previous versions of OpenSSL, ASN.1 encoding the value zero
1036 represented as a negative integer can cause a buffer underflow
1037 with an out-of-bounds write in i2c_ASN1_INTEGER. The ASN.1 parser does
1038 not normally create "negative zeroes" when parsing ASN.1 input, and
1039 therefore, an attacker cannot trigger this bug.
1041 However, a second, independent bug revealed that the ASN.1 parser
1042 (specifically, d2i_ASN1_TYPE) can misinterpret a large universal tag
1043 as a negative zero value. Large universal tags are not present in any
1044 common ASN.1 structures (such as X509) but are accepted as part of ANY
1047 Therefore, if an application deserializes untrusted ASN.1 structures
1048 containing an ANY field, and later reserializes them, an attacker may
1049 be able to trigger an out-of-bounds write. This has been shown to
1050 cause memory corruption that is potentially exploitable with some
1051 malloc implementations.
1053 Applications that parse and re-encode X509 certificates are known to
1054 be vulnerable. Applications that verify RSA signatures on X509
1055 certificates may also be vulnerable; however, only certificates with
1056 valid signatures trigger ASN.1 re-encoding and hence the
1057 bug. Specifically, since OpenSSL's default TLS X509 chain verification
1058 code verifies the certificate chain from root to leaf, TLS handshakes
1059 could only be targeted with valid certificates issued by trusted
1060 Certification Authorities.
1062 <advisory url="/news/secadv/20160503.txt"/>
1063 <reported source="Huzaifa Sidhpurwala (Red Hat), Hanno Böck, David Benjamin (Google)" date="20160331"/>
1065 <issue public="20160503">
1066 <impact severity="High"/>
1067 <cve name="2016-2107"/>
1068 <affects base="1.0.1" version="1.0.1"/>
1069 <affects base="1.0.1" version="1.0.1a"/>
1070 <affects base="1.0.1" version="1.0.1b"/>
1071 <affects base="1.0.1" version="1.0.1c"/>
1072 <affects base="1.0.1" version="1.0.1d"/>
1073 <affects base="1.0.1" version="1.0.1e"/>
1074 <affects base="1.0.1" version="1.0.1f"/>
1075 <affects base="1.0.1" version="1.0.1g"/>
1076 <affects base="1.0.1" version="1.0.1h"/>
1077 <affects base="1.0.1" version="1.0.1i"/>
1078 <affects base="1.0.1" version="1.0.1j"/>
1079 <affects base="1.0.1" version="1.0.1k"/>
1080 <affects base="1.0.1" version="1.0.1l"/>
1081 <affects base="1.0.1" version="1.0.1m"/>
1082 <affects base="1.0.1" version="1.0.1n"/>
1083 <affects base="1.0.1" version="1.0.1o"/>
1084 <affects base="1.0.1" version="1.0.1p"/>
1085 <affects base="1.0.1" version="1.0.1q"/>
1086 <affects base="1.0.1" version="1.0.1r"/>
1087 <affects base="1.0.1" version="1.0.1s"/>
1088 <affects base="1.0.2" version="1.0.2"/>
1089 <affects base="1.0.2" version="1.0.2a"/>
1090 <affects base="1.0.2" version="1.0.2b"/>
1091 <affects base="1.0.2" version="1.0.2c"/>
1092 <affects base="1.0.2" version="1.0.2d"/>
1093 <affects base="1.0.2" version="1.0.2e"/>
1094 <affects base="1.0.2" version="1.0.2f"/>
1095 <affects base="1.0.2" version="1.0.2g"/>
1096 <fixed base="1.0.1" version="1.0.1t" date="20160503"/>
1097 <fixed base="1.0.2" version="1.0.2h" date="20160503"/>
1100 A MITM attacker can use a padding oracle attack to decrypt traffic
1101 when the connection uses an AES CBC cipher and the server support
1104 This issue was introduced as part of the fix for Lucky 13 padding
1105 attack (CVE-2013-0169). The padding check was rewritten to be in
1106 constant time by making sure that always the same bytes are read and
1107 compared against either the MAC or padding bytes. But it no longer
1108 checked that there was enough data to have both the MAC and padding
1111 <advisory url="/news/secadv/20160503.txt"/>
1112 <reported source="Juraj Somorovsky" date="20160413"/>
1114 <issue public="20160503">
1115 <impact severity="Low"/>
1116 <cve name="2016-2105"/>
1117 <affects base="1.0.1" version="1.0.1"/>
1118 <affects base="1.0.1" version="1.0.1a"/>
1119 <affects base="1.0.1" version="1.0.1b"/>
1120 <affects base="1.0.1" version="1.0.1c"/>
1121 <affects base="1.0.1" version="1.0.1d"/>
1122 <affects base="1.0.1" version="1.0.1e"/>
1123 <affects base="1.0.1" version="1.0.1f"/>
1124 <affects base="1.0.1" version="1.0.1g"/>
1125 <affects base="1.0.1" version="1.0.1h"/>
1126 <affects base="1.0.1" version="1.0.1i"/>
1127 <affects base="1.0.1" version="1.0.1j"/>
1128 <affects base="1.0.1" version="1.0.1k"/>
1129 <affects base="1.0.1" version="1.0.1l"/>
1130 <affects base="1.0.1" version="1.0.1m"/>
1131 <affects base="1.0.1" version="1.0.1n"/>
1132 <affects base="1.0.1" version="1.0.1o"/>
1133 <affects base="1.0.1" version="1.0.1p"/>
1134 <affects base="1.0.1" version="1.0.1q"/>
1135 <affects base="1.0.1" version="1.0.1r"/>
1136 <affects base="1.0.1" version="1.0.1s"/>
1137 <affects base="1.0.2" version="1.0.2"/>
1138 <affects base="1.0.2" version="1.0.2a"/>
1139 <affects base="1.0.2" version="1.0.2b"/>
1140 <affects base="1.0.2" version="1.0.2c"/>
1141 <affects base="1.0.2" version="1.0.2d"/>
1142 <affects base="1.0.2" version="1.0.2e"/>
1143 <affects base="1.0.2" version="1.0.2f"/>
1144 <affects base="1.0.2" version="1.0.2g"/>
1145 <fixed base="1.0.1" version="1.0.1t" date="20160503"/>
1146 <fixed base="1.0.2" version="1.0.2h" date="20160503"/>
1149 An overflow can occur in the EVP_EncodeUpdate() function which is used for
1150 Base64 encoding of binary data. If an attacker is able to supply very
1151 large amounts of input data then a length check can overflow resulting in
1154 Internally to OpenSSL the EVP_EncodeUpdate() function is primarly used by the
1155 PEM_write_bio* family of functions. These are mainly used within the OpenSSL
1156 command line applications. These internal uses are not considered vulnerable
1157 because all calls are bounded with length checks so no overflow is possible.
1158 User applications that call these APIs directly with large amounts of untrusted
1159 data may be vulnerable. (Note: Initial analysis suggested that the
1160 PEM_write_bio* were vulnerable, and this is reflected in the patch commit
1161 message. This is no longer believed to be the case).
1163 <advisory url="/news/secadv/20160503.txt"/>
1164 <reported source="Guido Vranken" date="20160303"/>
1166 <issue public="20160503">
1167 <impact severity="Low"/>
1168 <cve name="2016-2106"/>
1169 <affects base="1.0.1" version="1.0.1"/>
1170 <affects base="1.0.1" version="1.0.1a"/>
1171 <affects base="1.0.1" version="1.0.1b"/>
1172 <affects base="1.0.1" version="1.0.1c"/>
1173 <affects base="1.0.1" version="1.0.1d"/>
1174 <affects base="1.0.1" version="1.0.1e"/>
1175 <affects base="1.0.1" version="1.0.1f"/>
1176 <affects base="1.0.1" version="1.0.1g"/>
1177 <affects base="1.0.1" version="1.0.1h"/>
1178 <affects base="1.0.1" version="1.0.1i"/>
1179 <affects base="1.0.1" version="1.0.1j"/>
1180 <affects base="1.0.1" version="1.0.1k"/>
1181 <affects base="1.0.1" version="1.0.1l"/>
1182 <affects base="1.0.1" version="1.0.1m"/>
1183 <affects base="1.0.1" version="1.0.1n"/>
1184 <affects base="1.0.1" version="1.0.1o"/>
1185 <affects base="1.0.1" version="1.0.1p"/>
1186 <affects base="1.0.1" version="1.0.1q"/>
1187 <affects base="1.0.1" version="1.0.1r"/>
1188 <affects base="1.0.1" version="1.0.1s"/>
1189 <affects base="1.0.2" version="1.0.2"/>
1190 <affects base="1.0.2" version="1.0.2a"/>
1191 <affects base="1.0.2" version="1.0.2b"/>
1192 <affects base="1.0.2" version="1.0.2c"/>
1193 <affects base="1.0.2" version="1.0.2d"/>
1194 <affects base="1.0.2" version="1.0.2e"/>
1195 <affects base="1.0.2" version="1.0.2f"/>
1196 <affects base="1.0.2" version="1.0.2g"/>
1197 <fixed base="1.0.1" version="1.0.1t" date="20160503"/>
1198 <fixed base="1.0.2" version="1.0.2h" date="20160503"/>
1201 An overflow can occur in the EVP_EncryptUpdate() function. If an attacker
1202 is able to supply very large amounts of input data after a previous call
1203 to EVP_EncryptUpdate() with a partial block then a length check can
1204 overflow resulting in a heap corruption. Following an analysis of all
1205 OpenSSL internal usage of the EVP_EncryptUpdate() function all usage is
1206 one of two forms. The first form is where the EVP_EncryptUpdate() call is
1207 known to be the first called function after an EVP_EncryptInit(), and
1208 therefore that specific call must be safe. The second form is where the
1209 length passed to EVP_EncryptUpdate() can be seen from the code to be some
1210 small value and therefore there is no possibility of an overflow. Since
1211 all instances are one of these two forms, it is believed that there can be
1212 no overflows in internal code due to this problem. It should be noted that
1213 EVP_DecryptUpdate() can call EVP_EncryptUpdate() in certain code paths.
1214 Also EVP_CipherUpdate() is a synonym for EVP_EncryptUpdate(). All
1215 instances of these calls have also been analysed too and it is believed
1216 there are no instances in internal usage where an overflow could occur.
1218 This could still represent a security issue for end user code that calls
1219 this function directly.
1221 <advisory url="/news/secadv/20160503.txt"/>
1222 <reported source="Guido Vranken" date="20160303"/>
1224 <issue public="20160503">
1225 <impact severity="Low"/>
1226 <cve name="2016-2109"/>
1227 <affects base="1.0.1" version="1.0.1"/>
1228 <affects base="1.0.1" version="1.0.1a"/>
1229 <affects base="1.0.1" version="1.0.1b"/>
1230 <affects base="1.0.1" version="1.0.1c"/>
1231 <affects base="1.0.1" version="1.0.1d"/>
1232 <affects base="1.0.1" version="1.0.1e"/>
1233 <affects base="1.0.1" version="1.0.1f"/>
1234 <affects base="1.0.1" version="1.0.1g"/>
1235 <affects base="1.0.1" version="1.0.1h"/>
1236 <affects base="1.0.1" version="1.0.1i"/>
1237 <affects base="1.0.1" version="1.0.1j"/>
1238 <affects base="1.0.1" version="1.0.1k"/>
1239 <affects base="1.0.1" version="1.0.1l"/>
1240 <affects base="1.0.1" version="1.0.1m"/>
1241 <affects base="1.0.1" version="1.0.1n"/>
1242 <affects base="1.0.1" version="1.0.1o"/>
1243 <affects base="1.0.1" version="1.0.1p"/>
1244 <affects base="1.0.1" version="1.0.1q"/>
1245 <affects base="1.0.1" version="1.0.1r"/>
1246 <affects base="1.0.1" version="1.0.1s"/>
1247 <affects base="1.0.2" version="1.0.2"/>
1248 <affects base="1.0.2" version="1.0.2a"/>
1249 <affects base="1.0.2" version="1.0.2b"/>
1250 <affects base="1.0.2" version="1.0.2c"/>
1251 <affects base="1.0.2" version="1.0.2d"/>
1252 <affects base="1.0.2" version="1.0.2e"/>
1253 <affects base="1.0.2" version="1.0.2f"/>
1254 <affects base="1.0.2" version="1.0.2g"/>
1255 <fixed base="1.0.1" version="1.0.1t" date="20160503"/>
1256 <fixed base="1.0.2" version="1.0.2h" date="20160503"/>
1259 When ASN.1 data is read from a BIO using functions such as d2i_CMS_bio()
1260 a short invalid encoding can casuse allocation of large amounts of memory
1261 potentially consuming excessive resources or exhausting memory.
1263 Any application parsing untrusted data through d2i BIO functions is
1264 affected. The memory based functions such as d2i_X509() are *not*
1265 affected. Since the memory based functions are used by the TLS library,
1266 TLS applications are not affected.
1268 <advisory url="/news/secadv/20160503.txt"/>
1269 <reported source="Brian Carpenter" date="20160404"/>
1271 <issue public="20160503">
1272 <impact severity="Low"/>
1273 <cve name="2016-2176"/>
1274 <affects base="1.0.1" version="1.0.1"/>
1275 <affects base="1.0.1" version="1.0.1a"/>
1276 <affects base="1.0.1" version="1.0.1b"/>
1277 <affects base="1.0.1" version="1.0.1c"/>
1278 <affects base="1.0.1" version="1.0.1d"/>
1279 <affects base="1.0.1" version="1.0.1e"/>
1280 <affects base="1.0.1" version="1.0.1f"/>
1281 <affects base="1.0.1" version="1.0.1g"/>
1282 <affects base="1.0.1" version="1.0.1h"/>
1283 <affects base="1.0.1" version="1.0.1i"/>
1284 <affects base="1.0.1" version="1.0.1j"/>
1285 <affects base="1.0.1" version="1.0.1k"/>
1286 <affects base="1.0.1" version="1.0.1l"/>
1287 <affects base="1.0.1" version="1.0.1m"/>
1288 <affects base="1.0.1" version="1.0.1n"/>
1289 <affects base="1.0.1" version="1.0.1o"/>
1290 <affects base="1.0.1" version="1.0.1p"/>
1291 <affects base="1.0.1" version="1.0.1q"/>
1292 <affects base="1.0.1" version="1.0.1r"/>
1293 <affects base="1.0.1" version="1.0.1s"/>
1294 <affects base="1.0.2" version="1.0.2"/>
1295 <affects base="1.0.2" version="1.0.2a"/>
1296 <affects base="1.0.2" version="1.0.2b"/>
1297 <affects base="1.0.2" version="1.0.2c"/>
1298 <affects base="1.0.2" version="1.0.2d"/>
1299 <affects base="1.0.2" version="1.0.2e"/>
1300 <affects base="1.0.2" version="1.0.2f"/>
1301 <affects base="1.0.2" version="1.0.2g"/>
1302 <fixed base="1.0.1" version="1.0.1t" date="20160503"/>
1303 <fixed base="1.0.2" version="1.0.2h" date="20160503"/>
1306 ASN1 Strings that are over 1024 bytes can cause an overread in
1307 applications using the X509_NAME_oneline() function on EBCDIC systems.
1308 This could result in arbitrary stack data being returned in the buffer.
1310 <advisory url="/news/secadv/20160503.txt"/>
1311 <reported source="Guido Vranken" date="20160305"/>
1313 <issue public="20160301">
1314 <impact severity="High"/>
1315 <cve name="2016-0800"/>
1316 <affects base="1.0.1" version="1.0.1"/>
1317 <affects base="1.0.1" version="1.0.1a"/>
1318 <affects base="1.0.1" version="1.0.1b"/>
1319 <affects base="1.0.1" version="1.0.1c"/>
1320 <affects base="1.0.1" version="1.0.1d"/>
1321 <affects base="1.0.1" version="1.0.1e"/>
1322 <affects base="1.0.1" version="1.0.1f"/>
1323 <affects base="1.0.1" version="1.0.1g"/>
1324 <affects base="1.0.1" version="1.0.1h"/>
1325 <affects base="1.0.1" version="1.0.1i"/>
1326 <affects base="1.0.1" version="1.0.1j"/>
1327 <affects base="1.0.1" version="1.0.1k"/>
1328 <affects base="1.0.1" version="1.0.1l"/>
1329 <affects base="1.0.1" version="1.0.1m"/>
1330 <affects base="1.0.1" version="1.0.1n"/>
1331 <affects base="1.0.1" version="1.0.1o"/>
1332 <affects base="1.0.1" version="1.0.1p"/>
1333 <affects base="1.0.1" version="1.0.1q"/>
1334 <affects base="1.0.1" version="1.0.1r"/>
1335 <affects base="1.0.2" version="1.0.2"/>
1336 <affects base="1.0.2" version="1.0.2a"/>
1337 <affects base="1.0.2" version="1.0.2b"/>
1338 <affects base="1.0.2" version="1.0.2c"/>
1339 <affects base="1.0.2" version="1.0.2d"/>
1340 <affects base="1.0.2" version="1.0.2e"/>
1341 <affects base="1.0.2" version="1.0.2f"/>
1342 <fixed base="1.0.1" version="1.0.1s" date="20160301"/>
1343 <fixed base="1.0.2" version="1.0.2g" date="20160301"/>
1346 A cross-protocol attack was discovered that could lead to decryption of TLS
1347 sessions by using a server supporting SSLv2 and EXPORT cipher suites as a
1348 Bleichenbacher RSA padding oracle. Note that traffic between clients and
1349 non-vulnerable servers can be decrypted provided another server supporting
1350 SSLv2 and EXPORT ciphers (even with a different protocol such as SMTP, IMAP or
1351 POP) shares the RSA keys of the non-vulnerable server. This vulnerability is
1352 known as DROWN (CVE-2016-0800).
1354 Recovering one session key requires the attacker to perform approximately 2^50
1355 computation, as well as thousands of connections to the affected server. A more
1356 efficient variant of the DROWN attack exists against unpatched OpenSSL servers
1357 using versions that predate 1.0.2a, 1.0.1m, 1.0.0r and 0.9.8zf released on
1358 19/Mar/2015 (see CVE-2016-0703 below).
1360 Users can avoid this issue by disabling the SSLv2 protocol in all their SSL/TLS
1361 servers, if they've not done so already. Disabling all SSLv2 ciphers is also
1362 sufficient, provided the patches for CVE-2015-3197 (fixed in OpenSSL 1.0.1r and
1363 1.0.2f) have been deployed. Servers that have not disabled the SSLv2 protocol,
1364 and are not patched for CVE-2015-3197 are vulnerable to DROWN even if all SSLv2
1365 ciphers are nominally disabled, because malicious clients can force the use of
1366 SSLv2 with EXPORT ciphers.
1368 OpenSSL 1.0.2g and 1.0.1s deploy the following mitigation against DROWN:
1370 SSLv2 is now by default disabled at build-time. Builds that are not configured
1371 with "enable-ssl2" will not support SSLv2. Even if "enable-ssl2" is used,
1372 users who want to negotiate SSLv2 via the version-flexible SSLv23_method() will
1373 need to explicitly call either of:
1375 SSL_CTX_clear_options(ctx, SSL_OP_NO_SSLv2);
1377 SSL_clear_options(ssl, SSL_OP_NO_SSLv2);
1379 as appropriate. Even if either of those is used, or the application explicitly
1380 uses the version-specific SSLv2_method() or its client or server variants,
1381 SSLv2 ciphers vulnerable to exhaustive search key recovery have been removed.
1382 Specifically, the SSLv2 40-bit EXPORT ciphers, and SSLv2 56-bit DES are no
1385 In addition, weak ciphers in SSLv3 and up are now disabled in default builds of
1386 OpenSSL. Builds that are not configured with "enable-weak-ssl-ciphers" will
1387 not provide any "EXPORT" or "LOW" strength ciphers.
1389 <advisory url="/news/secadv/20160301.txt"/>
1390 <reported source="Nimrod Aviram and Sebastian Schinzel" date="20151229"/>
1392 <issue public="20160301">
1393 <impact severity="Low"/>
1394 <cve name="2016-0705"/>
1395 <affects base="1.0.1" version="1.0.1"/>
1396 <affects base="1.0.1" version="1.0.1a"/>
1397 <affects base="1.0.1" version="1.0.1b"/>
1398 <affects base="1.0.1" version="1.0.1c"/>
1399 <affects base="1.0.1" version="1.0.1d"/>
1400 <affects base="1.0.1" version="1.0.1e"/>
1401 <affects base="1.0.1" version="1.0.1f"/>
1402 <affects base="1.0.1" version="1.0.1g"/>
1403 <affects base="1.0.1" version="1.0.1h"/>
1404 <affects base="1.0.1" version="1.0.1i"/>
1405 <affects base="1.0.1" version="1.0.1j"/>
1406 <affects base="1.0.1" version="1.0.1k"/>
1407 <affects base="1.0.1" version="1.0.1l"/>
1408 <affects base="1.0.1" version="1.0.1m"/>
1409 <affects base="1.0.1" version="1.0.1n"/>
1410 <affects base="1.0.1" version="1.0.1o"/>
1411 <affects base="1.0.1" version="1.0.1p"/>
1412 <affects base="1.0.1" version="1.0.1q"/>
1413 <affects base="1.0.1" version="1.0.1r"/>
1414 <affects base="1.0.2" version="1.0.2"/>
1415 <affects base="1.0.2" version="1.0.2a"/>
1416 <affects base="1.0.2" version="1.0.2b"/>
1417 <affects base="1.0.2" version="1.0.2c"/>
1418 <affects base="1.0.2" version="1.0.2d"/>
1419 <affects base="1.0.2" version="1.0.2e"/>
1420 <affects base="1.0.2" version="1.0.2f"/>
1421 <fixed base="1.0.1" version="1.0.1s" date="20160301"/>
1422 <fixed base="1.0.2" version="1.0.2g" date="20160301"/>
1425 A double free bug was discovered when OpenSSL parses malformed DSA private keys
1426 and could lead to a DoS attack or memory corruption for applications that
1427 receive DSA private keys from untrusted sources. This scenario is considered
1430 <advisory url="/news/secadv/20160301.txt"/>
1431 <reported source="Adam Langley (Google/BoringSSL)" date="20160207"/>
1433 <issue public="20160301">
1434 <impact severity="Low"/>
1435 <cve name="2016-0798"/>
1436 <affects base="1.0.1" version="1.0.1"/>
1437 <affects base="1.0.1" version="1.0.1a"/>
1438 <affects base="1.0.1" version="1.0.1b"/>
1439 <affects base="1.0.1" version="1.0.1c"/>
1440 <affects base="1.0.1" version="1.0.1d"/>
1441 <affects base="1.0.1" version="1.0.1e"/>
1442 <affects base="1.0.1" version="1.0.1f"/>
1443 <affects base="1.0.1" version="1.0.1g"/>
1444 <affects base="1.0.1" version="1.0.1h"/>
1445 <affects base="1.0.1" version="1.0.1i"/>
1446 <affects base="1.0.1" version="1.0.1j"/>
1447 <affects base="1.0.1" version="1.0.1k"/>
1448 <affects base="1.0.1" version="1.0.1l"/>
1449 <affects base="1.0.1" version="1.0.1m"/>
1450 <affects base="1.0.1" version="1.0.1n"/>
1451 <affects base="1.0.1" version="1.0.1o"/>
1452 <affects base="1.0.1" version="1.0.1p"/>
1453 <affects base="1.0.1" version="1.0.1q"/>
1454 <affects base="1.0.1" version="1.0.1r"/>
1455 <affects base="1.0.2" version="1.0.2"/>
1456 <affects base="1.0.2" version="1.0.2a"/>
1457 <affects base="1.0.2" version="1.0.2b"/>
1458 <affects base="1.0.2" version="1.0.2c"/>
1459 <affects base="1.0.2" version="1.0.2d"/>
1460 <affects base="1.0.2" version="1.0.2e"/>
1461 <affects base="1.0.2" version="1.0.2f"/>
1462 <fixed base="1.0.1" version="1.0.1s" date="20160301"/>
1463 <fixed base="1.0.2" version="1.0.2g" date="20160301"/>
1466 The SRP user database lookup method SRP_VBASE_get_by_user had
1467 confusing memory management semantics; the returned pointer was sometimes newly
1468 allocated, and sometimes owned by the callee. The calling code has no way of
1469 distinguishing these two cases.
1471 Specifically, SRP servers that configure a secret seed to hide valid
1472 login information are vulnerable to a memory leak: an attacker
1473 connecting with an invalid username can cause a memory leak of around
1474 300 bytes per connection. Servers that do not configure SRP, or
1475 configure SRP but do not configure a seed are not vulnerable.
1477 In Apache, the seed directive is known as SSLSRPUnknownUserSeed.
1479 To mitigate the memory leak, the seed handling in
1480 SRP_VBASE_get_by_user is now disabled even if the user has configured
1481 a seed. Applications are advised to migrate to
1482 SRP_VBASE_get1_by_user. However, note that OpenSSL makes no strong
1483 guarantees about the indistinguishability of valid and invalid
1484 logins. In particular, computations are currently not carried out in
1487 <advisory url="/news/secadv/20160301.txt"/>
1488 <reported source="Emilia Käsper (OpenSSL)" date="20160223"/>
1490 <issue public="20160301">
1491 <impact severity="Low"/>
1492 <cve name="2016-0797"/>
1493 <affects base="1.0.1" version="1.0.1"/>
1494 <affects base="1.0.1" version="1.0.1a"/>
1495 <affects base="1.0.1" version="1.0.1b"/>
1496 <affects base="1.0.1" version="1.0.1c"/>
1497 <affects base="1.0.1" version="1.0.1d"/>
1498 <affects base="1.0.1" version="1.0.1e"/>
1499 <affects base="1.0.1" version="1.0.1f"/>
1500 <affects base="1.0.1" version="1.0.1g"/>
1501 <affects base="1.0.1" version="1.0.1h"/>
1502 <affects base="1.0.1" version="1.0.1i"/>
1503 <affects base="1.0.1" version="1.0.1j"/>
1504 <affects base="1.0.1" version="1.0.1k"/>
1505 <affects base="1.0.1" version="1.0.1l"/>
1506 <affects base="1.0.1" version="1.0.1m"/>
1507 <affects base="1.0.1" version="1.0.1n"/>
1508 <affects base="1.0.1" version="1.0.1o"/>
1509 <affects base="1.0.1" version="1.0.1p"/>
1510 <affects base="1.0.1" version="1.0.1q"/>
1511 <affects base="1.0.1" version="1.0.1r"/>
1512 <affects base="1.0.2" version="1.0.2"/>
1513 <affects base="1.0.2" version="1.0.2a"/>
1514 <affects base="1.0.2" version="1.0.2b"/>
1515 <affects base="1.0.2" version="1.0.2c"/>
1516 <affects base="1.0.2" version="1.0.2d"/>
1517 <affects base="1.0.2" version="1.0.2e"/>
1518 <affects base="1.0.2" version="1.0.2f"/>
1519 <fixed base="1.0.1" version="1.0.1s" date="20160301"/>
1520 <fixed base="1.0.2" version="1.0.2g" date="20160301"/>
1523 In the BN_hex2bn function the number of hex digits is calculated using an int
1524 value |i|. Later |bn_expand| is called with a value of |i * 4|. For large values
1525 of |i| this can result in |bn_expand| not allocating any memory because |i * 4|
1526 is negative. This can leave the internal BIGNUM data field as NULL leading to a
1527 subsequent NULL ptr deref. For very large values of |i|, the calculation |i * 4|
1528 could be a positive value smaller than |i|. In this case memory is allocated to
1529 the internal BIGNUM data field, but it is insufficiently sized leading to heap
1530 corruption. A similar issue exists in BN_dec2bn. This could have security
1531 consequences if BN_hex2bn/BN_dec2bn is ever called by user applications with
1532 very large untrusted hex/dec data. This is anticipated to be a rare occurrence.
1534 All OpenSSL internal usage of these functions use data that is not expected to
1535 be untrusted, e.g. config file data or application command line arguments. If
1536 user developed applications generate config file data based on untrusted data
1537 then it is possible that this could also lead to security consequences. This is
1538 also anticipated to be rare.
1540 <advisory url="/news/secadv/20160301.txt"/>
1541 <reported source="Guido Vranken" date="20160219"/>
1543 <issue public="20160301">
1544 <impact severity="Low"/>
1545 <cve name="2016-0799"/>
1546 <affects base="1.0.1" version="1.0.1"/>
1547 <affects base="1.0.1" version="1.0.1a"/>
1548 <affects base="1.0.1" version="1.0.1b"/>
1549 <affects base="1.0.1" version="1.0.1c"/>
1550 <affects base="1.0.1" version="1.0.1d"/>
1551 <affects base="1.0.1" version="1.0.1e"/>
1552 <affects base="1.0.1" version="1.0.1f"/>
1553 <affects base="1.0.1" version="1.0.1g"/>
1554 <affects base="1.0.1" version="1.0.1h"/>
1555 <affects base="1.0.1" version="1.0.1i"/>
1556 <affects base="1.0.1" version="1.0.1j"/>
1557 <affects base="1.0.1" version="1.0.1k"/>
1558 <affects base="1.0.1" version="1.0.1l"/>
1559 <affects base="1.0.1" version="1.0.1m"/>
1560 <affects base="1.0.1" version="1.0.1n"/>
1561 <affects base="1.0.1" version="1.0.1o"/>
1562 <affects base="1.0.1" version="1.0.1p"/>
1563 <affects base="1.0.1" version="1.0.1q"/>
1564 <affects base="1.0.1" version="1.0.1r"/>
1565 <affects base="1.0.2" version="1.0.2"/>
1566 <affects base="1.0.2" version="1.0.2a"/>
1567 <affects base="1.0.2" version="1.0.2b"/>
1568 <affects base="1.0.2" version="1.0.2c"/>
1569 <affects base="1.0.2" version="1.0.2d"/>
1570 <affects base="1.0.2" version="1.0.2e"/>
1571 <affects base="1.0.2" version="1.0.2f"/>
1572 <fixed base="1.0.1" version="1.0.1s" date="20160301"/>
1573 <fixed base="1.0.2" version="1.0.2g" date="20160301"/>
1576 The internal |fmtstr| function used in processing a "%s" format string in the
1577 BIO_*printf functions could overflow while calculating the length of a string
1578 and cause an OOB read when printing very long strings.
1580 Additionally the internal |doapr_outch| function can attempt to write to an OOB
1581 memory location (at an offset from the NULL pointer) in the event of a memory
1582 allocation failure. In 1.0.2 and below this could be caused where the size of a
1583 buffer to be allocated is greater than INT_MAX. E.g. this could be in processing
1584 a very long "%s" format string. Memory leaks can also occur.
1586 The first issue may mask the second issue dependent on compiler behaviour.
1587 These problems could enable attacks where large amounts of untrusted data is
1588 passed to the BIO_*printf functions. If applications use these functions in this
1589 way then they could be vulnerable. OpenSSL itself uses these functions when
1590 printing out human-readable dumps of ASN.1 data. Therefore applications that
1591 print this data could be vulnerable if the data is from untrusted sources.
1592 OpenSSL command line applications could also be vulnerable where they print out
1593 ASN.1 data, or if untrusted data is passed as command line arguments.
1595 Libssl is not considered directly vulnerable. Additionally certificates etc
1596 received via remote connections via libssl are also unlikely to be able to
1597 trigger these issues because of message size limits enforced within libssl.
1599 <advisory url="/news/secadv/20160301.txt"/>
1600 <reported source="Guido Vranken" date="20160223"/>
1602 <issue public="20160301">
1603 <impact severity="Low"/>
1604 <cve name="2016-0702"/>
1605 <affects base="1.0.1" version="1.0.1"/>
1606 <affects base="1.0.1" version="1.0.1a"/>
1607 <affects base="1.0.1" version="1.0.1b"/>
1608 <affects base="1.0.1" version="1.0.1c"/>
1609 <affects base="1.0.1" version="1.0.1d"/>
1610 <affects base="1.0.1" version="1.0.1e"/>
1611 <affects base="1.0.1" version="1.0.1f"/>
1612 <affects base="1.0.1" version="1.0.1g"/>
1613 <affects base="1.0.1" version="1.0.1h"/>
1614 <affects base="1.0.1" version="1.0.1i"/>
1615 <affects base="1.0.1" version="1.0.1j"/>
1616 <affects base="1.0.1" version="1.0.1k"/>
1617 <affects base="1.0.1" version="1.0.1l"/>
1618 <affects base="1.0.1" version="1.0.1m"/>
1619 <affects base="1.0.1" version="1.0.1n"/>
1620 <affects base="1.0.1" version="1.0.1o"/>
1621 <affects base="1.0.1" version="1.0.1p"/>
1622 <affects base="1.0.1" version="1.0.1q"/>
1623 <affects base="1.0.1" version="1.0.1r"/>
1624 <affects base="1.0.2" version="1.0.2"/>
1625 <affects base="1.0.2" version="1.0.2a"/>
1626 <affects base="1.0.2" version="1.0.2b"/>
1627 <affects base="1.0.2" version="1.0.2c"/>
1628 <affects base="1.0.2" version="1.0.2d"/>
1629 <affects base="1.0.2" version="1.0.2e"/>
1630 <affects base="1.0.2" version="1.0.2f"/>
1631 <fixed base="1.0.1" version="1.0.1s" date="20160301"/>
1632 <fixed base="1.0.2" version="1.0.2g" date="20160301"/>
1635 A side-channel attack was found which makes use of cache-bank conflicts on the
1636 Intel Sandy-Bridge microarchitecture which could lead to the recovery of RSA
1637 keys. The ability to exploit this issue is limited as it relies on an attacker
1638 who has control of code in a thread running on the same hyper-threaded core as
1639 the victim thread which is performing decryptions.
1641 <advisory url="/news/secadv/20160301.txt"/>
1642 <reported source="Yuval Yarom, The University of Adelaide and NICTA, Daniel Genkin, Technion and Tel Aviv University, and Nadia Heninger, University of Pennsylvania" date="20160108"/>
1644 <issue public="20160301">
1645 <impact severity="High"/>
1646 <cve name="2016-0703"/>
1648 <affects base="0.9.8" version="0.9.8"/>
1649 <affects base="0.9.8" version="0.9.8a"/>
1650 <affects base="0.9.8" version="0.9.8b"/>
1651 <affects base="0.9.8" version="0.9.8c"/>
1652 <affects base="0.9.8" version="0.9.8d"/>
1653 <affects base="0.9.8" version="0.9.8e"/>
1654 <affects base="0.9.8" version="0.9.8f"/>
1655 <affects base="0.9.8" version="0.9.8g"/>
1656 <affects base="0.9.8" version="0.9.8h"/>
1657 <affects base="0.9.8" version="0.9.8i"/>
1658 <affects base="0.9.8" version="0.9.8j"/>
1659 <affects base="0.9.8" version="0.9.8k"/>
1660 <affects base="0.9.8" version="0.9.8l"/>
1661 <affects base="0.9.8" version="0.9.8m"/>
1662 <affects base="0.9.8" version="0.9.8n"/>
1663 <affects base="0.9.8" version="0.9.8o"/>
1664 <affects base="0.9.8" version="0.9.8p"/>
1665 <affects base="0.9.8" version="0.9.8q"/>
1666 <affects base="0.9.8" version="0.9.8r"/>
1667 <affects base="0.9.8" version="0.9.8s"/>
1668 <affects base="0.9.8" version="0.9.8t"/>
1669 <affects base="0.9.8" version="0.9.8u"/>
1670 <affects base="0.9.8" version="0.9.8v"/>
1671 <affects base="0.9.8" version="0.9.8w"/>
1672 <affects base="0.9.8" version="0.9.8x"/>
1673 <affects base="0.9.8" version="0.9.8y"/>
1674 <affects base="0.9.8" version="0.9.8za"/>
1675 <affects base="0.9.8" version="0.9.8zb"/>
1676 <affects base="0.9.8" version="0.9.8zc"/>
1677 <affects base="0.9.8" version="0.9.8zd"/>
1678 <affects base="0.9.8" version="0.9.8ze"/>
1679 <affects base="1.0.0" version="1.0.0"/>
1680 <affects base="1.0.0" version="1.0.0a"/>
1681 <affects base="1.0.0" version="1.0.0b"/>
1682 <affects base="1.0.0" version="1.0.0c"/>
1683 <affects base="1.0.0" version="1.0.0d"/>
1684 <affects base="1.0.0" version="1.0.0e"/>
1685 <affects base="1.0.0" version="1.0.0f"/>
1686 <affects base="1.0.0" version="1.0.0g"/>
1687 <affects base="1.0.0" version="1.0.0i"/>
1688 <affects base="1.0.0" version="1.0.0j"/>
1689 <affects base="1.0.0" version="1.0.0k"/>
1690 <affects base="1.0.0" version="1.0.0l"/>
1691 <affects base="1.0.0" version="1.0.0m"/>
1692 <affects base="1.0.0" version="1.0.0n"/>
1693 <affects base="1.0.0" version="1.0.0o"/>
1694 <affects base="1.0.0" version="1.0.0p"/>
1695 <affects base="1.0.0" version="1.0.0q"/>
1696 <affects base="1.0.1" version="1.0.1"/>
1697 <affects base="1.0.1" version="1.0.1a"/>
1698 <affects base="1.0.1" version="1.0.1b"/>
1699 <affects base="1.0.1" version="1.0.1c"/>
1700 <affects base="1.0.1" version="1.0.1d"/>
1701 <affects base="1.0.1" version="1.0.1e"/>
1702 <affects base="1.0.1" version="1.0.1f"/>
1703 <affects base="1.0.1" version="1.0.1g"/>
1704 <affects base="1.0.1" version="1.0.1h"/>
1705 <affects base="1.0.1" version="1.0.1i"/>
1706 <affects base="1.0.1" version="1.0.1j"/>
1707 <affects base="1.0.1" version="1.0.1k"/>
1708 <affects base="1.0.1" version="1.0.1l"/>
1709 <affects base="1.0.2" version="1.0.2"/>
1710 <fixed base="0.9.8" version="0.9.8zf" date="20150319"/>
1711 <fixed base="1.0.0" version="1.0.0r" date="20150319"/>
1712 <fixed base="1.0.1" version="1.0.1m" date="20150319"/>
1713 <fixed base="1.0.2" version="1.0.2a" date="20150319"/>
1716 This issue only affected versions of OpenSSL prior to March 19th 2015 at which
1717 time the code was refactored to address vulnerability CVE-2015-0293.
1719 s2_srvr.c did not enforce that clear-key-length is 0 for non-export ciphers. If
1720 clear-key bytes are present for these ciphers, they *displace* encrypted-key
1721 bytes. This leads to an efficient divide-and-conquer key recovery attack: if an
1722 eavesdropper has intercepted an SSLv2 handshake, they can use the server as an
1723 oracle to determine the SSLv2 master-key, using only 16 connections to the
1724 server and negligible computation.
1726 More importantly, this leads to a more efficient version of DROWN that is
1727 effective against non-export ciphersuites, and requires no significant
1730 <advisory url="/news/secadv/20160301.txt"/>
1731 <reported source="David Adrian and J.Alex Halderman (University of Michigan)" date="20160210"/>
1733 <issue public="20160301">
1734 <impact severity="Moderate"/>
1735 <cve name="2016-0704"/>
1737 <affects base="0.9.8" version="0.9.8"/>
1738 <affects base="0.9.8" version="0.9.8a"/>
1739 <affects base="0.9.8" version="0.9.8b"/>
1740 <affects base="0.9.8" version="0.9.8c"/>
1741 <affects base="0.9.8" version="0.9.8d"/>
1742 <affects base="0.9.8" version="0.9.8e"/>
1743 <affects base="0.9.8" version="0.9.8f"/>
1744 <affects base="0.9.8" version="0.9.8g"/>
1745 <affects base="0.9.8" version="0.9.8h"/>
1746 <affects base="0.9.8" version="0.9.8i"/>
1747 <affects base="0.9.8" version="0.9.8j"/>
1748 <affects base="0.9.8" version="0.9.8k"/>
1749 <affects base="0.9.8" version="0.9.8l"/>
1750 <affects base="0.9.8" version="0.9.8m"/>
1751 <affects base="0.9.8" version="0.9.8n"/>
1752 <affects base="0.9.8" version="0.9.8o"/>
1753 <affects base="0.9.8" version="0.9.8p"/>
1754 <affects base="0.9.8" version="0.9.8q"/>
1755 <affects base="0.9.8" version="0.9.8r"/>
1756 <affects base="0.9.8" version="0.9.8s"/>
1757 <affects base="0.9.8" version="0.9.8t"/>
1758 <affects base="0.9.8" version="0.9.8u"/>
1759 <affects base="0.9.8" version="0.9.8v"/>
1760 <affects base="0.9.8" version="0.9.8w"/>
1761 <affects base="0.9.8" version="0.9.8x"/>
1762 <affects base="0.9.8" version="0.9.8y"/>
1763 <affects base="0.9.8" version="0.9.8za"/>
1764 <affects base="0.9.8" version="0.9.8zb"/>
1765 <affects base="0.9.8" version="0.9.8zc"/>
1766 <affects base="0.9.8" version="0.9.8zd"/>
1767 <affects base="0.9.8" version="0.9.8ze"/>
1768 <affects base="1.0.0" version="1.0.0"/>
1769 <affects base="1.0.0" version="1.0.0a"/>
1770 <affects base="1.0.0" version="1.0.0b"/>
1771 <affects base="1.0.0" version="1.0.0c"/>
1772 <affects base="1.0.0" version="1.0.0d"/>
1773 <affects base="1.0.0" version="1.0.0e"/>
1774 <affects base="1.0.0" version="1.0.0f"/>
1775 <affects base="1.0.0" version="1.0.0g"/>
1776 <affects base="1.0.0" version="1.0.0i"/>
1777 <affects base="1.0.0" version="1.0.0j"/>
1778 <affects base="1.0.0" version="1.0.0k"/>
1779 <affects base="1.0.0" version="1.0.0l"/>
1780 <affects base="1.0.0" version="1.0.0m"/>
1781 <affects base="1.0.0" version="1.0.0n"/>
1782 <affects base="1.0.0" version="1.0.0o"/>
1783 <affects base="1.0.0" version="1.0.0p"/>
1784 <affects base="1.0.0" version="1.0.0q"/>
1785 <affects base="1.0.1" version="1.0.1"/>
1786 <affects base="1.0.1" version="1.0.1a"/>
1787 <affects base="1.0.1" version="1.0.1b"/>
1788 <affects base="1.0.1" version="1.0.1c"/>
1789 <affects base="1.0.1" version="1.0.1d"/>
1790 <affects base="1.0.1" version="1.0.1e"/>
1791 <affects base="1.0.1" version="1.0.1f"/>
1792 <affects base="1.0.1" version="1.0.1g"/>
1793 <affects base="1.0.1" version="1.0.1h"/>
1794 <affects base="1.0.1" version="1.0.1i"/>
1795 <affects base="1.0.1" version="1.0.1j"/>
1796 <affects base="1.0.1" version="1.0.1k"/>
1797 <affects base="1.0.1" version="1.0.1l"/>
1798 <affects base="1.0.2" version="1.0.2"/>
1799 <fixed base="0.9.8" version="0.9.8zf" date="20150319"/>
1800 <fixed base="1.0.0" version="1.0.0r" date="20150319"/>
1801 <fixed base="1.0.1" version="1.0.1m" date="20150319"/>
1802 <fixed base="1.0.2" version="1.0.2a" date="20150319"/>
1805 This issue only affected versions of OpenSSL prior to March 19th 2015 at which
1806 time the code was refactored to address the vulnerability CVE-2015-0293.
1808 s2_srvr.c overwrite the wrong bytes in the master-key when applying
1809 Bleichenbacher protection for export cipher suites. This provides a
1810 Bleichenbacher oracle, and could potentially allow more efficient variants of
1813 <advisory url="/news/secadv/20160301.txt"/>
1814 <reported source="David Adrian and J.Alex Halderman (University of Michigan)" date="20160210"/>
1816 <issue public="20160128">
1817 <impact severity="High"/>
1818 <cve name="2016-0701"/>
1819 <affects base="1.0.2" version="1.0.2"/>
1820 <affects base="1.0.2" version="1.0.2a"/>
1821 <affects base="1.0.2" version="1.0.2b"/>
1822 <affects base="1.0.2" version="1.0.2c"/>
1823 <affects base="1.0.2" version="1.0.2d"/>
1824 <affects base="1.0.2" version="1.0.2e"/>
1825 <fixed base="1.0.2" version="1.0.2f" date="2016-0701"/>
1828 Historically OpenSSL usually only ever generated DH parameters based on "safe"
1829 primes. More recently (in version 1.0.2) support was provided for generating
1830 X9.42 style parameter files such as those required for RFC 5114 support. The
1831 primes used in such files may not be "safe". Where an application is using DH
1832 configured with parameters based on primes that are not "safe" then an attacker
1833 could use this fact to find a peer's private DH exponent. This attack requires
1834 that the attacker complete multiple handshakes in which the peer uses the same
1835 private DH exponent. For example this could be used to discover a TLS server's
1836 private DH exponent if it's reusing the private DH exponent or it's using a
1837 static DH ciphersuite.
1839 OpenSSL provides the option SSL_OP_SINGLE_DH_USE for ephemeral DH (DHE) in TLS.
1840 It is not on by default. If the option is not set then the server reuses the
1841 same private DH exponent for the life of the server process and would be
1842 vulnerable to this attack. It is believed that many popular applications do set
1843 this option and would therefore not be at risk.
1845 OpenSSL before 1.0.2f will reuse the key if:
1846 - SSL_CTX_set_tmp_dh()/SSL_set_tmp_dh() is used and SSL_OP_SINGLE_DH_USE is not
1848 - SSL_CTX_set_tmp_dh_callback()/SSL_set_tmp_dh_callback() is used, and both the
1849 parameters and the key are set and SSL_OP_SINGLE_DH_USE is not used. This is
1850 an undocumted feature and parameter files don't contain the key.
1851 - Static DH ciphersuites are used. The key is part of the certificate and
1852 so it will always reuse it. This is only supported in 1.0.2.
1854 It will not reuse the key for DHE ciphers suites if:
1855 - SSL_OP_SINGLE_DH_USE is set
1856 - SSL_CTX_set_tmp_dh_callback()/SSL_set_tmp_dh_callback() is used and the
1857 callback does not provide the key, only the parameters. The callback is
1858 almost always used like this.
1860 Non-safe primes are generated by OpenSSL when using:
1861 - genpkey with the dh_rfc5114 option. This will write an X9.42 style file
1862 including the prime-order subgroup size "q". This is supported since the 1.0.2
1863 version. Older versions can't read files generated in this way.
1864 - dhparam with the -dsaparam option. This has always been documented as
1865 requiring the single use.
1867 The fix for this issue adds an additional check where a "q" parameter is
1868 available (as is the case in X9.42 based parameters). This detects the
1869 only known attack, and is the only possible defense for static DH ciphersuites.
1870 This could have some performance impact.
1872 Additionally the SSL_OP_SINGLE_DH_USE option has been switched on by default
1873 and cannot be disabled. This could have some performance impact.
1875 <advisory url="/news/secadv/20160128.txt"/>
1876 <reported source="Antonio Sanso (Adobe)" date="20160112"/>
1878 <issue public="20160128">
1879 <impact severity="Low"/>
1880 <cve name="2015-3197"/>
1881 <affects base="1.0.1" version="1.0.1"/>
1882 <affects base="1.0.1" version="1.0.1a"/>
1883 <affects base="1.0.1" version="1.0.1b"/>
1884 <affects base="1.0.1" version="1.0.1c"/>
1885 <affects base="1.0.1" version="1.0.1d"/>
1886 <affects base="1.0.1" version="1.0.1e"/>
1887 <affects base="1.0.1" version="1.0.1f"/>
1888 <affects base="1.0.1" version="1.0.1g"/>
1889 <affects base="1.0.1" version="1.0.1h"/>
1890 <affects base="1.0.1" version="1.0.1i"/>
1891 <affects base="1.0.1" version="1.0.1j"/>
1892 <affects base="1.0.1" version="1.0.1k"/>
1893 <affects base="1.0.1" version="1.0.1l"/>
1894 <affects base="1.0.1" version="1.0.1m"/>
1895 <affects base="1.0.1" version="1.0.1n"/>
1896 <affects base="1.0.1" version="1.0.1o"/>
1897 <affects base="1.0.1" version="1.0.1p"/>
1898 <affects base="1.0.1" version="1.0.1q"/>
1899 <affects base="1.0.2" version="1.0.2"/>
1900 <affects base="1.0.2" version="1.0.2a"/>
1901 <affects base="1.0.2" version="1.0.2b"/>
1902 <affects base="1.0.2" version="1.0.2c"/>
1903 <affects base="1.0.2" version="1.0.2d"/>
1904 <affects base="1.0.2" version="1.0.2e"/>
1905 <fixed base="1.0.1" version="1.0.1r" date="20160128"/>
1906 <fixed base="1.0.2" version="1.0.2f" date="20160128"/>
1909 A malicious client can negotiate SSLv2 ciphers that have been disabled on the
1910 server and complete SSLv2 handshakes even if all SSLv2 ciphers have been
1911 disabled, provided that the SSLv2 protocol was not also disabled via
1914 <advisory url="/news/secadv/20160128.txt"/>
1915 <reported source="Nimrod Aviram and Sebastian Schinzel" date="20151226"/>
1917 <issue public="20150811">
1918 <impact severity="Low"/>
1919 <cve name="2015-1794"/>
1920 <affects base="1.0.2" version="1.0.2"/>
1921 <affects base="1.0.2" version="1.0.2a"/>
1922 <affects base="1.0.2" version="1.0.2b"/>
1923 <affects base="1.0.2" version="1.0.2c"/>
1924 <affects base="1.0.2" version="1.0.2d"/>
1925 <fixed base="1.0.2" version="1.0.2e" date="20151203"/>
1928 If a client receives a ServerKeyExchange for an anonymous DH ciphersuite with
1929 the value of p set to 0 then a seg fault can occur leading to a possible denial
1932 <advisory url="/news/secadv/20151203.txt"/>
1933 <reported source="Guy Leaver (Cisco)" date="20150803"/>
1935 <issue public="20151203">
1936 <cve name="2015-3193"/>
1937 <impact severity="Moderate"/>
1938 <affects base="1.0.2" version="1.0.2"/>
1939 <affects base="1.0.2" version="1.0.2a"/>
1940 <affects base="1.0.2" version="1.0.2b"/>
1941 <affects base="1.0.2" version="1.0.2c"/>
1942 <affects base="1.0.2" version="1.0.2d"/>
1943 <fixed base="1.0.2" version="1.0.2e" date="20151203"/>
1946 There is a carry propagating bug in the x86_64 Montgomery squaring procedure. No
1947 EC algorithms are affected. Analysis suggests that attacks against RSA and DSA
1948 as a result of this defect would be very difficult to perform and are not
1949 believed likely. Attacks against DH are considered just feasible (although very
1950 difficult) because most of the work necessary to deduce information
1951 about a private key may be performed offline. The amount of resources
1952 required for such an attack would be very significant and likely only
1953 accessible to a limited number of attackers. An attacker would
1954 additionally need online access to an unpatched system using the target
1955 private key in a scenario with persistent DH parameters and a private
1956 key that is shared between multiple clients. For example this can occur by
1957 default in OpenSSL DHE based SSL/TLS ciphersuites.
1959 <advisory url="/news/secadv/20151203.txt"/>
1960 <reported source="Hanno Böck" date="20150813"/>
1962 <issue public="20151203">
1963 <cve name="2015-3194"/>
1964 <impact severity="Moderate"/>
1965 <affects base="1.0.1" version="1.0.1"/>
1966 <affects base="1.0.1" version="1.0.1a"/>
1967 <affects base="1.0.1" version="1.0.1b"/>
1968 <affects base="1.0.1" version="1.0.1c"/>
1969 <affects base="1.0.1" version="1.0.1d"/>
1970 <affects base="1.0.1" version="1.0.1e"/>
1971 <affects base="1.0.1" version="1.0.1f"/>
1972 <affects base="1.0.1" version="1.0.1g"/>
1973 <affects base="1.0.1" version="1.0.1h"/>
1974 <affects base="1.0.1" version="1.0.1i"/>
1975 <affects base="1.0.1" version="1.0.1j"/>
1976 <affects base="1.0.1" version="1.0.1k"/>
1977 <affects base="1.0.1" version="1.0.1l"/>
1978 <affects base="1.0.1" version="1.0.1m"/>
1979 <affects base="1.0.1" version="1.0.1n"/>
1980 <affects base="1.0.1" version="1.0.1o"/>
1981 <affects base="1.0.1" version="1.0.1p"/>
1982 <affects base="1.0.2" version="1.0.2"/>
1983 <affects base="1.0.2" version="1.0.2a"/>
1984 <affects base="1.0.2" version="1.0.2b"/>
1985 <affects base="1.0.2" version="1.0.2c"/>
1986 <affects base="1.0.2" version="1.0.2d"/>
1987 <fixed base="1.0.2" version="1.0.2e" date="20151203"/>
1988 <fixed base="1.0.1" version="1.0.1q" date="20151203"/>
1991 The signature verification routines will crash with a NULL pointer dereference
1992 if presented with an ASN.1 signature using the RSA PSS algorithm and absent
1993 mask generation function parameter. Since these routines are used to verify
1994 certificate signature algorithms this can be used to crash any certificate
1995 verification operation and exploited in a DoS attack. Any application which
1996 performs certificate verification is vulnerable including OpenSSL clients and
1997 servers which enable client authentication.
1999 <advisory url="/news/secadv/20151203.txt"/>
2000 <reported source="Loïc Jonas Etienne (Qnective AG)" date="20150827"/>
2002 <issue public="20151203">
2003 <cve name="2015-3195"/>
2004 <impact severity="Moderate"/>
2005 <affects base="0.9.8" version="0.9.8"/>
2006 <affects base="0.9.8" version="0.9.8a"/>
2007 <affects base="0.9.8" version="0.9.8b"/>
2008 <affects base="0.9.8" version="0.9.8c"/>
2009 <affects base="0.9.8" version="0.9.8d"/>
2010 <affects base="0.9.8" version="0.9.8e"/>
2011 <affects base="0.9.8" version="0.9.8f"/>
2012 <affects base="0.9.8" version="0.9.8g"/>
2013 <affects base="0.9.8" version="0.9.8h"/>
2014 <affects base="0.9.8" version="0.9.8i"/>
2015 <affects base="0.9.8" version="0.9.8j"/>
2016 <affects base="0.9.8" version="0.9.8k"/>
2017 <affects base="0.9.8" version="0.9.8l"/>
2018 <affects base="0.9.8" version="0.9.8m"/>
2019 <affects base="0.9.8" version="0.9.8n"/>
2020 <affects base="0.9.8" version="0.9.8o"/>
2021 <affects base="0.9.8" version="0.9.8p"/>
2022 <affects base="0.9.8" version="0.9.8q"/>
2023 <affects base="0.9.8" version="0.9.8r"/>
2024 <affects base="0.9.8" version="0.9.8s"/>
2025 <affects base="0.9.8" version="0.9.8t"/>
2026 <affects base="0.9.8" version="0.9.8u"/>
2027 <affects base="0.9.8" version="0.9.8v"/>
2028 <affects base="0.9.8" version="0.9.8w"/>
2029 <affects base="0.9.8" version="0.9.8x"/>
2030 <affects base="0.9.8" version="0.9.8y"/>
2031 <affects base="0.9.8" version="0.9.8za"/>
2032 <affects base="0.9.8" version="0.9.8zb"/>
2033 <affects base="0.9.8" version="0.9.8zc"/>
2034 <affects base="0.9.8" version="0.9.8zd"/>
2035 <affects base="0.9.8" version="0.9.8ze"/>
2036 <affects base="0.9.8" version="0.9.8zf"/>
2037 <affects base="0.9.8" version="0.9.8zg"/>
2038 <affects base="1.0.0" version="1.0.0"/>
2039 <affects base="1.0.0" version="1.0.0a"/>
2040 <affects base="1.0.0" version="1.0.0b"/>
2041 <affects base="1.0.0" version="1.0.0c"/>
2042 <affects base="1.0.0" version="1.0.0d"/>
2043 <affects base="1.0.0" version="1.0.0e"/>
2044 <affects base="1.0.0" version="1.0.0f"/>
2045 <affects base="1.0.0" version="1.0.0g"/>
2046 <affects base="1.0.0" version="1.0.0h"/>
2047 <affects base="1.0.0" version="1.0.0i"/>
2048 <affects base="1.0.0" version="1.0.0j"/>
2049 <affects base="1.0.0" version="1.0.0k"/>
2050 <affects base="1.0.0" version="1.0.0l"/>
2051 <affects base="1.0.0" version="1.0.0m"/>
2052 <affects base="1.0.0" version="1.0.0n"/>
2053 <affects base="1.0.0" version="1.0.0o"/>
2054 <affects base="1.0.0" version="1.0.0p"/>
2055 <affects base="1.0.0" version="1.0.0q"/>
2056 <affects base="1.0.0" version="1.0.0r"/>
2057 <affects base="1.0.0" version="1.0.0s"/>
2058 <affects base="1.0.1" version="1.0.1"/>
2059 <affects base="1.0.1" version="1.0.1a"/>
2060 <affects base="1.0.1" version="1.0.1b"/>
2061 <affects base="1.0.1" version="1.0.1c"/>
2062 <affects base="1.0.1" version="1.0.1d"/>
2063 <affects base="1.0.1" version="1.0.1e"/>
2064 <affects base="1.0.1" version="1.0.1f"/>
2065 <affects base="1.0.1" version="1.0.1g"/>
2066 <affects base="1.0.1" version="1.0.1h"/>
2067 <affects base="1.0.1" version="1.0.1i"/>
2068 <affects base="1.0.1" version="1.0.1j"/>
2069 <affects base="1.0.1" version="1.0.1k"/>
2070 <affects base="1.0.1" version="1.0.1l"/>
2071 <affects base="1.0.1" version="1.0.1m"/>
2072 <affects base="1.0.1" version="1.0.1n"/>
2073 <affects base="1.0.1" version="1.0.1o"/>
2074 <affects base="1.0.1" version="1.0.1p"/>
2075 <affects base="1.0.2" version="1.0.2"/>
2076 <affects base="1.0.2" version="1.0.2a"/>
2077 <affects base="1.0.2" version="1.0.2b"/>
2078 <affects base="1.0.2" version="1.0.2c"/>
2079 <affects base="1.0.2" version="1.0.2d"/>
2080 <fixed base="1.0.2" version="1.0.2e" date="20151203"/>
2081 <fixed base="1.0.1" version="1.0.1q" date="20151203"/>
2082 <fixed base="1.0.0" version="1.0.0t" date="20151203"/>
2083 <fixed base="0.9.8" version="0.9.8zh" date="20151203"/>
2086 When presented with a malformed X509_ATTRIBUTE structure OpenSSL will leak
2087 memory. This structure is used by the PKCS#7 and CMS routines so any
2088 application which reads PKCS#7 or CMS data from untrusted sources is affected.
2089 SSL/TLS is not affected.
2091 <advisory url="/news/secadv/20151203.txt"/>
2092 <reported source="Adam Langley (Google/BoringSSL) using libFuzzer" date="20151109"/>
2094 <issue public="20151203">
2095 <cve name="2015-3196"/>
2096 <impact severity="Low"/>
2097 <affects base="1.0.0" version="1.0.0"/>
2098 <affects base="1.0.0" version="1.0.0a"/>
2099 <affects base="1.0.0" version="1.0.0b"/>
2100 <affects base="1.0.0" version="1.0.0c"/>
2101 <affects base="1.0.0" version="1.0.0d"/>
2102 <affects base="1.0.0" version="1.0.0e"/>
2103 <affects base="1.0.0" version="1.0.0f"/>
2104 <affects base="1.0.0" version="1.0.0g"/>
2105 <affects base="1.0.0" version="1.0.0h"/>
2106 <affects base="1.0.0" version="1.0.0i"/>
2107 <affects base="1.0.0" version="1.0.0j"/>
2108 <affects base="1.0.0" version="1.0.0k"/>
2109 <affects base="1.0.0" version="1.0.0l"/>
2110 <affects base="1.0.0" version="1.0.0m"/>
2111 <affects base="1.0.0" version="1.0.0n"/>
2112 <affects base="1.0.0" version="1.0.0o"/>
2113 <affects base="1.0.0" version="1.0.0p"/>
2114 <affects base="1.0.0" version="1.0.0q"/>
2115 <affects base="1.0.0" version="1.0.0r"/>
2116 <affects base="1.0.0" version="1.0.0s"/>
2117 <affects base="1.0.1" version="1.0.1"/>
2118 <affects base="1.0.1" version="1.0.1a"/>
2119 <affects base="1.0.1" version="1.0.1b"/>
2120 <affects base="1.0.1" version="1.0.1c"/>
2121 <affects base="1.0.1" version="1.0.1d"/>
2122 <affects base="1.0.1" version="1.0.1e"/>
2123 <affects base="1.0.1" version="1.0.1f"/>
2124 <affects base="1.0.1" version="1.0.1g"/>
2125 <affects base="1.0.1" version="1.0.1h"/>
2126 <affects base="1.0.1" version="1.0.1i"/>
2127 <affects base="1.0.1" version="1.0.1j"/>
2128 <affects base="1.0.1" version="1.0.1k"/>
2129 <affects base="1.0.1" version="1.0.1l"/>
2130 <affects base="1.0.1" version="1.0.1m"/>
2131 <affects base="1.0.1" version="1.0.1n"/>
2132 <affects base="1.0.1" version="1.0.1o"/>
2133 <affects base="1.0.2" version="1.0.2"/>
2134 <affects base="1.0.2" version="1.0.2a"/>
2135 <affects base="1.0.2" version="1.0.2b"/>
2136 <affects base="1.0.2" version="1.0.2c"/>
2137 <fixed base="1.0.2" version="1.0.2d" date="20150709"/>
2138 <fixed base="1.0.1" version="1.0.1p" date="20150709"/>
2139 <fixed base="1.0.0" version="1.0.0t" date="20151203"/>
2142 If PSK identity hints are received by a multi-threaded client then
2143 the values are wrongly updated in the parent SSL_CTX structure. This can
2144 result in a race condition potentially leading to a double free of the
2147 <advisory url="/news/secadv/20151203.txt"/>
2148 <reported source="Stephen Henson (OpenSSL)"/>
2151 <issue public="20150709">
2152 <cve name="2015-1793"/>
2153 <impact severity="High"/>
2154 <affects base="1.0.1" version="1.0.1n"/>
2155 <affects base="1.0.1" version="1.0.1o"/>
2156 <affects base="1.0.2" version="1.0.2b"/>
2157 <affects base="1.0.2" version="1.0.2c"/>
2158 <fixed base="1.0.2" version="1.0.2d" date="20150709"/>
2159 <fixed base="1.0.1" version="1.0.1p" date="20150709"/>
2162 An error in the implementation of the alternative certificate
2163 chain logic could allow an attacker to cause certain checks on
2164 untrusted certificates to be bypassed, such as the CA flag,
2165 enabling them to use a valid leaf certificate to act as a CA and
2166 "issue" an invalid certificate.
2168 <advisory url="/news/secadv/20150709.txt"/>
2169 <reported source="Adam Langley and David Benjamin (Google/BoringSSL)" date="20150624"/>
2171 <issue public="20150611">
2172 <cve name="2015-1788"/>
2173 <affects base="0.9.8" version="0.9.8"/>
2174 <affects base="0.9.8" version="0.9.8a"/>
2175 <affects base="0.9.8" version="0.9.8b"/>
2176 <affects base="0.9.8" version="0.9.8c"/>
2177 <affects base="0.9.8" version="0.9.8d"/>
2178 <affects base="0.9.8" version="0.9.8e"/>
2179 <affects base="0.9.8" version="0.9.8f"/>
2180 <affects base="0.9.8" version="0.9.8g"/>
2181 <affects base="0.9.8" version="0.9.8h"/>
2182 <affects base="0.9.8" version="0.9.8i"/>
2183 <affects base="0.9.8" version="0.9.8j"/>
2184 <affects base="0.9.8" version="0.9.8k"/>
2185 <affects base="0.9.8" version="0.9.8l"/>
2186 <affects base="0.9.8" version="0.9.8m"/>
2187 <affects base="0.9.8" version="0.9.8n"/>
2188 <affects base="0.9.8" version="0.9.8o"/>
2189 <affects base="0.9.8" version="0.9.8p"/>
2190 <affects base="0.9.8" version="0.9.8q"/>
2191 <affects base="0.9.8" version="0.9.8r"/>
2192 <affects base="1.0.0" version="1.0.0"/>
2193 <affects base="1.0.0" version="1.0.0a"/>
2194 <affects base="1.0.0" version="1.0.0b"/>
2195 <affects base="1.0.0" version="1.0.0c"/>
2196 <affects base="1.0.0" version="1.0.0d"/>
2197 <affects base="1.0.1" version="1.0.1"/>
2198 <affects base="1.0.1" version="1.0.1a"/>
2199 <affects base="1.0.1" version="1.0.1b"/>
2200 <affects base="1.0.1" version="1.0.1c"/>
2201 <affects base="1.0.1" version="1.0.1d"/>
2202 <affects base="1.0.1" version="1.0.1e"/>
2203 <affects base="1.0.1" version="1.0.1f"/>
2204 <affects base="1.0.1" version="1.0.1g"/>
2205 <affects base="1.0.1" version="1.0.1h"/>
2206 <affects base="1.0.1" version="1.0.1i"/>
2207 <affects base="1.0.1" version="1.0.1j"/>
2208 <affects base="1.0.1" version="1.0.1k"/>
2209 <affects base="1.0.1" version="1.0.1l"/>
2210 <affects base="1.0.1" version="1.0.1m"/>
2211 <affects base="1.0.2" version="1.0.2"/>
2212 <affects base="1.0.2" version="1.0.2a"/>
2213 <fixed base="1.0.2" version="1.0.2b" date="20150611"/>
2214 <fixed base="1.0.1" version="1.0.1n" date="20150611"/>
2215 <fixed base="1.0.0" version="1.0.0e" date="20110906"/>
2216 <fixed base="0.9.8" version="0.9.8s" date="20120104"/>
2219 When processing an ECParameters structure OpenSSL enters an infinite loop if
2220 the curve specified is over a specially malformed binary polynomial field.
2222 This can be used to perform denial of service against any
2223 system which processes public keys, certificate requests or
2224 certificates. This includes TLS clients and TLS servers with
2225 client authentication enabled.
2227 <advisory url="/news/secadv/20150611.txt"/>
2228 <reported source="Joseph Birr-Pixton" date="20150406"/>
2231 <issue public="20150611">
2232 <cve name="2015-1789"/>
2233 <impact severity="Moderate"/>
2234 <affects base="0.9.8" version="0.9.8"/>
2235 <affects base="0.9.8" version="0.9.8a"/>
2236 <affects base="0.9.8" version="0.9.8b"/>
2237 <affects base="0.9.8" version="0.9.8c"/>
2238 <affects base="0.9.8" version="0.9.8d"/>
2239 <affects base="0.9.8" version="0.9.8e"/>
2240 <affects base="0.9.8" version="0.9.8f"/>
2241 <affects base="0.9.8" version="0.9.8g"/>
2242 <affects base="0.9.8" version="0.9.8h"/>
2243 <affects base="0.9.8" version="0.9.8i"/>
2244 <affects base="0.9.8" version="0.9.8j"/>
2245 <affects base="0.9.8" version="0.9.8k"/>
2246 <affects base="0.9.8" version="0.9.8l"/>
2247 <affects base="0.9.8" version="0.9.8m"/>
2248 <affects base="0.9.8" version="0.9.8n"/>
2249 <affects base="0.9.8" version="0.9.8o"/>
2250 <affects base="0.9.8" version="0.9.8p"/>
2251 <affects base="0.9.8" version="0.9.8q"/>
2252 <affects base="0.9.8" version="0.9.8r"/>
2253 <affects base="0.9.8" version="0.9.8s"/>
2254 <affects base="0.9.8" version="0.9.8t"/>
2255 <affects base="0.9.8" version="0.9.8u"/>
2256 <affects base="0.9.8" version="0.9.8v"/>
2257 <affects base="0.9.8" version="0.9.8w"/>
2258 <affects base="0.9.8" version="0.9.8x"/>
2259 <affects base="0.9.8" version="0.9.8y"/>
2260 <affects base="0.9.8" version="0.9.8za"/>
2261 <affects base="0.9.8" version="0.9.8zb"/>
2262 <affects base="0.9.8" version="0.9.8zc"/>
2263 <affects base="0.9.8" version="0.9.8zd"/>
2264 <affects base="0.9.8" version="0.9.8ze"/>
2265 <affects base="0.9.8" version="0.9.8zf"/>
2266 <affects base="1.0.0" version="1.0.0"/>
2267 <affects base="1.0.0" version="1.0.0a"/>
2268 <affects base="1.0.0" version="1.0.0b"/>
2269 <affects base="1.0.0" version="1.0.0c"/>
2270 <affects base="1.0.0" version="1.0.0d"/>
2271 <affects base="1.0.0" version="1.0.0e"/>
2272 <affects base="1.0.0" version="1.0.0f"/>
2273 <affects base="1.0.0" version="1.0.0g"/>
2274 <affects base="1.0.0" version="1.0.0i"/>
2275 <affects base="1.0.0" version="1.0.0j"/>
2276 <affects base="1.0.0" version="1.0.0k"/>
2277 <affects base="1.0.0" version="1.0.0l"/>
2278 <affects base="1.0.0" version="1.0.0m"/>
2279 <affects base="1.0.0" version="1.0.0n"/>
2280 <affects base="1.0.0" version="1.0.0o"/>
2281 <affects base="1.0.0" version="1.0.0p"/>
2282 <affects base="1.0.0" version="1.0.0q"/>
2283 <affects base="1.0.0" version="1.0.0r"/>
2284 <affects base="1.0.1" version="1.0.1"/>
2285 <affects base="1.0.1" version="1.0.1a"/>
2286 <affects base="1.0.1" version="1.0.1b"/>
2287 <affects base="1.0.1" version="1.0.1c"/>
2288 <affects base="1.0.1" version="1.0.1d"/>
2289 <affects base="1.0.1" version="1.0.1e"/>
2290 <affects base="1.0.1" version="1.0.1f"/>
2291 <affects base="1.0.1" version="1.0.1g"/>
2292 <affects base="1.0.1" version="1.0.1h"/>
2293 <affects base="1.0.1" version="1.0.1i"/>
2294 <affects base="1.0.1" version="1.0.1j"/>
2295 <affects base="1.0.1" version="1.0.1k"/>
2296 <affects base="1.0.1" version="1.0.1l"/>
2297 <affects base="1.0.1" version="1.0.1m"/>
2298 <affects base="1.0.2" version="1.0.2"/>
2299 <affects base="1.0.2" version="1.0.2a"/>
2300 <fixed base="1.0.2" version="1.0.2b" date="20150611"/>
2301 <fixed base="1.0.1" version="1.0.1n" date="20150611"/>
2302 <fixed base="1.0.0" version="1.0.0s" date="20150611"/>
2303 <fixed base="0.9.8" version="0.9.8zg" date="20150611"/>
2306 X509_cmp_time does not properly check the length of the ASN1_TIME
2307 string and can read a few bytes out of bounds. In addition,
2308 X509_cmp_time accepts an arbitrary number of fractional seconds in the
2311 An attacker can use this to craft malformed certificates and CRLs of
2312 various sizes and potentially cause a segmentation fault, resulting in
2313 a DoS on applications that verify certificates or CRLs. TLS clients
2314 that verify CRLs are affected. TLS clients and servers with client
2315 authentication enabled may be affected if they use custom verification
2318 <advisory url="/news/secadv/20150611.txt"/>
2319 <reported source="Robert Święcki (Google Security Team)" date="20150408"/>
2320 <reported source="Hanno Böck" date="20150411"/>
2323 <issue public="20150611">
2324 <cve name="2015-1790"/>
2325 <impact severity="Moderate"/>
2326 <affects base="0.9.8" version="0.9.8"/>
2327 <affects base="0.9.8" version="0.9.8a"/>
2328 <affects base="0.9.8" version="0.9.8b"/>
2329 <affects base="0.9.8" version="0.9.8c"/>
2330 <affects base="0.9.8" version="0.9.8d"/>
2331 <affects base="0.9.8" version="0.9.8e"/>
2332 <affects base="0.9.8" version="0.9.8f"/>
2333 <affects base="0.9.8" version="0.9.8g"/>
2334 <affects base="0.9.8" version="0.9.8h"/>
2335 <affects base="0.9.8" version="0.9.8i"/>
2336 <affects base="0.9.8" version="0.9.8j"/>
2337 <affects base="0.9.8" version="0.9.8k"/>
2338 <affects base="0.9.8" version="0.9.8l"/>
2339 <affects base="0.9.8" version="0.9.8m"/>
2340 <affects base="0.9.8" version="0.9.8n"/>
2341 <affects base="0.9.8" version="0.9.8o"/>
2342 <affects base="0.9.8" version="0.9.8p"/>
2343 <affects base="0.9.8" version="0.9.8q"/>
2344 <affects base="0.9.8" version="0.9.8r"/>
2345 <affects base="0.9.8" version="0.9.8s"/>
2346 <affects base="0.9.8" version="0.9.8t"/>
2347 <affects base="0.9.8" version="0.9.8u"/>
2348 <affects base="0.9.8" version="0.9.8v"/>
2349 <affects base="0.9.8" version="0.9.8w"/>
2350 <affects base="0.9.8" version="0.9.8x"/>
2351 <affects base="0.9.8" version="0.9.8y"/>
2352 <affects base="0.9.8" version="0.9.8za"/>
2353 <affects base="0.9.8" version="0.9.8zb"/>
2354 <affects base="0.9.8" version="0.9.8zc"/>
2355 <affects base="0.9.8" version="0.9.8zd"/>
2356 <affects base="0.9.8" version="0.9.8ze"/>
2357 <affects base="0.9.8" version="0.9.8zf"/>
2358 <affects base="1.0.0" version="1.0.0"/>
2359 <affects base="1.0.0" version="1.0.0a"/>
2360 <affects base="1.0.0" version="1.0.0b"/>
2361 <affects base="1.0.0" version="1.0.0c"/>
2362 <affects base="1.0.0" version="1.0.0d"/>
2363 <affects base="1.0.0" version="1.0.0e"/>
2364 <affects base="1.0.0" version="1.0.0f"/>
2365 <affects base="1.0.0" version="1.0.0g"/>
2366 <affects base="1.0.0" version="1.0.0i"/>
2367 <affects base="1.0.0" version="1.0.0j"/>
2368 <affects base="1.0.0" version="1.0.0k"/>
2369 <affects base="1.0.0" version="1.0.0l"/>
2370 <affects base="1.0.0" version="1.0.0m"/>
2371 <affects base="1.0.0" version="1.0.0n"/>
2372 <affects base="1.0.0" version="1.0.0o"/>
2373 <affects base="1.0.0" version="1.0.0p"/>
2374 <affects base="1.0.0" version="1.0.0q"/>
2375 <affects base="1.0.0" version="1.0.0r"/>
2376 <affects base="1.0.1" version="1.0.1"/>
2377 <affects base="1.0.1" version="1.0.1a"/>
2378 <affects base="1.0.1" version="1.0.1b"/>
2379 <affects base="1.0.1" version="1.0.1c"/>
2380 <affects base="1.0.1" version="1.0.1d"/>
2381 <affects base="1.0.1" version="1.0.1e"/>
2382 <affects base="1.0.1" version="1.0.1f"/>
2383 <affects base="1.0.1" version="1.0.1g"/>
2384 <affects base="1.0.1" version="1.0.1h"/>
2385 <affects base="1.0.1" version="1.0.1i"/>
2386 <affects base="1.0.1" version="1.0.1j"/>
2387 <affects base="1.0.1" version="1.0.1k"/>
2388 <affects base="1.0.1" version="1.0.1l"/>
2389 <affects base="1.0.1" version="1.0.1m"/>
2390 <affects base="1.0.2" version="1.0.2"/>
2391 <affects base="1.0.2" version="1.0.2a"/>
2392 <fixed base="1.0.2" version="1.0.2b" date="20150611"/>
2393 <fixed base="1.0.1" version="1.0.1n" date="20150611"/>
2394 <fixed base="1.0.0" version="1.0.0s" date="20150611"/>
2395 <fixed base="0.9.8" version="0.9.8zg" date="20150611"/>
2398 The PKCS#7 parsing code does not handle missing inner EncryptedContent
2399 correctly. An attacker can craft malformed ASN.1-encoded PKCS#7 blobs
2400 with missing content and trigger a NULL pointer dereference on parsing.
2402 Applications that decrypt PKCS#7 data or otherwise parse PKCS#7
2403 structures from untrusted sources are affected. OpenSSL clients and
2404 servers are not affected.
2406 <advisory url="/news/secadv/20150611.txt"/>
2407 <reported source="Michal Zalewski (Google)" date="20150418"/>
2410 <issue public="20150611">
2411 <cve name="2015-1792"/>
2412 <impact severity="Moderate"/>
2413 <affects base="0.9.8" version="0.9.8"/>
2414 <affects base="0.9.8" version="0.9.8a"/>
2415 <affects base="0.9.8" version="0.9.8b"/>
2416 <affects base="0.9.8" version="0.9.8c"/>
2417 <affects base="0.9.8" version="0.9.8d"/>
2418 <affects base="0.9.8" version="0.9.8e"/>
2419 <affects base="0.9.8" version="0.9.8f"/>
2420 <affects base="0.9.8" version="0.9.8g"/>
2421 <affects base="0.9.8" version="0.9.8h"/>
2422 <affects base="0.9.8" version="0.9.8i"/>
2423 <affects base="0.9.8" version="0.9.8j"/>
2424 <affects base="0.9.8" version="0.9.8k"/>
2425 <affects base="0.9.8" version="0.9.8l"/>
2426 <affects base="0.9.8" version="0.9.8m"/>
2427 <affects base="0.9.8" version="0.9.8n"/>
2428 <affects base="0.9.8" version="0.9.8o"/>
2429 <affects base="0.9.8" version="0.9.8p"/>
2430 <affects base="0.9.8" version="0.9.8q"/>
2431 <affects base="0.9.8" version="0.9.8r"/>
2432 <affects base="0.9.8" version="0.9.8s"/>
2433 <affects base="0.9.8" version="0.9.8t"/>
2434 <affects base="0.9.8" version="0.9.8u"/>
2435 <affects base="0.9.8" version="0.9.8v"/>
2436 <affects base="0.9.8" version="0.9.8w"/>
2437 <affects base="0.9.8" version="0.9.8x"/>
2438 <affects base="0.9.8" version="0.9.8y"/>
2439 <affects base="0.9.8" version="0.9.8za"/>
2440 <affects base="0.9.8" version="0.9.8zb"/>
2441 <affects base="0.9.8" version="0.9.8zc"/>
2442 <affects base="0.9.8" version="0.9.8zd"/>
2443 <affects base="0.9.8" version="0.9.8ze"/>
2444 <affects base="0.9.8" version="0.9.8zf"/>
2445 <affects base="1.0.0" version="1.0.0"/>
2446 <affects base="1.0.0" version="1.0.0a"/>
2447 <affects base="1.0.0" version="1.0.0b"/>
2448 <affects base="1.0.0" version="1.0.0c"/>
2449 <affects base="1.0.0" version="1.0.0d"/>
2450 <affects base="1.0.0" version="1.0.0e"/>
2451 <affects base="1.0.0" version="1.0.0f"/>
2452 <affects base="1.0.0" version="1.0.0g"/>
2453 <affects base="1.0.0" version="1.0.0i"/>
2454 <affects base="1.0.0" version="1.0.0j"/>
2455 <affects base="1.0.0" version="1.0.0k"/>
2456 <affects base="1.0.0" version="1.0.0l"/>
2457 <affects base="1.0.0" version="1.0.0m"/>
2458 <affects base="1.0.0" version="1.0.0n"/>
2459 <affects base="1.0.0" version="1.0.0o"/>
2460 <affects base="1.0.0" version="1.0.0p"/>
2461 <affects base="1.0.0" version="1.0.0q"/>
2462 <affects base="1.0.0" version="1.0.0r"/>
2463 <affects base="1.0.1" version="1.0.1"/>
2464 <affects base="1.0.1" version="1.0.1a"/>
2465 <affects base="1.0.1" version="1.0.1b"/>
2466 <affects base="1.0.1" version="1.0.1c"/>
2467 <affects base="1.0.1" version="1.0.1d"/>
2468 <affects base="1.0.1" version="1.0.1e"/>
2469 <affects base="1.0.1" version="1.0.1f"/>
2470 <affects base="1.0.1" version="1.0.1g"/>
2471 <affects base="1.0.1" version="1.0.1h"/>
2472 <affects base="1.0.1" version="1.0.1i"/>
2473 <affects base="1.0.1" version="1.0.1j"/>
2474 <affects base="1.0.1" version="1.0.1k"/>
2475 <affects base="1.0.1" version="1.0.1l"/>
2476 <affects base="1.0.1" version="1.0.1m"/>
2477 <affects base="1.0.2" version="1.0.2"/>
2478 <affects base="1.0.2" version="1.0.2a"/>
2479 <fixed base="1.0.2" version="1.0.2b" date="20150611"/>
2480 <fixed base="1.0.1" version="1.0.1n" date="20150611"/>
2481 <fixed base="1.0.0" version="1.0.0s" date="20150611"/>
2482 <fixed base="0.9.8" version="0.9.8zg" date="20150611"/>
2485 When verifying a signedData message the CMS code can enter an infinite loop
2486 if presented with an unknown hash function OID.
2488 This can be used to perform denial of service against any system which
2489 verifies signedData messages using the CMS code.
2491 <advisory url="/news/secadv/20150611.txt"/>
2492 <reported source="Johannes Bauer" date="20150331"/>
2495 <issue public="20150602">
2496 <cve name="2015-1791"/>
2497 <impact severity="Low"/>
2498 <affects base="0.9.8" version="0.9.8"/>
2499 <affects base="0.9.8" version="0.9.8a"/>
2500 <affects base="0.9.8" version="0.9.8b"/>
2501 <affects base="0.9.8" version="0.9.8c"/>
2502 <affects base="0.9.8" version="0.9.8d"/>
2503 <affects base="0.9.8" version="0.9.8e"/>
2504 <affects base="0.9.8" version="0.9.8f"/>
2505 <affects base="0.9.8" version="0.9.8g"/>
2506 <affects base="0.9.8" version="0.9.8h"/>
2507 <affects base="0.9.8" version="0.9.8i"/>
2508 <affects base="0.9.8" version="0.9.8j"/>
2509 <affects base="0.9.8" version="0.9.8k"/>
2510 <affects base="0.9.8" version="0.9.8l"/>
2511 <affects base="0.9.8" version="0.9.8m"/>
2512 <affects base="0.9.8" version="0.9.8n"/>
2513 <affects base="0.9.8" version="0.9.8o"/>
2514 <affects base="0.9.8" version="0.9.8p"/>
2515 <affects base="0.9.8" version="0.9.8q"/>
2516 <affects base="0.9.8" version="0.9.8r"/>
2517 <affects base="0.9.8" version="0.9.8s"/>
2518 <affects base="0.9.8" version="0.9.8t"/>
2519 <affects base="0.9.8" version="0.9.8u"/>
2520 <affects base="0.9.8" version="0.9.8v"/>
2521 <affects base="0.9.8" version="0.9.8w"/>
2522 <affects base="0.9.8" version="0.9.8x"/>
2523 <affects base="0.9.8" version="0.9.8y"/>
2524 <affects base="0.9.8" version="0.9.8za"/>
2525 <affects base="0.9.8" version="0.9.8zb"/>
2526 <affects base="0.9.8" version="0.9.8zc"/>
2527 <affects base="0.9.8" version="0.9.8zd"/>
2528 <affects base="0.9.8" version="0.9.8ze"/>
2529 <affects base="0.9.8" version="0.9.8zf"/>
2530 <affects base="1.0.0" version="1.0.0"/>
2531 <affects base="1.0.0" version="1.0.0a"/>
2532 <affects base="1.0.0" version="1.0.0b"/>
2533 <affects base="1.0.0" version="1.0.0c"/>
2534 <affects base="1.0.0" version="1.0.0d"/>
2535 <affects base="1.0.0" version="1.0.0e"/>
2536 <affects base="1.0.0" version="1.0.0f"/>
2537 <affects base="1.0.0" version="1.0.0g"/>
2538 <affects base="1.0.0" version="1.0.0i"/>
2539 <affects base="1.0.0" version="1.0.0j"/>
2540 <affects base="1.0.0" version="1.0.0k"/>
2541 <affects base="1.0.0" version="1.0.0l"/>
2542 <affects base="1.0.0" version="1.0.0m"/>
2543 <affects base="1.0.0" version="1.0.0n"/>
2544 <affects base="1.0.0" version="1.0.0o"/>
2545 <affects base="1.0.0" version="1.0.0p"/>
2546 <affects base="1.0.0" version="1.0.0q"/>
2547 <affects base="1.0.0" version="1.0.0r"/>
2548 <affects base="1.0.1" version="1.0.1"/>
2549 <affects base="1.0.1" version="1.0.1a"/>
2550 <affects base="1.0.1" version="1.0.1b"/>
2551 <affects base="1.0.1" version="1.0.1c"/>
2552 <affects base="1.0.1" version="1.0.1d"/>
2553 <affects base="1.0.1" version="1.0.1e"/>
2554 <affects base="1.0.1" version="1.0.1f"/>
2555 <affects base="1.0.1" version="1.0.1g"/>
2556 <affects base="1.0.1" version="1.0.1h"/>
2557 <affects base="1.0.1" version="1.0.1i"/>
2558 <affects base="1.0.1" version="1.0.1j"/>
2559 <affects base="1.0.1" version="1.0.1k"/>
2560 <affects base="1.0.1" version="1.0.1l"/>
2561 <affects base="1.0.1" version="1.0.1m"/>
2562 <affects base="1.0.2" version="1.0.2"/>
2563 <affects base="1.0.2" version="1.0.2a"/>
2564 <fixed base="1.0.2" version="1.0.2b" date="20150611"/>
2565 <fixed base="1.0.1" version="1.0.1n" date="20150611"/>
2566 <fixed base="1.0.0" version="1.0.0s" date="20150611"/>
2567 <fixed base="0.9.8" version="0.9.8zg" date="20150611"/>
2570 If a NewSessionTicket is received by a multi-threaded client when attempting to
2571 reuse a previous ticket then a race condition can occur potentially leading to
2572 a double free of the ticket data.
2574 <advisory url="/news/secadv/20150611.txt"/>
2575 <reported source="Emilia Käsper (OpenSSL)"/>
2578 <issue public="20150611">
2579 <cve name="2014-8176"/>
2580 <impact severity="Moderate"/>
2581 <affects base="0.9.8" version="0.9.8"/>
2582 <affects base="0.9.8" version="0.9.8a"/>
2583 <affects base="0.9.8" version="0.9.8b"/>
2584 <affects base="0.9.8" version="0.9.8c"/>
2585 <affects base="0.9.8" version="0.9.8d"/>
2586 <affects base="0.9.8" version="0.9.8e"/>
2587 <affects base="0.9.8" version="0.9.8f"/>
2588 <affects base="0.9.8" version="0.9.8g"/>
2589 <affects base="0.9.8" version="0.9.8h"/>
2590 <affects base="0.9.8" version="0.9.8i"/>
2591 <affects base="0.9.8" version="0.9.8j"/>
2592 <affects base="0.9.8" version="0.9.8k"/>
2593 <affects base="0.9.8" version="0.9.8l"/>
2594 <affects base="0.9.8" version="0.9.8m"/>
2595 <affects base="0.9.8" version="0.9.8n"/>
2596 <affects base="0.9.8" version="0.9.8o"/>
2597 <affects base="0.9.8" version="0.9.8p"/>
2598 <affects base="0.9.8" version="0.9.8q"/>
2599 <affects base="0.9.8" version="0.9.8r"/>
2600 <affects base="0.9.8" version="0.9.8s"/>
2601 <affects base="0.9.8" version="0.9.8t"/>
2602 <affects base="0.9.8" version="0.9.8u"/>
2603 <affects base="0.9.8" version="0.9.8v"/>
2604 <affects base="0.9.8" version="0.9.8w"/>
2605 <affects base="0.9.8" version="0.9.8x"/>
2606 <affects base="0.9.8" version="0.9.8y"/>
2607 <affects base="1.0.0" version="1.0.0"/>
2608 <affects base="1.0.0" version="1.0.0a"/>
2609 <affects base="1.0.0" version="1.0.0b"/>
2610 <affects base="1.0.0" version="1.0.0c"/>
2611 <affects base="1.0.0" version="1.0.0d"/>
2612 <affects base="1.0.0" version="1.0.0e"/>
2613 <affects base="1.0.0" version="1.0.0f"/>
2614 <affects base="1.0.0" version="1.0.0g"/>
2615 <affects base="1.0.0" version="1.0.0i"/>
2616 <affects base="1.0.0" version="1.0.0j"/>
2617 <affects base="1.0.0" version="1.0.0k"/>
2618 <affects base="1.0.0" version="1.0.0l"/>
2619 <affects base="1.0.1" version="1.0.1"/>
2620 <affects base="1.0.1" version="1.0.1a"/>
2621 <affects base="1.0.1" version="1.0.1b"/>
2622 <affects base="1.0.1" version="1.0.1c"/>
2623 <affects base="1.0.1" version="1.0.1d"/>
2624 <affects base="1.0.1" version="1.0.1e"/>
2625 <affects base="1.0.1" version="1.0.1f"/>
2626 <affects base="1.0.1" version="1.0.1g"/>
2627 <fixed base="1.0.1" version="1.0.1h" date="20140605"/>
2628 <fixed base="1.0.0" version="1.0.0m" date="20140605"/>
2629 <fixed base="0.9.8" version="0.9.8za" date="20140605"/>
2631 This vulnerability does not affect current versions of OpenSSL. It
2632 existed in previous OpenSSL versions and was fixed in June 2014.
2634 If a DTLS peer receives application data between the ChangeCipherSpec
2635 and Finished messages, buffering of such data may cause an invalid
2636 free, resulting in a segmentation fault or potentially, memory
2639 <advisory url="/news/secadv/20150611.txt"/>
2640 <reported source="Praveen Kariyanahalli, and subsequently by Ivan Fratric and Felix Groebert (Google)" date="20140328"/>
2642 <issue public="20150319">
2643 <impact severity="High"/>
2644 <cve name="2015-0291"/>
2645 <affects base="1.0.2" version="1.0.2"/>
2646 <fixed base="1.0.2" version="1.0.2a" date="20150319"/>
2649 ClientHello sigalgs DoS. If a client connects to an OpenSSL 1.0.2 server and renegotiates with an
2650 invalid signature algorithms extension a NULL pointer dereference will occur.
2651 This can be exploited in a DoS attack against the server.
2653 <advisory url="/news/secadv/20150319.txt"/>
2654 <reported source=" David Ramos (Stanford University)" date="20150226"/>
2657 <issue public="20150319">
2658 <cve name="2015-0290"/>
2659 <impact severity="Moderate"/>
2660 <affects base="1.0.2" version="1.0.2"/>
2661 <fixed base="1.0.2" version="1.0.2a" date="20150319"/>
2664 Multiblock corrupted pointer.
2665 OpenSSL 1.0.2 introduced the "multiblock" performance improvement. This feature
2666 only applies on 64 bit x86 architecture platforms that support AES NI
2667 instructions. A defect in the implementation of "multiblock" can cause OpenSSL's
2668 internal write buffer to become incorrectly set to NULL when using non-blocking
2669 IO. Typically, when the user application is using a socket BIO for writing, this
2670 will only result in a failed connection. However if some other BIO is used then
2671 it is likely that a segmentation fault will be triggered, thus enabling a
2672 potential DoS attack.
2674 <advisory url="/news/secadv/20150319.txt"/>
2675 <reported source="Daniel Danner and Rainer Mueller" date="20150213"/>
2678 <issue public="20150319">
2679 <cve name="2015-0207"/>
2680 <impact severity="Moderate"/>
2681 <affects base="1.0.2" version="1.0.2"/>
2682 <fixed base="1.0.2" version="1.0.2a" date="20150319"/>
2685 Segmentation fault in DTLSv1_listen.
2686 A defect in the implementation of DTLSv1_listen means that state is preserved in
2687 the SSL object from one invocation to the next that can lead to a segmentation
2688 fault. Errors processing the initial ClientHello can trigger this scenario. An
2689 example of such an error could be that a DTLS1.0 only client is attempting to
2690 connect to a DTLS1.2 only server.
2692 <advisory url="/news/secadv/20150319.txt"/>
2693 <reported source="Per Allansson" date="20150127"/>
2696 <issue public="20150319">
2697 <cve name="2015-0286"/>
2698 <impact severity="Moderate"/>
2699 <affects base="0.9.8" version="0.9.8zd"/>
2700 <affects base="0.9.8" version="0.9.8ze"/>
2701 <affects base="1.0.0" version="1.0.0"/>
2702 <affects base="1.0.0" version="1.0.0a"/>
2703 <affects base="1.0.0" version="1.0.0b"/>
2704 <affects base="1.0.0" version="1.0.0c"/>
2705 <affects base="1.0.0" version="1.0.0d"/>
2706 <affects base="1.0.0" version="1.0.0e"/>
2707 <affects base="1.0.0" version="1.0.0f"/>
2708 <affects base="1.0.0" version="1.0.0g"/>
2709 <affects base="1.0.0" version="1.0.0i"/>
2710 <affects base="1.0.0" version="1.0.0j"/>
2711 <affects base="1.0.0" version="1.0.0k"/>
2712 <affects base="1.0.0" version="1.0.0l"/>
2713 <affects base="1.0.0" version="1.0.0m"/>
2714 <affects base="1.0.0" version="1.0.0n"/>
2715 <affects base="1.0.0" version="1.0.0o"/>
2716 <affects base="1.0.0" version="1.0.0p"/>
2717 <affects base="1.0.0" version="1.0.0q"/>
2718 <affects base="1.0.1" version="1.0.1"/>
2719 <affects base="1.0.1" version="1.0.1a"/>
2720 <affects base="1.0.1" version="1.0.1b"/>
2721 <affects base="1.0.1" version="1.0.1c"/>
2722 <affects base="1.0.1" version="1.0.1d"/>
2723 <affects base="1.0.1" version="1.0.1e"/>
2724 <affects base="1.0.1" version="1.0.1f"/>
2725 <affects base="1.0.1" version="1.0.1g"/>
2726 <affects base="1.0.1" version="1.0.1h"/>
2727 <affects base="1.0.1" version="1.0.1i"/>
2728 <affects base="1.0.1" version="1.0.1j"/>
2729 <affects base="1.0.1" version="1.0.1k"/>
2730 <affects base="1.0.1" version="1.0.1l"/>
2731 <affects base="1.0.2" version="1.0.2"/>
2732 <fixed base="1.0.2" version="1.0.2a" date="20150319"/>
2733 <fixed base="1.0.1" version="1.0.1m" date="20150319"/>
2734 <fixed base="1.0.0" version="1.0.0r" date="20150319"/>
2735 <fixed base="0.9.8" version="0.9.8zf" date="20150319"/>
2738 Segmentation fault in ASN1_TYPE_cmp.
2739 The function ASN1_TYPE_cmp will crash with an invalid read if an attempt is
2740 made to compare ASN.1 boolean types. Since ASN1_TYPE_cmp is used to check
2741 certificate signature algorithm consistency this can be used to crash any
2742 certificate verification operation and exploited in a DoS attack. Any
2743 application which performs certificate verification is vulnerable including
2744 OpenSSL clients and servers which enable client authentication.
2746 <advisory url="/news/secadv/20150319.txt"/>
2747 <reported source="Stephen Henson (OpenSSL development team)"/>
2750 <issue public="20150319">
2751 <cve name="2015-0208"/>
2752 <impact severity="Moderate"/>
2753 <affects base="1.0.2" version="1.0.2"/>
2754 <fixed base="1.0.2" version="1.0.2a" date="20150319"/>
2757 Segmentation fault for invalid PSS parameters.
2758 The signature verification routines will crash with a NULL pointer
2759 dereference if presented with an ASN.1 signature using the RSA PSS
2760 algorithm and invalid parameters. Since these routines are used to verify
2761 certificate signature algorithms this can be used to crash any
2762 certificate verification operation and exploited in a DoS attack. Any
2763 application which performs certificate verification is vulnerable including
2764 OpenSSL clients and servers which enable client authentication.
2766 <advisory url="/news/secadv/20150319.txt"/>
2767 <reported source="Brian Carpenter" date="20150131"/>
2770 <issue public="20150319">
2771 <cve name="2015-0287"/>
2772 <impact severity="Moderate"/>
2773 <affects base="0.9.8" version="0.9.8"/>
2774 <affects base="0.9.8" version="0.9.8a"/>
2775 <affects base="0.9.8" version="0.9.8b"/>
2776 <affects base="0.9.8" version="0.9.8c"/>
2777 <affects base="0.9.8" version="0.9.8d"/>
2778 <affects base="0.9.8" version="0.9.8e"/>
2779 <affects base="0.9.8" version="0.9.8f"/>
2780 <affects base="0.9.8" version="0.9.8g"/>
2781 <affects base="0.9.8" version="0.9.8h"/>
2782 <affects base="0.9.8" version="0.9.8i"/>
2783 <affects base="0.9.8" version="0.9.8j"/>
2784 <affects base="0.9.8" version="0.9.8k"/>
2785 <affects base="0.9.8" version="0.9.8l"/>
2786 <affects base="0.9.8" version="0.9.8m"/>
2787 <affects base="0.9.8" version="0.9.8n"/>
2788 <affects base="0.9.8" version="0.9.8o"/>
2789 <affects base="0.9.8" version="0.9.8p"/>
2790 <affects base="0.9.8" version="0.9.8q"/>
2791 <affects base="0.9.8" version="0.9.8r"/>
2792 <affects base="0.9.8" version="0.9.8s"/>
2793 <affects base="0.9.8" version="0.9.8t"/>
2794 <affects base="0.9.8" version="0.9.8u"/>
2795 <affects base="0.9.8" version="0.9.8v"/>
2796 <affects base="0.9.8" version="0.9.8w"/>
2797 <affects base="0.9.8" version="0.9.8x"/>
2798 <affects base="0.9.8" version="0.9.8y"/>
2799 <affects base="0.9.8" version="0.9.8za"/>
2800 <affects base="0.9.8" version="0.9.8zb"/>
2801 <affects base="0.9.8" version="0.9.8zc"/>
2802 <affects base="0.9.8" version="0.9.8zd"/>
2803 <affects base="0.9.8" version="0.9.8ze"/>
2804 <affects base="1.0.0" version="1.0.0"/>
2805 <affects base="1.0.0" version="1.0.0a"/>
2806 <affects base="1.0.0" version="1.0.0b"/>
2807 <affects base="1.0.0" version="1.0.0c"/>
2808 <affects base="1.0.0" version="1.0.0d"/>
2809 <affects base="1.0.0" version="1.0.0e"/>
2810 <affects base="1.0.0" version="1.0.0f"/>
2811 <affects base="1.0.0" version="1.0.0g"/>
2812 <affects base="1.0.0" version="1.0.0i"/>
2813 <affects base="1.0.0" version="1.0.0j"/>
2814 <affects base="1.0.0" version="1.0.0k"/>
2815 <affects base="1.0.0" version="1.0.0l"/>
2816 <affects base="1.0.0" version="1.0.0m"/>
2817 <affects base="1.0.0" version="1.0.0n"/>
2818 <affects base="1.0.0" version="1.0.0o"/>
2819 <affects base="1.0.0" version="1.0.0p"/>
2820 <affects base="1.0.0" version="1.0.0q"/>
2821 <affects base="1.0.1" version="1.0.1"/>
2822 <affects base="1.0.1" version="1.0.1a"/>
2823 <affects base="1.0.1" version="1.0.1b"/>
2824 <affects base="1.0.1" version="1.0.1c"/>
2825 <affects base="1.0.1" version="1.0.1d"/>
2826 <affects base="1.0.1" version="1.0.1e"/>
2827 <affects base="1.0.1" version="1.0.1f"/>
2828 <affects base="1.0.1" version="1.0.1g"/>
2829 <affects base="1.0.1" version="1.0.1h"/>
2830 <affects base="1.0.1" version="1.0.1i"/>
2831 <affects base="1.0.1" version="1.0.1j"/>
2832 <affects base="1.0.1" version="1.0.1k"/>
2833 <affects base="1.0.1" version="1.0.1l"/>
2834 <affects base="1.0.2" version="1.0.2"/>
2835 <fixed base="1.0.2" version="1.0.2a" date="20150319"/>
2836 <fixed base="1.0.1" version="1.0.1m" date="20150319"/>
2837 <fixed base="1.0.0" version="1.0.0r" date="20150319"/>
2838 <fixed base="0.9.8" version="0.9.8zf" date="20150319"/>
2841 ASN.1 structure reuse memory corruption.
2842 Reusing a structure in ASN.1 parsing may allow an attacker to cause
2843 memory corruption via an invalid write. Such reuse is and has been
2844 strongly discouraged and is believed to be rare.
2846 <advisory url="/news/secadv/20150319.txt"/>
2847 <reported source="Emilia Käsper (OpenSSL development team)"/>
2850 <issue public="20150319">
2851 <cve name="2015-0289"/>
2852 <impact severity="Moderate"/>
2853 <affects base="0.9.8" version="0.9.8"/>
2854 <affects base="0.9.8" version="0.9.8a"/>
2855 <affects base="0.9.8" version="0.9.8b"/>
2856 <affects base="0.9.8" version="0.9.8c"/>
2857 <affects base="0.9.8" version="0.9.8d"/>
2858 <affects base="0.9.8" version="0.9.8e"/>
2859 <affects base="0.9.8" version="0.9.8f"/>
2860 <affects base="0.9.8" version="0.9.8g"/>
2861 <affects base="0.9.8" version="0.9.8h"/>
2862 <affects base="0.9.8" version="0.9.8i"/>
2863 <affects base="0.9.8" version="0.9.8j"/>
2864 <affects base="0.9.8" version="0.9.8k"/>
2865 <affects base="0.9.8" version="0.9.8l"/>
2866 <affects base="0.9.8" version="0.9.8m"/>
2867 <affects base="0.9.8" version="0.9.8n"/>
2868 <affects base="0.9.8" version="0.9.8o"/>
2869 <affects base="0.9.8" version="0.9.8p"/>
2870 <affects base="0.9.8" version="0.9.8q"/>
2871 <affects base="0.9.8" version="0.9.8r"/>
2872 <affects base="0.9.8" version="0.9.8s"/>
2873 <affects base="0.9.8" version="0.9.8t"/>
2874 <affects base="0.9.8" version="0.9.8u"/>
2875 <affects base="0.9.8" version="0.9.8v"/>
2876 <affects base="0.9.8" version="0.9.8w"/>
2877 <affects base="0.9.8" version="0.9.8x"/>
2878 <affects base="0.9.8" version="0.9.8y"/>
2879 <affects base="0.9.8" version="0.9.8za"/>
2880 <affects base="0.9.8" version="0.9.8zb"/>
2881 <affects base="0.9.8" version="0.9.8zc"/>
2882 <affects base="0.9.8" version="0.9.8zd"/>
2883 <affects base="0.9.8" version="0.9.8ze"/>
2884 <affects base="1.0.0" version="1.0.0"/>
2885 <affects base="1.0.0" version="1.0.0a"/>
2886 <affects base="1.0.0" version="1.0.0b"/>
2887 <affects base="1.0.0" version="1.0.0c"/>
2888 <affects base="1.0.0" version="1.0.0d"/>
2889 <affects base="1.0.0" version="1.0.0e"/>
2890 <affects base="1.0.0" version="1.0.0f"/>
2891 <affects base="1.0.0" version="1.0.0g"/>
2892 <affects base="1.0.0" version="1.0.0i"/>
2893 <affects base="1.0.0" version="1.0.0j"/>
2894 <affects base="1.0.0" version="1.0.0k"/>
2895 <affects base="1.0.0" version="1.0.0l"/>
2896 <affects base="1.0.0" version="1.0.0m"/>
2897 <affects base="1.0.0" version="1.0.0n"/>
2898 <affects base="1.0.0" version="1.0.0o"/>
2899 <affects base="1.0.0" version="1.0.0p"/>
2900 <affects base="1.0.0" version="1.0.0q"/>
2901 <affects base="1.0.1" version="1.0.1"/>
2902 <affects base="1.0.1" version="1.0.1a"/>
2903 <affects base="1.0.1" version="1.0.1b"/>
2904 <affects base="1.0.1" version="1.0.1c"/>
2905 <affects base="1.0.1" version="1.0.1d"/>
2906 <affects base="1.0.1" version="1.0.1e"/>
2907 <affects base="1.0.1" version="1.0.1f"/>
2908 <affects base="1.0.1" version="1.0.1g"/>
2909 <affects base="1.0.1" version="1.0.1h"/>
2910 <affects base="1.0.1" version="1.0.1i"/>
2911 <affects base="1.0.1" version="1.0.1j"/>
2912 <affects base="1.0.1" version="1.0.1k"/>
2913 <affects base="1.0.1" version="1.0.1l"/>
2914 <affects base="1.0.2" version="1.0.2"/>
2915 <fixed base="1.0.2" version="1.0.2a" date="20150319"/>
2916 <fixed base="1.0.1" version="1.0.1m" date="20150319"/>
2917 <fixed base="1.0.0" version="1.0.0r" date="20150319"/>
2918 <fixed base="0.9.8" version="0.9.8zf" date="20150319"/>
2921 PKCS#7 NULL pointer dereference.
2922 The PKCS#7 parsing code does not handle missing outer ContentInfo correctly.
2923 An attacker can craft malformed ASN.1-encoded PKCS#7 blobs with
2924 missing content and trigger a NULL pointer dereference on parsing.
2925 Applications that verify PKCS#7 signatures, decrypt PKCS#7 data or
2926 otherwise parse PKCS#7 structures from untrusted sources are
2927 affected. OpenSSL clients and servers are not affected.
2929 <advisory url="/news/secadv/20150319.txt"/>
2930 <reported source="Michal Zalewski (Google)" date="20150216"/>
2933 <issue public="20150319">
2934 <cve name="2015-0292"/>
2935 <impact severity="Moderate"/>
2936 <affects base="0.9.8" version="0.9.8"/>
2937 <affects base="0.9.8" version="0.9.8a"/>
2938 <affects base="0.9.8" version="0.9.8b"/>
2939 <affects base="0.9.8" version="0.9.8c"/>
2940 <affects base="0.9.8" version="0.9.8d"/>
2941 <affects base="0.9.8" version="0.9.8e"/>
2942 <affects base="0.9.8" version="0.9.8f"/>
2943 <affects base="0.9.8" version="0.9.8g"/>
2944 <affects base="0.9.8" version="0.9.8h"/>
2945 <affects base="0.9.8" version="0.9.8i"/>
2946 <affects base="0.9.8" version="0.9.8j"/>
2947 <affects base="0.9.8" version="0.9.8k"/>
2948 <affects base="0.9.8" version="0.9.8l"/>
2949 <affects base="0.9.8" version="0.9.8m"/>
2950 <affects base="0.9.8" version="0.9.8n"/>
2951 <affects base="0.9.8" version="0.9.8o"/>
2952 <affects base="0.9.8" version="0.9.8p"/>
2953 <affects base="0.9.8" version="0.9.8q"/>
2954 <affects base="0.9.8" version="0.9.8r"/>
2955 <affects base="0.9.8" version="0.9.8s"/>
2956 <affects base="0.9.8" version="0.9.8t"/>
2957 <affects base="0.9.8" version="0.9.8u"/>
2958 <affects base="0.9.8" version="0.9.8v"/>
2959 <affects base="0.9.8" version="0.9.8w"/>
2960 <affects base="0.9.8" version="0.9.8x"/>
2961 <affects base="0.9.8" version="0.9.8y"/>
2962 <affects base="1.0.0" version="1.0.0"/>
2963 <affects base="1.0.0" version="1.0.0a"/>
2964 <affects base="1.0.0" version="1.0.0b"/>
2965 <affects base="1.0.0" version="1.0.0c"/>
2966 <affects base="1.0.0" version="1.0.0d"/>
2967 <affects base="1.0.0" version="1.0.0e"/>
2968 <affects base="1.0.0" version="1.0.0f"/>
2969 <affects base="1.0.0" version="1.0.0g"/>
2970 <affects base="1.0.0" version="1.0.0i"/>
2971 <affects base="1.0.0" version="1.0.0j"/>
2972 <affects base="1.0.0" version="1.0.0k"/>
2973 <affects base="1.0.0" version="1.0.0l"/>
2974 <affects base="1.0.1" version="1.0.1"/>
2975 <affects base="1.0.1" version="1.0.1a"/>
2976 <affects base="1.0.1" version="1.0.1b"/>
2977 <affects base="1.0.1" version="1.0.1c"/>
2978 <affects base="1.0.1" version="1.0.1d"/>
2979 <affects base="1.0.1" version="1.0.1e"/>
2980 <affects base="1.0.1" version="1.0.1f"/>
2981 <affects base="1.0.1" version="1.0.1g"/>
2982 <fixed base="1.0.1" version="1.0.1h" date="20140605"/>
2983 <fixed base="1.0.0" version="1.0.0m" date="20140605"/>
2984 <fixed base="0.9.8" version="0.9.8za" date="20140605"/>
2987 A vulnerability existed in previous versions of OpenSSL related to the
2988 processing of base64 encoded data. Any code path that reads base64 data from an
2989 untrusted source could be affected (such as the PEM processing routines).
2990 Maliciously crafted base 64 data could trigger a segmenation fault or memory
2993 <advisory url="/news/secadv/20150319.txt"/>
2994 <reported source="Robert Dugal, also David Ramos, also Huzaifa Sidhpurwala (Red Hat)"/>
2997 <issue public="20150319">
2998 <cve name="2015-0293"/>
2999 <impact severity="Moderate"/>
3000 <affects base="0.9.8" version="0.9.8"/>
3001 <affects base="0.9.8" version="0.9.8a"/>
3002 <affects base="0.9.8" version="0.9.8b"/>
3003 <affects base="0.9.8" version="0.9.8c"/>
3004 <affects base="0.9.8" version="0.9.8d"/>
3005 <affects base="0.9.8" version="0.9.8e"/>
3006 <affects base="0.9.8" version="0.9.8f"/>
3007 <affects base="0.9.8" version="0.9.8g"/>
3008 <affects base="0.9.8" version="0.9.8h"/>
3009 <affects base="0.9.8" version="0.9.8i"/>
3010 <affects base="0.9.8" version="0.9.8j"/>
3011 <affects base="0.9.8" version="0.9.8k"/>
3012 <affects base="0.9.8" version="0.9.8l"/>
3013 <affects base="0.9.8" version="0.9.8m"/>
3014 <affects base="0.9.8" version="0.9.8n"/>
3015 <affects base="0.9.8" version="0.9.8o"/>
3016 <affects base="0.9.8" version="0.9.8p"/>
3017 <affects base="0.9.8" version="0.9.8q"/>
3018 <affects base="0.9.8" version="0.9.8r"/>
3019 <affects base="0.9.8" version="0.9.8s"/>
3020 <affects base="0.9.8" version="0.9.8t"/>
3021 <affects base="0.9.8" version="0.9.8u"/>
3022 <affects base="0.9.8" version="0.9.8v"/>
3023 <affects base="0.9.8" version="0.9.8w"/>
3024 <affects base="0.9.8" version="0.9.8x"/>
3025 <affects base="0.9.8" version="0.9.8y"/>
3026 <affects base="0.9.8" version="0.9.8za"/>
3027 <affects base="0.9.8" version="0.9.8zb"/>
3028 <affects base="0.9.8" version="0.9.8zc"/>
3029 <affects base="0.9.8" version="0.9.8zd"/>
3030 <affects base="0.9.8" version="0.9.8ze"/>
3031 <affects base="1.0.0" version="1.0.0"/>
3032 <affects base="1.0.0" version="1.0.0a"/>
3033 <affects base="1.0.0" version="1.0.0b"/>
3034 <affects base="1.0.0" version="1.0.0c"/>
3035 <affects base="1.0.0" version="1.0.0d"/>
3036 <affects base="1.0.0" version="1.0.0e"/>
3037 <affects base="1.0.0" version="1.0.0f"/>
3038 <affects base="1.0.0" version="1.0.0g"/>
3039 <affects base="1.0.0" version="1.0.0i"/>
3040 <affects base="1.0.0" version="1.0.0j"/>
3041 <affects base="1.0.0" version="1.0.0k"/>
3042 <affects base="1.0.0" version="1.0.0l"/>
3043 <affects base="1.0.0" version="1.0.0m"/>
3044 <affects base="1.0.0" version="1.0.0n"/>
3045 <affects base="1.0.0" version="1.0.0o"/>
3046 <affects base="1.0.0" version="1.0.0p"/>
3047 <affects base="1.0.0" version="1.0.0q"/>
3048 <affects base="1.0.1" version="1.0.1"/>
3049 <affects base="1.0.1" version="1.0.1a"/>
3050 <affects base="1.0.1" version="1.0.1b"/>
3051 <affects base="1.0.1" version="1.0.1c"/>
3052 <affects base="1.0.1" version="1.0.1d"/>
3053 <affects base="1.0.1" version="1.0.1e"/>
3054 <affects base="1.0.1" version="1.0.1f"/>
3055 <affects base="1.0.1" version="1.0.1g"/>
3056 <affects base="1.0.1" version="1.0.1h"/>
3057 <affects base="1.0.1" version="1.0.1i"/>
3058 <affects base="1.0.1" version="1.0.1j"/>
3059 <affects base="1.0.1" version="1.0.1k"/>
3060 <affects base="1.0.1" version="1.0.1l"/>
3061 <affects base="1.0.2" version="1.0.2"/>
3062 <fixed base="1.0.2" version="1.0.2a" date="20150319"/>
3063 <fixed base="1.0.1" version="1.0.1m" date="20150319"/>
3064 <fixed base="1.0.0" version="1.0.0r" date="20150319"/>
3065 <fixed base="0.9.8" version="0.9.8zf" date="20150319"/>
3068 DoS via reachable assert in SSLv2 servers.
3069 A malicious client can trigger an OPENSSL_assert in
3070 servers that both support SSLv2 and enable export cipher suites by sending
3071 a specially crafted SSLv2 CLIENT-MASTER-KEY message.
3073 <advisory url="/news/secadv/20150319.txt"/>
3074 <reported source="Sean Burford (Google) and Emilia Käsper (OpenSSL development team)"/>
3077 <issue public="20150319">
3078 <impact severity="Moderate"/>
3079 <cve name="2015-1787"/>
3080 <affects base="1.0.2" version="1.0.2"/>
3081 <fixed base="1.0.2" version="1.0.2a" date="20150319"/>
3084 Empty CKE with client auth and DHE.
3085 If client auth is used then a server can seg fault in the event of a DHE
3086 ciphersuite being selected and a zero length ClientKeyExchange message being
3087 sent by the client. This could be exploited in a DoS attack.
3089 <advisory url="/news/secadv/20150319.txt"/>
3090 <reported source="Matt Caswell (OpenSSL development team)"/>
3093 <issue public="20150310">
3094 <impact severity="Low"/>
3095 <cve name="2015-0285"/>
3096 <affects base="1.0.2" version="1.0.2"/>
3097 <fixed base="1.0.2" version="1.0.2a" date="20150319"/>
3100 Under certain conditions an OpenSSL 1.0.2 client can complete a handshake with
3101 an unseeded PRNG. If the handshake succeeds then the client random that has been used will have
3102 been generated from a PRNG with insufficient entropy and therefore the output
3105 <advisory url="/news/secadv/20150319.txt"/>
3106 <reported source="Matt Caswell (OpenSSL development team)"/>
3109 <issue public="20150319">
3110 <impact severity="Low"/>
3111 <cve name="2015-0209"/>
3112 <affects base="0.9.8" version="0.9.8"/>
3113 <affects base="0.9.8" version="0.9.8a"/>
3114 <affects base="0.9.8" version="0.9.8b"/>
3115 <affects base="0.9.8" version="0.9.8c"/>
3116 <affects base="0.9.8" version="0.9.8d"/>
3117 <affects base="0.9.8" version="0.9.8e"/>
3118 <affects base="0.9.8" version="0.9.8f"/>
3119 <affects base="0.9.8" version="0.9.8g"/>
3120 <affects base="0.9.8" version="0.9.8h"/>
3121 <affects base="0.9.8" version="0.9.8i"/>
3122 <affects base="0.9.8" version="0.9.8j"/>
3123 <affects base="0.9.8" version="0.9.8k"/>
3124 <affects base="0.9.8" version="0.9.8l"/>
3125 <affects base="0.9.8" version="0.9.8m"/>
3126 <affects base="0.9.8" version="0.9.8n"/>
3127 <affects base="0.9.8" version="0.9.8o"/>
3128 <affects base="0.9.8" version="0.9.8p"/>
3129 <affects base="0.9.8" version="0.9.8q"/>
3130 <affects base="0.9.8" version="0.9.8r"/>
3131 <affects base="0.9.8" version="0.9.8s"/>
3132 <affects base="0.9.8" version="0.9.8t"/>
3133 <affects base="0.9.8" version="0.9.8u"/>
3134 <affects base="0.9.8" version="0.9.8v"/>
3135 <affects base="0.9.8" version="0.9.8w"/>
3136 <affects base="0.9.8" version="0.9.8x"/>
3137 <affects base="0.9.8" version="0.9.8y"/>
3138 <affects base="0.9.8" version="0.9.8za"/>
3139 <affects base="0.9.8" version="0.9.8zb"/>
3140 <affects base="0.9.8" version="0.9.8zc"/>
3141 <affects base="0.9.8" version="0.9.8zd"/>
3142 <affects base="0.9.8" version="0.9.8ze"/>
3143 <affects base="1.0.0" version="1.0.0"/>
3144 <affects base="1.0.0" version="1.0.0a"/>
3145 <affects base="1.0.0" version="1.0.0b"/>
3146 <affects base="1.0.0" version="1.0.0c"/>
3147 <affects base="1.0.0" version="1.0.0d"/>
3148 <affects base="1.0.0" version="1.0.0e"/>
3149 <affects base="1.0.0" version="1.0.0f"/>
3150 <affects base="1.0.0" version="1.0.0g"/>
3151 <affects base="1.0.0" version="1.0.0i"/>
3152 <affects base="1.0.0" version="1.0.0j"/>
3153 <affects base="1.0.0" version="1.0.0k"/>
3154 <affects base="1.0.0" version="1.0.0l"/>
3155 <affects base="1.0.0" version="1.0.0m"/>
3156 <affects base="1.0.0" version="1.0.0n"/>
3157 <affects base="1.0.0" version="1.0.0o"/>
3158 <affects base="1.0.0" version="1.0.0p"/>
3159 <affects base="1.0.0" version="1.0.0q"/>
3160 <affects base="1.0.1" version="1.0.1"/>
3161 <affects base="1.0.1" version="1.0.1a"/>
3162 <affects base="1.0.1" version="1.0.1b"/>
3163 <affects base="1.0.1" version="1.0.1c"/>
3164 <affects base="1.0.1" version="1.0.1d"/>
3165 <affects base="1.0.1" version="1.0.1e"/>
3166 <affects base="1.0.1" version="1.0.1f"/>
3167 <affects base="1.0.1" version="1.0.1g"/>
3168 <affects base="1.0.1" version="1.0.1h"/>
3169 <affects base="1.0.1" version="1.0.1i"/>
3170 <affects base="1.0.1" version="1.0.1j"/>
3171 <affects base="1.0.1" version="1.0.1k"/>
3172 <affects base="1.0.1" version="1.0.1l"/>
3173 <affects base="1.0.2" version="1.0.2"/>
3174 <fixed base="1.0.2" version="1.0.2a" date="20150319"/>
3175 <fixed base="1.0.1" version="1.0.1m" date="20150319"/>
3176 <fixed base="1.0.0" version="1.0.0r" date="20150319"/>
3177 <fixed base="0.9.8" version="0.9.8zf" date="20150319"/>
3180 Use After Free following d2i_ECPrivatekey error.
3181 A malformed EC private key file consumed via the d2i_ECPrivateKey function could
3182 cause a use after free condition. This, in turn, could cause a double
3183 free in several private key parsing functions (such as d2i_PrivateKey
3184 or EVP_PKCS82PKEY) and could lead to a DoS attack or memory corruption
3185 for applications that receive EC private keys from untrusted
3186 sources. This scenario is considered rare.
3188 <advisory url="/news/secadv/20150319.txt"/>
3189 <reported source="The BoringSSL project"/>
3192 <issue public="20150302">
3193 <cve name="2015-0288"/>
3194 <impact severity="Low"/>
3195 <affects base="0.9.8" version="0.9.8"/>
3196 <affects base="0.9.8" version="0.9.8a"/>
3197 <affects base="0.9.8" version="0.9.8b"/>
3198 <affects base="0.9.8" version="0.9.8c"/>
3199 <affects base="0.9.8" version="0.9.8d"/>
3200 <affects base="0.9.8" version="0.9.8e"/>
3201 <affects base="0.9.8" version="0.9.8f"/>
3202 <affects base="0.9.8" version="0.9.8g"/>
3203 <affects base="0.9.8" version="0.9.8h"/>
3204 <affects base="0.9.8" version="0.9.8i"/>
3205 <affects base="0.9.8" version="0.9.8j"/>
3206 <affects base="0.9.8" version="0.9.8k"/>
3207 <affects base="0.9.8" version="0.9.8l"/>
3208 <affects base="0.9.8" version="0.9.8m"/>
3209 <affects base="0.9.8" version="0.9.8n"/>
3210 <affects base="0.9.8" version="0.9.8o"/>
3211 <affects base="0.9.8" version="0.9.8p"/>
3212 <affects base="0.9.8" version="0.9.8q"/>
3213 <affects base="0.9.8" version="0.9.8r"/>
3214 <affects base="0.9.8" version="0.9.8s"/>
3215 <affects base="0.9.8" version="0.9.8t"/>
3216 <affects base="0.9.8" version="0.9.8u"/>
3217 <affects base="0.9.8" version="0.9.8v"/>
3218 <affects base="0.9.8" version="0.9.8w"/>
3219 <affects base="0.9.8" version="0.9.8x"/>
3220 <affects base="0.9.8" version="0.9.8y"/>
3221 <affects base="0.9.8" version="0.9.8za"/>
3222 <affects base="0.9.8" version="0.9.8zb"/>
3223 <affects base="0.9.8" version="0.9.8zc"/>
3224 <affects base="0.9.8" version="0.9.8zd"/>
3225 <affects base="0.9.8" version="0.9.8ze"/>
3226 <affects base="1.0.0" version="1.0.0"/>
3227 <affects base="1.0.0" version="1.0.0a"/>
3228 <affects base="1.0.0" version="1.0.0b"/>
3229 <affects base="1.0.0" version="1.0.0c"/>
3230 <affects base="1.0.0" version="1.0.0d"/>
3231 <affects base="1.0.0" version="1.0.0e"/>
3232 <affects base="1.0.0" version="1.0.0f"/>
3233 <affects base="1.0.0" version="1.0.0g"/>
3234 <affects base="1.0.0" version="1.0.0i"/>
3235 <affects base="1.0.0" version="1.0.0j"/>
3236 <affects base="1.0.0" version="1.0.0k"/>
3237 <affects base="1.0.0" version="1.0.0l"/>
3238 <affects base="1.0.0" version="1.0.0m"/>
3239 <affects base="1.0.0" version="1.0.0n"/>
3240 <affects base="1.0.0" version="1.0.0o"/>
3241 <affects base="1.0.0" version="1.0.0p"/>
3242 <affects base="1.0.0" version="1.0.0q"/>
3243 <affects base="1.0.1" version="1.0.1"/>
3244 <affects base="1.0.1" version="1.0.1a"/>
3245 <affects base="1.0.1" version="1.0.1b"/>
3246 <affects base="1.0.1" version="1.0.1c"/>
3247 <affects base="1.0.1" version="1.0.1d"/>
3248 <affects base="1.0.1" version="1.0.1e"/>
3249 <affects base="1.0.1" version="1.0.1f"/>
3250 <affects base="1.0.1" version="1.0.1g"/>
3251 <affects base="1.0.1" version="1.0.1h"/>
3252 <affects base="1.0.1" version="1.0.1i"/>
3253 <affects base="1.0.1" version="1.0.1j"/>
3254 <affects base="1.0.1" version="1.0.1k"/>
3255 <affects base="1.0.1" version="1.0.1l"/>
3256 <affects base="1.0.2" version="1.0.2"/>
3257 <fixed base="1.0.2" version="1.0.2a" date="20150319"/>
3258 <fixed base="1.0.1" version="1.0.1m" date="20150319"/>
3259 <fixed base="1.0.0" version="1.0.0r" date="20150319"/>
3260 <fixed base="0.9.8" version="0.9.8zf" date="20150319"/>
3263 X509_to_X509_REQ NULL pointer deref.
3264 The function X509_to_X509_REQ will crash with a NULL pointer dereference if
3265 the certificate key is invalid. This function is rarely used in practice.
3267 <advisory url="/news/secadv/20150319.txt"/>
3268 <reported source="Brian Carpenter"/>
3271 <issue public="20150108">
3272 <cve name="2015-0206"/>
3273 <affects base="1.0.0" version="1.0.0"/>
3274 <affects base="1.0.0" version="1.0.0a"/>
3275 <affects base="1.0.0" version="1.0.0b"/>
3276 <affects base="1.0.0" version="1.0.0c"/>
3277 <affects base="1.0.0" version="1.0.0d"/>
3278 <affects base="1.0.0" version="1.0.0e"/>
3279 <affects base="1.0.0" version="1.0.0f"/>
3280 <affects base="1.0.0" version="1.0.0g"/>
3281 <affects base="1.0.0" version="1.0.0i"/>
3282 <affects base="1.0.0" version="1.0.0j"/>
3283 <affects base="1.0.0" version="1.0.0k"/>
3284 <affects base="1.0.0" version="1.0.0l"/>
3285 <affects base="1.0.0" version="1.0.0m"/>
3286 <affects base="1.0.0" version="1.0.0n"/>
3287 <affects base="1.0.0" version="1.0.0o"/>
3288 <affects base="1.0.1" version="1.0.1"/>
3289 <affects base="1.0.1" version="1.0.1a"/>
3290 <affects base="1.0.1" version="1.0.1b"/>
3291 <affects base="1.0.1" version="1.0.1c"/>
3292 <affects base="1.0.1" version="1.0.1d"/>
3293 <affects base="1.0.1" version="1.0.1e"/>
3294 <affects base="1.0.1" version="1.0.1f"/>
3295 <affects base="1.0.1" version="1.0.1g"/>
3296 <affects base="1.0.1" version="1.0.1h"/>
3297 <affects base="1.0.1" version="1.0.1i"/>
3298 <affects base="1.0.1" version="1.0.1j"/>
3299 <fixed base="1.0.1" version="1.0.1k" date="20150108"/>
3300 <fixed base="1.0.0" version="1.0.0p" date="20150108"/>
3303 A memory leak can occur in the dtls1_buffer_record function under certain
3304 conditions. In particular this could occur if an attacker sent repeated
3305 DTLS records with the same sequence number but for the next epoch. The
3306 memory leak could be exploited by an attacker in a Denial of Service
3307 attack through memory exhaustion.
3309 <advisory url="/news/secadv/20150108.txt"/>
3310 <reported source="Chris Mueller"/>
3313 <issue public="20141021">
3314 <cve name="2014-3569"/>
3315 <affects base="0.9.8" version="0.9.8zc"/>
3316 <affects base="1.0.0" version="1.0.0o"/>
3317 <affects base="1.0.1" version="1.0.1j"/>
3318 <fixed base="1.0.1" version="1.0.1k" date="20150108"/>
3319 <fixed base="1.0.0" version="1.0.0p" date="20150108"/>
3320 <fixed base="0.9.8" version="0.9.8zd" date="20150108"/>
3323 When openssl is built with the no-ssl3 option and a SSL v3 ClientHello is
3324 received the ssl method would be set to NULL which could later result in
3325 a NULL pointer dereference.
3327 <advisory url="/news/secadv/20150108.txt"/>
3328 <reported source="Frank Schmirler"/>
3331 <issue public="20150105">
3332 <cve name="2014-3572"/>
3333 <affects base="0.9.8" version="0.9.8"/>
3334 <affects base="0.9.8" version="0.9.8a"/>
3335 <affects base="0.9.8" version="0.9.8b"/>
3336 <affects base="0.9.8" version="0.9.8c"/>
3337 <affects base="0.9.8" version="0.9.8d"/>
3338 <affects base="0.9.8" version="0.9.8e"/>
3339 <affects base="0.9.8" version="0.9.8f"/>
3340 <affects base="0.9.8" version="0.9.8g"/>
3341 <affects base="0.9.8" version="0.9.8h"/>
3342 <affects base="0.9.8" version="0.9.8i"/>
3343 <affects base="0.9.8" version="0.9.8j"/>
3344 <affects base="0.9.8" version="0.9.8k"/>
3345 <affects base="0.9.8" version="0.9.8l"/>
3346 <affects base="0.9.8" version="0.9.8m"/>
3347 <affects base="0.9.8" version="0.9.8n"/>
3348 <affects base="0.9.8" version="0.9.8o"/>
3349 <affects base="0.9.8" version="0.9.8p"/>
3350 <affects base="0.9.8" version="0.9.8q"/>
3351 <affects base="0.9.8" version="0.9.8r"/>
3352 <affects base="0.9.8" version="0.9.8s"/>
3353 <affects base="0.9.8" version="0.9.8t"/>
3354 <affects base="0.9.8" version="0.9.8u"/>
3355 <affects base="0.9.8" version="0.9.8v"/>
3356 <affects base="0.9.8" version="0.9.8w"/>
3357 <affects base="0.9.8" version="0.9.8x"/>
3358 <affects base="0.9.8" version="0.9.8y"/>
3359 <affects base="0.9.8" version="0.9.8za"/>
3360 <affects base="0.9.8" version="0.9.8zb"/>
3361 <affects base="0.9.8" version="0.9.8zc"/>
3362 <affects base="1.0.0" version="1.0.0"/>
3363 <affects base="1.0.0" version="1.0.0a"/>
3364 <affects base="1.0.0" version="1.0.0b"/>
3365 <affects base="1.0.0" version="1.0.0c"/>
3366 <affects base="1.0.0" version="1.0.0d"/>
3367 <affects base="1.0.0" version="1.0.0e"/>
3368 <affects base="1.0.0" version="1.0.0f"/>
3369 <affects base="1.0.0" version="1.0.0g"/>
3370 <affects base="1.0.0" version="1.0.0i"/>
3371 <affects base="1.0.0" version="1.0.0j"/>
3372 <affects base="1.0.0" version="1.0.0k"/>
3373 <affects base="1.0.0" version="1.0.0l"/>
3374 <affects base="1.0.0" version="1.0.0m"/>
3375 <affects base="1.0.0" version="1.0.0n"/>
3376 <affects base="1.0.0" version="1.0.0o"/>
3377 <affects base="1.0.1" version="1.0.1"/>
3378 <affects base="1.0.1" version="1.0.1a"/>
3379 <affects base="1.0.1" version="1.0.1b"/>
3380 <affects base="1.0.1" version="1.0.1c"/>
3381 <affects base="1.0.1" version="1.0.1d"/>
3382 <affects base="1.0.1" version="1.0.1e"/>
3383 <affects base="1.0.1" version="1.0.1f"/>
3384 <affects base="1.0.1" version="1.0.1g"/>
3385 <affects base="1.0.1" version="1.0.1h"/>
3386 <affects base="1.0.1" version="1.0.1i"/>
3387 <affects base="1.0.1" version="1.0.1j"/>
3388 <fixed base="1.0.1" version="1.0.1k" date="20150108"/>
3389 <fixed base="1.0.0" version="1.0.0p" date="20150108"/>
3390 <fixed base="0.9.8" version="0.9.8zd" date="20150108"/>
3393 An OpenSSL client will accept a handshake using an ephemeral ECDH
3394 ciphersuite using an ECDSA certificate if the server key exchange message
3395 is omitted. This effectively removes forward secrecy from the ciphersuite.
3397 <advisory url="/news/secadv/20150108.txt"/>
3398 <reported source="Karthikeyan Bhargavan of the PROSECCO team at INRIA"/>
3401 <issue public="20150106">
3402 <cve name="2015-0204"/>
3403 <affects base="0.9.8" version="0.9.8"/>
3404 <affects base="0.9.8" version="0.9.8a"/>
3405 <affects base="0.9.8" version="0.9.8b"/>
3406 <affects base="0.9.8" version="0.9.8c"/>
3407 <affects base="0.9.8" version="0.9.8d"/>
3408 <affects base="0.9.8" version="0.9.8e"/>
3409 <affects base="0.9.8" version="0.9.8f"/>
3410 <affects base="0.9.8" version="0.9.8g"/>
3411 <affects base="0.9.8" version="0.9.8h"/>
3412 <affects base="0.9.8" version="0.9.8i"/>
3413 <affects base="0.9.8" version="0.9.8j"/>
3414 <affects base="0.9.8" version="0.9.8k"/>
3415 <affects base="0.9.8" version="0.9.8l"/>
3416 <affects base="0.9.8" version="0.9.8m"/>
3417 <affects base="0.9.8" version="0.9.8n"/>
3418 <affects base="0.9.8" version="0.9.8o"/>
3419 <affects base="0.9.8" version="0.9.8p"/>
3420 <affects base="0.9.8" version="0.9.8q"/>
3421 <affects base="0.9.8" version="0.9.8r"/>
3422 <affects base="0.9.8" version="0.9.8s"/>
3423 <affects base="0.9.8" version="0.9.8t"/>
3424 <affects base="0.9.8" version="0.9.8u"/>
3425 <affects base="0.9.8" version="0.9.8v"/>
3426 <affects base="0.9.8" version="0.9.8w"/>
3427 <affects base="0.9.8" version="0.9.8x"/>
3428 <affects base="0.9.8" version="0.9.8y"/>
3429 <affects base="0.9.8" version="0.9.8za"/>
3430 <affects base="0.9.8" version="0.9.8zb"/>
3431 <affects base="0.9.8" version="0.9.8zc"/>
3432 <affects base="1.0.0" version="1.0.0"/>
3433 <affects base="1.0.0" version="1.0.0a"/>
3434 <affects base="1.0.0" version="1.0.0b"/>
3435 <affects base="1.0.0" version="1.0.0c"/>
3436 <affects base="1.0.0" version="1.0.0d"/>
3437 <affects base="1.0.0" version="1.0.0e"/>
3438 <affects base="1.0.0" version="1.0.0f"/>
3439 <affects base="1.0.0" version="1.0.0g"/>
3440 <affects base="1.0.0" version="1.0.0i"/>
3441 <affects base="1.0.0" version="1.0.0j"/>
3442 <affects base="1.0.0" version="1.0.0k"/>
3443 <affects base="1.0.0" version="1.0.0l"/>
3444 <affects base="1.0.0" version="1.0.0m"/>
3445 <affects base="1.0.0" version="1.0.0n"/>
3446 <affects base="1.0.0" version="1.0.0o"/>
3447 <affects base="1.0.1" version="1.0.1"/>
3448 <affects base="1.0.1" version="1.0.1a"/>
3449 <affects base="1.0.1" version="1.0.1b"/>
3450 <affects base="1.0.1" version="1.0.1c"/>
3451 <affects base="1.0.1" version="1.0.1d"/>
3452 <affects base="1.0.1" version="1.0.1e"/>
3453 <affects base="1.0.1" version="1.0.1f"/>
3454 <affects base="1.0.1" version="1.0.1g"/>
3455 <affects base="1.0.1" version="1.0.1h"/>
3456 <affects base="1.0.1" version="1.0.1i"/>
3457 <affects base="1.0.1" version="1.0.1j"/>
3458 <fixed base="1.0.1" version="1.0.1k" date="20150108"/>
3459 <fixed base="1.0.0" version="1.0.0p" date="20150108"/>
3460 <fixed base="0.9.8" version="0.9.8zd" date="20150108"/>
3463 An OpenSSL client will accept the use of an RSA temporary key in a
3464 non-export RSA key exchange ciphersuite. A server could present a weak
3465 temporary key and downgrade the security of the session.
3467 <advisory url="/news/secadv/20150108.txt"/>
3468 <reported source="Karthikeyan Bhargavan of the PROSECCO team at INRIA"/>
3471 <issue public="20150108">
3472 <cve name="2015-0205"/>
3473 <affects base="1.0.0" version="1.0.0"/>
3474 <affects base="1.0.0" version="1.0.0a"/>
3475 <affects base="1.0.0" version="1.0.0b"/>
3476 <affects base="1.0.0" version="1.0.0c"/>
3477 <affects base="1.0.0" version="1.0.0d"/>
3478 <affects base="1.0.0" version="1.0.0e"/>
3479 <affects base="1.0.0" version="1.0.0f"/>
3480 <affects base="1.0.0" version="1.0.0g"/>
3481 <affects base="1.0.0" version="1.0.0i"/>
3482 <affects base="1.0.0" version="1.0.0j"/>
3483 <affects base="1.0.0" version="1.0.0k"/>
3484 <affects base="1.0.0" version="1.0.0l"/>
3485 <affects base="1.0.0" version="1.0.0m"/>
3486 <affects base="1.0.0" version="1.0.0n"/>
3487 <affects base="1.0.0" version="1.0.0o"/>
3488 <affects base="1.0.1" version="1.0.1"/>
3489 <affects base="1.0.1" version="1.0.1a"/>
3490 <affects base="1.0.1" version="1.0.1b"/>
3491 <affects base="1.0.1" version="1.0.1c"/>
3492 <affects base="1.0.1" version="1.0.1d"/>
3493 <affects base="1.0.1" version="1.0.1e"/>
3494 <affects base="1.0.1" version="1.0.1f"/>
3495 <affects base="1.0.1" version="1.0.1g"/>
3496 <affects base="1.0.1" version="1.0.1h"/>
3497 <affects base="1.0.1" version="1.0.1i"/>
3498 <affects base="1.0.1" version="1.0.1j"/>
3499 <fixed base="1.0.1" version="1.0.1k" date="20150108"/>
3500 <fixed base="1.0.0" version="1.0.0p" date="20150108"/>
3503 An OpenSSL server will accept a DH certificate for client authentication
3504 without the certificate verify message. This effectively allows a client
3505 to authenticate without the use of a private key. This only affects
3506 servers which trust a client certificate authority which issues
3507 certificates containing DH keys: these are extremely rare and hardly ever
3510 <advisory url="/news/secadv/20150108.txt"/>
3511 <reported source="Karthikeyan Bhargavan of the PROSECCO team at INRIA"/>
3514 <issue public="20150105">
3515 <cve name="2014-8275"/>
3516 <affects base="0.9.8" version="0.9.8"/>
3517 <affects base="0.9.8" version="0.9.8a"/>
3518 <affects base="0.9.8" version="0.9.8b"/>
3519 <affects base="0.9.8" version="0.9.8c"/>
3520 <affects base="0.9.8" version="0.9.8d"/>
3521 <affects base="0.9.8" version="0.9.8e"/>
3522 <affects base="0.9.8" version="0.9.8f"/>
3523 <affects base="0.9.8" version="0.9.8g"/>
3524 <affects base="0.9.8" version="0.9.8h"/>
3525 <affects base="0.9.8" version="0.9.8i"/>
3526 <affects base="0.9.8" version="0.9.8j"/>
3527 <affects base="0.9.8" version="0.9.8k"/>
3528 <affects base="0.9.8" version="0.9.8l"/>
3529 <affects base="0.9.8" version="0.9.8m"/>
3530 <affects base="0.9.8" version="0.9.8n"/>
3531 <affects base="0.9.8" version="0.9.8o"/>
3532 <affects base="0.9.8" version="0.9.8p"/>
3533 <affects base="0.9.8" version="0.9.8q"/>
3534 <affects base="0.9.8" version="0.9.8r"/>
3535 <affects base="0.9.8" version="0.9.8s"/>
3536 <affects base="0.9.8" version="0.9.8t"/>
3537 <affects base="0.9.8" version="0.9.8u"/>
3538 <affects base="0.9.8" version="0.9.8v"/>
3539 <affects base="0.9.8" version="0.9.8w"/>
3540 <affects base="0.9.8" version="0.9.8x"/>
3541 <affects base="0.9.8" version="0.9.8y"/>
3542 <affects base="0.9.8" version="0.9.8za"/>
3543 <affects base="0.9.8" version="0.9.8zb"/>
3544 <affects base="0.9.8" version="0.9.8zc"/>
3545 <affects base="1.0.0" version="1.0.0"/>
3546 <affects base="1.0.0" version="1.0.0a"/>
3547 <affects base="1.0.0" version="1.0.0b"/>
3548 <affects base="1.0.0" version="1.0.0c"/>
3549 <affects base="1.0.0" version="1.0.0d"/>
3550 <affects base="1.0.0" version="1.0.0e"/>
3551 <affects base="1.0.0" version="1.0.0f"/>
3552 <affects base="1.0.0" version="1.0.0g"/>
3553 <affects base="1.0.0" version="1.0.0i"/>
3554 <affects base="1.0.0" version="1.0.0j"/>
3555 <affects base="1.0.0" version="1.0.0k"/>
3556 <affects base="1.0.0" version="1.0.0l"/>
3557 <affects base="1.0.0" version="1.0.0m"/>
3558 <affects base="1.0.0" version="1.0.0n"/>
3559 <affects base="1.0.0" version="1.0.0o"/>
3560 <affects base="1.0.1" version="1.0.1"/>
3561 <affects base="1.0.1" version="1.0.1a"/>
3562 <affects base="1.0.1" version="1.0.1b"/>
3563 <affects base="1.0.1" version="1.0.1c"/>
3564 <affects base="1.0.1" version="1.0.1d"/>
3565 <affects base="1.0.1" version="1.0.1e"/>
3566 <affects base="1.0.1" version="1.0.1f"/>
3567 <affects base="1.0.1" version="1.0.1g"/>
3568 <affects base="1.0.1" version="1.0.1h"/>
3569 <affects base="1.0.1" version="1.0.1i"/>
3570 <affects base="1.0.1" version="1.0.1j"/>
3571 <fixed base="1.0.1" version="1.0.1k" date="20150108"/>
3572 <fixed base="1.0.0" version="1.0.0p" date="20150108"/>
3573 <fixed base="0.9.8" version="0.9.8zd" date="20150108"/>
3576 OpenSSL accepts several non-DER-variations of certificate signature
3577 algorithm and signature encodings. OpenSSL also does not enforce a
3578 match between the signature algorithm between the signed and unsigned
3579 portions of the certificate. By modifying the contents of the
3580 signature algorithm or the encoding of the signature, it is possible
3581 to change the certificate's fingerprint.
3583 This does not allow an attacker to forge certificates, and does not
3584 affect certificate verification or OpenSSL servers/clients in any other
3585 way. It also does not affect common revocation mechanisms. Only custom
3586 applications that rely on the uniqueness of the fingerprint (e.g.
3587 certificate blacklists) may be affected.
3589 <advisory url="/news/secadv/20150108.txt"/>
3590 <reported source="Antti Karjalainen and Tuomo Untinen from the Codenomicon CROSS program/Konrad Kraszewski from Google"/>
3593 <issue public="20150108">
3594 <cve name="2014-3570"/>
3595 <affects base="0.9.8" version="0.9.8"/>
3596 <affects base="0.9.8" version="0.9.8a"/>
3597 <affects base="0.9.8" version="0.9.8b"/>
3598 <affects base="0.9.8" version="0.9.8c"/>
3599 <affects base="0.9.8" version="0.9.8d"/>
3600 <affects base="0.9.8" version="0.9.8e"/>
3601 <affects base="0.9.8" version="0.9.8f"/>
3602 <affects base="0.9.8" version="0.9.8g"/>
3603 <affects base="0.9.8" version="0.9.8h"/>
3604 <affects base="0.9.8" version="0.9.8i"/>
3605 <affects base="0.9.8" version="0.9.8j"/>
3606 <affects base="0.9.8" version="0.9.8k"/>
3607 <affects base="0.9.8" version="0.9.8l"/>
3608 <affects base="0.9.8" version="0.9.8m"/>
3609 <affects base="0.9.8" version="0.9.8n"/>
3610 <affects base="0.9.8" version="0.9.8o"/>
3611 <affects base="0.9.8" version="0.9.8p"/>
3612 <affects base="0.9.8" version="0.9.8q"/>
3613 <affects base="0.9.8" version="0.9.8r"/>
3614 <affects base="0.9.8" version="0.9.8s"/>
3615 <affects base="0.9.8" version="0.9.8t"/>
3616 <affects base="0.9.8" version="0.9.8u"/>
3617 <affects base="0.9.8" version="0.9.8v"/>
3618 <affects base="0.9.8" version="0.9.8w"/>
3619 <affects base="0.9.8" version="0.9.8x"/>
3620 <affects base="0.9.8" version="0.9.8y"/>
3621 <affects base="0.9.8" version="0.9.8za"/>
3622 <affects base="0.9.8" version="0.9.8zb"/>
3623 <affects base="0.9.8" version="0.9.8zc"/>
3624 <affects base="1.0.0" version="1.0.0"/>
3625 <affects base="1.0.0" version="1.0.0a"/>
3626 <affects base="1.0.0" version="1.0.0b"/>
3627 <affects base="1.0.0" version="1.0.0c"/>
3628 <affects base="1.0.0" version="1.0.0d"/>
3629 <affects base="1.0.0" version="1.0.0e"/>
3630 <affects base="1.0.0" version="1.0.0f"/>
3631 <affects base="1.0.0" version="1.0.0g"/>
3632 <affects base="1.0.0" version="1.0.0i"/>
3633 <affects base="1.0.0" version="1.0.0j"/>
3634 <affects base="1.0.0" version="1.0.0k"/>
3635 <affects base="1.0.0" version="1.0.0l"/>
3636 <affects base="1.0.0" version="1.0.0m"/>
3637 <affects base="1.0.0" version="1.0.0n"/>
3638 <affects base="1.0.0" version="1.0.0o"/>
3639 <affects base="1.0.1" version="1.0.1"/>
3640 <affects base="1.0.1" version="1.0.1a"/>
3641 <affects base="1.0.1" version="1.0.1b"/>
3642 <affects base="1.0.1" version="1.0.1c"/>
3643 <affects base="1.0.1" version="1.0.1d"/>
3644 <affects base="1.0.1" version="1.0.1e"/>
3645 <affects base="1.0.1" version="1.0.1f"/>
3646 <affects base="1.0.1" version="1.0.1g"/>
3647 <affects base="1.0.1" version="1.0.1h"/>
3648 <affects base="1.0.1" version="1.0.1i"/>
3649 <affects base="1.0.1" version="1.0.1j"/>
3650 <fixed base="1.0.1" version="1.0.1k" date="20150108"/>
3651 <fixed base="1.0.0" version="1.0.0p" date="20150108"/>
3652 <fixed base="0.9.8" version="0.9.8zd" date="20150108"/>
3655 Bignum squaring (BN_sqr) may produce incorrect results on some platforms,
3656 including x86_64. This bug occurs at random with a very low probability,
3657 and is not known to be exploitable in any way, though its exact impact is
3658 difficult to determine. The following has been determined:
3660 *) The probability of BN_sqr producing an incorrect result at random is
3661 very low: 1/2^64 on the single affected 32-bit platform (MIPS) and 1/2^128
3662 on affected 64-bit platforms.
3663 *) On most platforms, RSA follows a different code path and RSA operations
3664 are not affected at all. For the remaining platforms (e.g. OpenSSL built
3665 without assembly support), pre-existing countermeasures thwart bug
3667 *) Static ECDH is theoretically affected: it is possible to construct
3668 elliptic curve points that would falsely appear to be on the given curve.
3669 However, there is no known computationally feasible way to construct such
3670 points with low order, and so the security of static ECDH private keys is
3671 believed to be unaffected.
3672 *) Other routines known to be theoretically affected are modular
3673 exponentiation, primality testing, DSA, RSA blinding, JPAKE and SRP. No
3674 exploits are known and straightforward bug attacks fail - either the
3675 attacker cannot control when the bug triggers, or no private key material
3678 <advisory url="/news/secadv/20150108.txt"/>
3679 <reported source="Pieter Wuille (Blockstream)"/>
3682 <issue public="20141015">
3683 <cve name="2014-3513"/>
3684 <affects base="1.0.1" version="1.0.1"/>
3685 <affects base="1.0.1" version="1.0.1a"/>
3686 <affects base="1.0.1" version="1.0.1b"/>
3687 <affects base="1.0.1" version="1.0.1c"/>
3688 <affects base="1.0.1" version="1.0.1d"/>
3689 <affects base="1.0.1" version="1.0.1e"/>
3690 <affects base="1.0.1" version="1.0.1f"/>
3691 <affects base="1.0.1" version="1.0.1g"/>
3692 <affects base="1.0.1" version="1.0.1h"/>
3693 <affects base="1.0.1" version="1.0.1i"/>
3694 <fixed base="1.0.1" version="1.0.1j" date="20141015"/>
3696 A flaw in the DTLS SRTP extension parsing code allows an attacker, who
3697 sends a carefully crafted handshake message, to cause OpenSSL to fail
3698 to free up to 64k of memory causing a memory leak. This could be
3699 exploited in a Denial Of Service attack. This issue affects OpenSSL
3700 1.0.1 server implementations for both SSL/TLS and DTLS regardless of
3701 whether SRTP is used or configured. Implementations of OpenSSL that
3702 have been compiled with OPENSSL_NO_SRTP defined are not affected.
3704 <advisory url="/news/secadv/20141015.txt"/>
3705 <reported source="LibreSSL project"/>
3708 <issue public="20141015">
3709 <cve name="2014-3567"/>
3710 <affects base="0.9.8" version="0.9.8g"/>
3711 <affects base="0.9.8" version="0.9.8h"/>
3712 <affects base="0.9.8" version="0.9.8i"/>
3713 <affects base="0.9.8" version="0.9.8j"/>
3714 <affects base="0.9.8" version="0.9.8k"/>
3715 <affects base="0.9.8" version="0.9.8l"/>
3716 <affects base="0.9.8" version="0.9.8m"/>
3717 <affects base="0.9.8" version="0.9.8n"/>
3718 <affects base="0.9.8" version="0.9.8o"/>
3719 <affects base="0.9.8" version="0.9.8p"/>
3720 <affects base="0.9.8" version="0.9.8q"/>
3721 <affects base="0.9.8" version="0.9.8r"/>
3722 <affects base="0.9.8" version="0.9.8s"/>
3723 <affects base="0.9.8" version="0.9.8t"/>
3724 <affects base="0.9.8" version="0.9.8u"/>
3725 <affects base="0.9.8" version="0.9.8v"/>
3726 <affects base="0.9.8" version="0.9.8w"/>
3727 <affects base="0.9.8" version="0.9.8x"/>
3728 <affects base="0.9.8" version="0.9.8y"/>
3729 <affects base="0.9.8" version="0.9.8za"/>
3730 <affects base="0.9.8" version="0.9.8zb"/>
3731 <affects base="1.0.0" version="1.0.0"/>
3732 <affects base="1.0.0" version="1.0.0a"/>
3733 <affects base="1.0.0" version="1.0.0b"/>
3734 <affects base="1.0.0" version="1.0.0c"/>
3735 <affects base="1.0.0" version="1.0.0d"/>
3736 <affects base="1.0.0" version="1.0.0e"/>
3737 <affects base="1.0.0" version="1.0.0f"/>
3738 <affects base="1.0.0" version="1.0.0g"/>
3739 <affects base="1.0.0" version="1.0.0i"/>
3740 <affects base="1.0.0" version="1.0.0j"/>
3741 <affects base="1.0.0" version="1.0.0k"/>
3742 <affects base="1.0.0" version="1.0.0l"/>
3743 <affects base="1.0.0" version="1.0.0m"/>
3744 <affects base="1.0.0" version="1.0.0n"/>
3745 <affects base="1.0.1" version="1.0.1"/>
3746 <affects base="1.0.1" version="1.0.1a"/>
3747 <affects base="1.0.1" version="1.0.1b"/>
3748 <affects base="1.0.1" version="1.0.1c"/>
3749 <affects base="1.0.1" version="1.0.1d"/>
3750 <affects base="1.0.1" version="1.0.1e"/>
3751 <affects base="1.0.1" version="1.0.1f"/>
3752 <affects base="1.0.1" version="1.0.1g"/>
3753 <affects base="1.0.1" version="1.0.1h"/>
3754 <affects base="1.0.1" version="1.0.1i"/>
3755 <fixed base="1.0.1" version="1.0.1j" date="20140806"/>
3756 <fixed base="1.0.0" version="1.0.0o" date="20140806"/>
3757 <fixed base="0.9.8" version="0.9.8zc" date="20140806"/>
3759 When an OpenSSL SSL/TLS/DTLS server receives a session ticket the
3760 integrity of that ticket is first verified. In the event of a session
3761 ticket integrity check failing, OpenSSL will fail to free memory
3762 causing a memory leak. By sending a large number of invalid session
3763 tickets an attacker could exploit this issue in a Denial Of Service
3766 <advisory url="/news/secadv/20141015.txt"/>
3768 <issue public="20141015">
3769 <cve name=""/> <!-- this is deliberate -->
3770 <affects base="0.9.8" version="0.9.8"/>
3771 <affects base="0.9.8" version="0.9.8a"/>
3772 <affects base="0.9.8" version="0.9.8b"/>
3773 <affects base="0.9.8" version="0.9.8c"/>
3774 <affects base="0.9.8" version="0.9.8d"/>
3775 <affects base="0.9.8" version="0.9.8e"/>
3776 <affects base="0.9.8" version="0.9.8f"/>
3777 <affects base="0.9.8" version="0.9.8g"/>
3778 <affects base="0.9.8" version="0.9.8h"/>
3779 <affects base="0.9.8" version="0.9.8i"/>
3780 <affects base="0.9.8" version="0.9.8j"/>
3781 <affects base="0.9.8" version="0.9.8k"/>
3782 <affects base="0.9.8" version="0.9.8l"/>
3783 <affects base="0.9.8" version="0.9.8m"/>
3784 <affects base="0.9.8" version="0.9.8n"/>
3785 <affects base="0.9.8" version="0.9.8o"/>
3786 <affects base="0.9.8" version="0.9.8p"/>
3787 <affects base="0.9.8" version="0.9.8q"/>
3788 <affects base="0.9.8" version="0.9.8r"/>
3789 <affects base="0.9.8" version="0.9.8s"/>
3790 <affects base="0.9.8" version="0.9.8t"/>
3791 <affects base="0.9.8" version="0.9.8u"/>
3792 <affects base="0.9.8" version="0.9.8v"/>
3793 <affects base="0.9.8" version="0.9.8w"/>
3794 <affects base="0.9.8" version="0.9.8x"/>
3795 <affects base="0.9.8" version="0.9.8y"/>
3796 <affects base="0.9.8" version="0.9.8za"/>
3797 <affects base="0.9.8" version="0.9.8zb"/>
3798 <affects base="1.0.0" version="1.0.0"/>
3799 <affects base="1.0.0" version="1.0.0a"/>
3800 <affects base="1.0.0" version="1.0.0b"/>
3801 <affects base="1.0.0" version="1.0.0c"/>
3802 <affects base="1.0.0" version="1.0.0d"/>
3803 <affects base="1.0.0" version="1.0.0e"/>
3804 <affects base="1.0.0" version="1.0.0f"/>
3805 <affects base="1.0.0" version="1.0.0g"/>
3806 <affects base="1.0.0" version="1.0.0i"/>
3807 <affects base="1.0.0" version="1.0.0j"/>
3808 <affects base="1.0.0" version="1.0.0k"/>
3809 <affects base="1.0.0" version="1.0.0l"/>
3810 <affects base="1.0.0" version="1.0.0m"/>
3811 <affects base="1.0.0" version="1.0.0n"/>
3812 <affects base="1.0.1" version="1.0.1"/>
3813 <affects base="1.0.1" version="1.0.1a"/>
3814 <affects base="1.0.1" version="1.0.1b"/>
3815 <affects base="1.0.1" version="1.0.1c"/>
3816 <affects base="1.0.1" version="1.0.1d"/>
3817 <affects base="1.0.1" version="1.0.1e"/>
3818 <affects base="1.0.1" version="1.0.1f"/>
3819 <affects base="1.0.1" version="1.0.1g"/>
3820 <affects base="1.0.1" version="1.0.1h"/>
3821 <affects base="1.0.1" version="1.0.1i"/>
3822 <fixed base="1.0.1" version="1.0.1j" date="20140806"/>
3823 <fixed base="1.0.0" version="1.0.0o" date="20140806"/>
3824 <fixed base="0.9.8" version="0.9.8zc" date="20140806"/>
3826 OpenSSL has added support for TLS_FALLBACK_SCSV to allow applications
3827 to block the ability for a MITM attacker to force a protocol
3830 Some client applications (such as browsers) will reconnect using a
3831 downgraded protocol to work around interoperability bugs in older
3832 servers. This could be exploited by an active man-in-the-middle to
3833 downgrade connections to SSL 3.0 even if both sides of the connection
3834 support higher protocols. SSL 3.0 contains a number of weaknesses
3835 including POODLE (CVE-2014-3566).
3838 https://tools.ietf.org/html/draft-ietf-tls-downgrade-scsv-00 and
3839 https://www.openssl.org/~bodo/ssl-poodle.pdf
3843 <issue public="20141015">
3844 <cve name="2014-3568"/>
3845 <affects base="0.9.8" version="0.9.8"/>
3846 <affects base="0.9.8" version="0.9.8a"/>
3847 <affects base="0.9.8" version="0.9.8b"/>
3848 <affects base="0.9.8" version="0.9.8c"/>
3849 <affects base="0.9.8" version="0.9.8d"/>
3850 <affects base="0.9.8" version="0.9.8e"/>
3851 <affects base="0.9.8" version="0.9.8f"/>
3852 <affects base="0.9.8" version="0.9.8g"/>
3853 <affects base="0.9.8" version="0.9.8h"/>
3854 <affects base="0.9.8" version="0.9.8i"/>
3855 <affects base="0.9.8" version="0.9.8j"/>
3856 <affects base="0.9.8" version="0.9.8k"/>
3857 <affects base="0.9.8" version="0.9.8l"/>
3858 <affects base="0.9.8" version="0.9.8m"/>
3859 <affects base="0.9.8" version="0.9.8n"/>
3860 <affects base="0.9.8" version="0.9.8o"/>
3861 <affects base="0.9.8" version="0.9.8p"/>
3862 <affects base="0.9.8" version="0.9.8q"/>
3863 <affects base="0.9.8" version="0.9.8r"/>
3864 <affects base="0.9.8" version="0.9.8s"/>
3865 <affects base="0.9.8" version="0.9.8t"/>
3866 <affects base="0.9.8" version="0.9.8u"/>
3867 <affects base="0.9.8" version="0.9.8v"/>
3868 <affects base="0.9.8" version="0.9.8w"/>
3869 <affects base="0.9.8" version="0.9.8x"/>
3870 <affects base="0.9.8" version="0.9.8y"/>
3871 <affects base="0.9.8" version="0.9.8za"/>
3872 <affects base="0.9.8" version="0.9.8zb"/>
3873 <affects base="1.0.0" version="1.0.0"/>
3874 <affects base="1.0.0" version="1.0.0a"/>
3875 <affects base="1.0.0" version="1.0.0b"/>
3876 <affects base="1.0.0" version="1.0.0c"/>
3877 <affects base="1.0.0" version="1.0.0d"/>
3878 <affects base="1.0.0" version="1.0.0e"/>
3879 <affects base="1.0.0" version="1.0.0f"/>
3880 <affects base="1.0.0" version="1.0.0g"/>
3881 <affects base="1.0.0" version="1.0.0i"/>
3882 <affects base="1.0.0" version="1.0.0j"/>
3883 <affects base="1.0.0" version="1.0.0k"/>
3884 <affects base="1.0.0" version="1.0.0l"/>
3885 <affects base="1.0.0" version="1.0.0m"/>
3886 <affects base="1.0.0" version="1.0.0n"/>
3887 <affects base="1.0.1" version="1.0.1"/>
3888 <affects base="1.0.1" version="1.0.1a"/>
3889 <affects base="1.0.1" version="1.0.1b"/>
3890 <affects base="1.0.1" version="1.0.1c"/>
3891 <affects base="1.0.1" version="1.0.1d"/>
3892 <affects base="1.0.1" version="1.0.1e"/>
3893 <affects base="1.0.1" version="1.0.1f"/>
3894 <affects base="1.0.1" version="1.0.1g"/>
3895 <affects base="1.0.1" version="1.0.1h"/>
3896 <affects base="1.0.1" version="1.0.1i"/>
3897 <fixed base="1.0.1" version="1.0.1j" date="20140806"/>
3898 <fixed base="1.0.0" version="1.0.0o" date="20140806"/>
3899 <fixed base="0.9.8" version="0.9.8zc" date="20140806"/>
3902 When OpenSSL is configured with "no-ssl3" as a build option, servers
3903 could accept and complete a SSL 3.0 handshake, and clients could be
3904 configured to send them.
3906 <advisory url="/news/secadv/20141015.txt"/>
3907 <reported source="Akamai Technologies"/>
3909 <issue public="20140806">
3910 <cve name="2014-3508"/>
3911 <affects base="0.9.8" version="0.9.8"/>
3912 <affects base="0.9.8" version="0.9.8a"/>
3913 <affects base="0.9.8" version="0.9.8b"/>
3914 <affects base="0.9.8" version="0.9.8c"/>
3915 <affects base="0.9.8" version="0.9.8d"/>
3916 <affects base="0.9.8" version="0.9.8e"/>
3917 <affects base="0.9.8" version="0.9.8f"/>
3918 <affects base="0.9.8" version="0.9.8g"/>
3919 <affects base="0.9.8" version="0.9.8h"/>
3920 <affects base="0.9.8" version="0.9.8i"/>
3921 <affects base="0.9.8" version="0.9.8j"/>
3922 <affects base="0.9.8" version="0.9.8k"/>
3923 <affects base="0.9.8" version="0.9.8l"/>
3924 <affects base="0.9.8" version="0.9.8m"/>
3925 <affects base="0.9.8" version="0.9.8n"/>
3926 <affects base="0.9.8" version="0.9.8o"/>
3927 <affects base="0.9.8" version="0.9.8p"/>
3928 <affects base="0.9.8" version="0.9.8q"/>
3929 <affects base="0.9.8" version="0.9.8r"/>
3930 <affects base="0.9.8" version="0.9.8s"/>
3931 <affects base="0.9.8" version="0.9.8t"/>
3932 <affects base="0.9.8" version="0.9.8u"/>
3933 <affects base="0.9.8" version="0.9.8v"/>
3934 <affects base="0.9.8" version="0.9.8w"/>
3935 <affects base="0.9.8" version="0.9.8x"/>
3936 <affects base="0.9.8" version="0.9.8y"/>
3937 <affects base="0.9.8" version="0.9.8za"/>
3938 <affects base="1.0.0" version="1.0.0"/>
3939 <affects base="1.0.0" version="1.0.0a"/>
3940 <affects base="1.0.0" version="1.0.0b"/>
3941 <affects base="1.0.0" version="1.0.0c"/>
3942 <affects base="1.0.0" version="1.0.0d"/>
3943 <affects base="1.0.0" version="1.0.0e"/>
3944 <affects base="1.0.0" version="1.0.0f"/>
3945 <affects base="1.0.0" version="1.0.0g"/>
3946 <affects base="1.0.0" version="1.0.0i"/>
3947 <affects base="1.0.0" version="1.0.0j"/>
3948 <affects base="1.0.0" version="1.0.0k"/>
3949 <affects base="1.0.0" version="1.0.0l"/>
3950 <affects base="1.0.0" version="1.0.0m"/>
3951 <affects base="1.0.1" version="1.0.1"/>
3952 <affects base="1.0.1" version="1.0.1a"/>
3953 <affects base="1.0.1" version="1.0.1b"/>
3954 <affects base="1.0.1" version="1.0.1c"/>
3955 <affects base="1.0.1" version="1.0.1d"/>
3956 <affects base="1.0.1" version="1.0.1e"/>
3957 <affects base="1.0.1" version="1.0.1f"/>
3958 <affects base="1.0.1" version="1.0.1g"/>
3959 <affects base="1.0.1" version="1.0.1h"/>
3960 <fixed base="1.0.1" version="1.0.1i" date="20140806">
3962 <fixed base="1.0.0" version="1.0.0n" date="20140806">
3964 <fixed base="0.9.8" version="0.9.8zb" date="20140806">
3967 A flaw in OBJ_obj2txt may cause pretty printing functions such as
3968 X509_name_oneline, X509_name_print_ex, to leak some information from the
3969 stack. Applications may be affected if they echo pretty printing output to the
3970 attacker. OpenSSL SSL/TLS clients and servers themselves are not affected.
3972 <advisory url="/news/secadv/20140806.txt"/>
3973 <reported source="Ivan Fratric (Google)"/>
3976 <issue public="20140806">
3977 <cve name="2014-5139"/>
3979 A crash was found affecting SRP ciphersuites used in a Server Hello message.
3980 The issue affects OpenSSL clients and allows a malicious server to crash
3981 the client with a null pointer dereference (read) by specifying an SRP
3982 ciphersuite even though it was not properly negotiated with the client. This
3983 could lead to a Denial of Service.
3985 <affects base="1.0.1" version="1.0.1"/>
3986 <affects base="1.0.1" version="1.0.1a"/>
3987 <affects base="1.0.1" version="1.0.1b"/>
3988 <affects base="1.0.1" version="1.0.1c"/>
3989 <affects base="1.0.1" version="1.0.1d"/>
3990 <affects base="1.0.1" version="1.0.1e"/>
3991 <affects base="1.0.1" version="1.0.1f"/>
3992 <affects base="1.0.1" version="1.0.1g"/>
3993 <affects base="1.0.1" version="1.0.1h"/>
3994 <fixed base="1.0.1" version="1.0.1i" date="20140806">
3996 <advisory url="/news/secadv/20140806.txt"/>
3997 <reported source="Joonas Kuorilehto and Riku Hietamäki (Codenomicon)"/>
4000 <issue public="20140806">
4001 <cve name="2014-3509"/>
4002 <description>A race condition was found in ssl_parse_serverhello_tlsext.
4003 If a multithreaded client connects to a malicious server using a resumed session
4004 and the server sends an ec point format extension, it could write up to 255 bytes
4005 to freed memory.</description>
4006 <affects base="1.0.0" version="1.0.0"/>
4007 <affects base="1.0.0" version="1.0.0a"/>
4008 <affects base="1.0.0" version="1.0.0b"/>
4009 <affects base="1.0.0" version="1.0.0c"/>
4010 <affects base="1.0.0" version="1.0.0d"/>
4011 <affects base="1.0.0" version="1.0.0e"/>
4012 <affects base="1.0.0" version="1.0.0f"/>
4013 <affects base="1.0.0" version="1.0.0g"/>
4014 <affects base="1.0.0" version="1.0.0i"/>
4015 <affects base="1.0.0" version="1.0.0j"/>
4016 <affects base="1.0.0" version="1.0.0k"/>
4017 <affects base="1.0.0" version="1.0.0l"/>
4018 <affects base="1.0.0" version="1.0.0m"/>
4019 <affects base="1.0.1" version="1.0.1"/>
4020 <affects base="1.0.1" version="1.0.1a"/>
4021 <affects base="1.0.1" version="1.0.1b"/>
4022 <affects base="1.0.1" version="1.0.1c"/>
4023 <affects base="1.0.1" version="1.0.1d"/>
4024 <affects base="1.0.1" version="1.0.1e"/>
4025 <affects base="1.0.1" version="1.0.1f"/>
4026 <affects base="1.0.1" version="1.0.1g"/>
4027 <affects base="1.0.1" version="1.0.1h"/>
4028 <fixed base="1.0.1" version="1.0.1i" date="20140806">
4030 <fixed base="1.0.0" version="1.0.0n" date="20140806">
4032 <reported source="Gabor Tyukasz (LogMeIn Inc)"/>
4033 <advisory url="/news/secadv/20140806.txt"/>
4036 <issue public="20140806">
4037 <cve name="2014-3505"/>
4038 <affects base="0.9.8" version="0.9.8m"/>
4039 <affects base="0.9.8" version="0.9.8n"/>
4040 <affects base="0.9.8" version="0.9.8o"/>
4041 <affects base="0.9.8" version="0.9.8p"/>
4042 <affects base="0.9.8" version="0.9.8q"/>
4043 <affects base="0.9.8" version="0.9.8r"/>
4044 <affects base="0.9.8" version="0.9.8s"/>
4045 <affects base="0.9.8" version="0.9.8t"/>
4046 <affects base="0.9.8" version="0.9.8u"/>
4047 <affects base="0.9.8" version="0.9.8v"/>
4048 <affects base="0.9.8" version="0.9.8w"/>
4049 <affects base="0.9.8" version="0.9.8x"/>
4050 <affects base="0.9.8" version="0.9.8y"/>
4051 <affects base="0.9.8" version="0.9.8za"/>
4052 <affects base="1.0.0" version="1.0.0"/>
4053 <affects base="1.0.0" version="1.0.0a"/>
4054 <affects base="1.0.0" version="1.0.0b"/>
4055 <affects base="1.0.0" version="1.0.0c"/>
4056 <affects base="1.0.0" version="1.0.0d"/>
4057 <affects base="1.0.0" version="1.0.0e"/>
4058 <affects base="1.0.0" version="1.0.0f"/>
4059 <affects base="1.0.0" version="1.0.0g"/>
4060 <affects base="1.0.0" version="1.0.0i"/>
4061 <affects base="1.0.0" version="1.0.0j"/>
4062 <affects base="1.0.0" version="1.0.0k"/>
4063 <affects base="1.0.0" version="1.0.0l"/>
4064 <affects base="1.0.0" version="1.0.0m"/>
4065 <affects base="1.0.1" version="1.0.1"/>
4066 <affects base="1.0.1" version="1.0.1a"/>
4067 <affects base="1.0.1" version="1.0.1b"/>
4068 <affects base="1.0.1" version="1.0.1c"/>
4069 <affects base="1.0.1" version="1.0.1d"/>
4070 <affects base="1.0.1" version="1.0.1e"/>
4071 <affects base="1.0.1" version="1.0.1f"/>
4072 <affects base="1.0.1" version="1.0.1g"/>
4073 <affects base="1.0.1" version="1.0.1h"/>
4074 <fixed base="1.0.1" version="1.0.1i" date="20140806">
4076 <fixed base="1.0.0" version="1.0.0n" date="20140806">
4078 <fixed base="0.9.8" version="0.9.8zb" date="20140806">
4081 A Double Free was found when processing DTLS packets.
4082 An attacker can force an error condition which causes openssl to crash whilst
4083 processing DTLS packets due to memory being freed twice. This could lead to a
4084 Denial of Service attack.
4086 <reported source="Adam Langley and Wan-Teh Chang (Google)"/>
4087 <advisory url="/news/secadv/20140806.txt"/>
4090 <issue public="20140806">
4091 <cve name="2014-3506"/>
4092 <affects base="0.9.8" version="0.9.8"/>
4093 <affects base="0.9.8" version="0.9.8a"/>
4094 <affects base="0.9.8" version="0.9.8b"/>
4095 <affects base="0.9.8" version="0.9.8c"/>
4096 <affects base="0.9.8" version="0.9.8d"/>
4097 <affects base="0.9.8" version="0.9.8e"/>
4098 <affects base="0.9.8" version="0.9.8f"/>
4099 <affects base="0.9.8" version="0.9.8g"/>
4100 <affects base="0.9.8" version="0.9.8h"/>
4101 <affects base="0.9.8" version="0.9.8i"/>
4102 <affects base="0.9.8" version="0.9.8j"/>
4103 <affects base="0.9.8" version="0.9.8k"/>
4104 <affects base="0.9.8" version="0.9.8l"/>
4105 <affects base="0.9.8" version="0.9.8m"/>
4106 <affects base="0.9.8" version="0.9.8n"/>
4107 <affects base="0.9.8" version="0.9.8o"/>
4108 <affects base="0.9.8" version="0.9.8p"/>
4109 <affects base="0.9.8" version="0.9.8q"/>
4110 <affects base="0.9.8" version="0.9.8r"/>
4111 <affects base="0.9.8" version="0.9.8s"/>
4112 <affects base="0.9.8" version="0.9.8t"/>
4113 <affects base="0.9.8" version="0.9.8u"/>
4114 <affects base="0.9.8" version="0.9.8v"/>
4115 <affects base="0.9.8" version="0.9.8w"/>
4116 <affects base="0.9.8" version="0.9.8x"/>
4117 <affects base="0.9.8" version="0.9.8y"/>
4118 <affects base="0.9.8" version="0.9.8za"/>
4119 <affects base="1.0.0" version="1.0.0"/>
4120 <affects base="1.0.0" version="1.0.0a"/>
4121 <affects base="1.0.0" version="1.0.0b"/>
4122 <affects base="1.0.0" version="1.0.0c"/>
4123 <affects base="1.0.0" version="1.0.0d"/>
4124 <affects base="1.0.0" version="1.0.0e"/>
4125 <affects base="1.0.0" version="1.0.0f"/>
4126 <affects base="1.0.0" version="1.0.0g"/>
4127 <affects base="1.0.0" version="1.0.0i"/>
4128 <affects base="1.0.0" version="1.0.0j"/>
4129 <affects base="1.0.0" version="1.0.0k"/>
4130 <affects base="1.0.0" version="1.0.0l"/>
4131 <affects base="1.0.0" version="1.0.0m"/>
4132 <affects base="1.0.1" version="1.0.1"/>
4133 <affects base="1.0.1" version="1.0.1a"/>
4134 <affects base="1.0.1" version="1.0.1b"/>
4135 <affects base="1.0.1" version="1.0.1c"/>
4136 <affects base="1.0.1" version="1.0.1d"/>
4137 <affects base="1.0.1" version="1.0.1e"/>
4138 <affects base="1.0.1" version="1.0.1f"/>
4139 <affects base="1.0.1" version="1.0.1g"/>
4140 <affects base="1.0.1" version="1.0.1h"/>
4141 <fixed base="1.0.1" version="1.0.1i" date="20140806">
4143 <fixed base="1.0.0" version="1.0.0n" date="20140806">
4145 <fixed base="0.9.8" version="0.9.8zb" date="20140806">
4148 A DTLS flaw leading to memory exhaustion was found.
4149 An attacker can force openssl to consume large amounts of memory whilst
4150 processing DTLS handshake messages. This could lead to a Denial of
4153 <reported source="Adam Langley (Google)"/>
4154 <advisory url="/news/secadv/20140806.txt"/>
4157 <issue public="20140806">
4158 <cve name="2014-3507"/>
4159 <affects base="0.9.8" version="0.9.8o"/>
4160 <affects base="0.9.8" version="0.9.8p"/>
4161 <affects base="0.9.8" version="0.9.8q"/>
4162 <affects base="0.9.8" version="0.9.8r"/>
4163 <affects base="0.9.8" version="0.9.8s"/>
4164 <affects base="0.9.8" version="0.9.8t"/>
4165 <affects base="0.9.8" version="0.9.8u"/>
4166 <affects base="0.9.8" version="0.9.8v"/>
4167 <affects base="0.9.8" version="0.9.8w"/>
4168 <affects base="0.9.8" version="0.9.8x"/>
4169 <affects base="0.9.8" version="0.9.8y"/>
4170 <affects base="0.9.8" version="0.9.8za"/>
4171 <affects base="1.0.0" version="1.0.0a"/>
4172 <affects base="1.0.0" version="1.0.0b"/>
4173 <affects base="1.0.0" version="1.0.0c"/>
4174 <affects base="1.0.0" version="1.0.0d"/>
4175 <affects base="1.0.0" version="1.0.0e"/>
4176 <affects base="1.0.0" version="1.0.0f"/>
4177 <affects base="1.0.0" version="1.0.0g"/>
4178 <affects base="1.0.0" version="1.0.0i"/>
4179 <affects base="1.0.0" version="1.0.0j"/>
4180 <affects base="1.0.0" version="1.0.0k"/>
4181 <affects base="1.0.0" version="1.0.0l"/>
4182 <affects base="1.0.0" version="1.0.0m"/>
4183 <affects base="1.0.1" version="1.0.1"/>
4184 <affects base="1.0.1" version="1.0.1a"/>
4185 <affects base="1.0.1" version="1.0.1b"/>
4186 <affects base="1.0.1" version="1.0.1c"/>
4187 <affects base="1.0.1" version="1.0.1d"/>
4188 <affects base="1.0.1" version="1.0.1e"/>
4189 <affects base="1.0.1" version="1.0.1f"/>
4190 <affects base="1.0.1" version="1.0.1g"/>
4191 <affects base="1.0.1" version="1.0.1h"/>
4192 <fixed base="1.0.1" version="1.0.1i" date="20140806">
4194 <fixed base="1.0.0" version="1.0.0n" date="20140806">
4196 <fixed base="0.9.8" version="0.9.8zb" date="20140806">
4199 A DTLS memory leak from zero-length fragments was found.
4200 By sending carefully crafted DTLS packets an attacker could cause OpenSSL to
4201 leak memory. This could lead to a Denial of Service attack.
4203 <reported source="Adam Langley (Google)"/>
4204 <advisory url="/news/secadv/20140806.txt"/>
4207 <issue public="20140806">
4208 <cve name="2014-3510"/>
4209 <affects base="0.9.8" version="0.9.8"/>
4210 <affects base="0.9.8" version="0.9.8a"/>
4211 <affects base="0.9.8" version="0.9.8b"/>
4212 <affects base="0.9.8" version="0.9.8c"/>
4213 <affects base="0.9.8" version="0.9.8d"/>
4214 <affects base="0.9.8" version="0.9.8e"/>
4215 <affects base="0.9.8" version="0.9.8f"/>
4216 <affects base="0.9.8" version="0.9.8g"/>
4217 <affects base="0.9.8" version="0.9.8h"/>
4218 <affects base="0.9.8" version="0.9.8i"/>
4219 <affects base="0.9.8" version="0.9.8j"/>
4220 <affects base="0.9.8" version="0.9.8k"/>
4221 <affects base="0.9.8" version="0.9.8l"/>
4222 <affects base="0.9.8" version="0.9.8m"/>
4223 <affects base="0.9.8" version="0.9.8n"/>
4224 <affects base="0.9.8" version="0.9.8o"/>
4225 <affects base="0.9.8" version="0.9.8p"/>
4226 <affects base="0.9.8" version="0.9.8q"/>
4227 <affects base="0.9.8" version="0.9.8r"/>
4228 <affects base="0.9.8" version="0.9.8s"/>
4229 <affects base="0.9.8" version="0.9.8t"/>
4230 <affects base="0.9.8" version="0.9.8u"/>
4231 <affects base="0.9.8" version="0.9.8v"/>
4232 <affects base="0.9.8" version="0.9.8w"/>
4233 <affects base="0.9.8" version="0.9.8x"/>
4234 <affects base="0.9.8" version="0.9.8y"/>
4235 <affects base="0.9.8" version="0.9.8za"/>
4236 <affects base="1.0.0" version="1.0.0"/>
4237 <affects base="1.0.0" version="1.0.0a"/>
4238 <affects base="1.0.0" version="1.0.0b"/>
4239 <affects base="1.0.0" version="1.0.0c"/>
4240 <affects base="1.0.0" version="1.0.0d"/>
4241 <affects base="1.0.0" version="1.0.0e"/>
4242 <affects base="1.0.0" version="1.0.0f"/>
4243 <affects base="1.0.0" version="1.0.0g"/>
4244 <affects base="1.0.0" version="1.0.0i"/>
4245 <affects base="1.0.0" version="1.0.0j"/>
4246 <affects base="1.0.0" version="1.0.0k"/>
4247 <affects base="1.0.0" version="1.0.0l"/>
4248 <affects base="1.0.0" version="1.0.0m"/>
4249 <affects base="1.0.1" version="1.0.1"/>
4250 <affects base="1.0.1" version="1.0.1a"/>
4251 <affects base="1.0.1" version="1.0.1b"/>
4252 <affects base="1.0.1" version="1.0.1c"/>
4253 <affects base="1.0.1" version="1.0.1d"/>
4254 <affects base="1.0.1" version="1.0.1e"/>
4255 <affects base="1.0.1" version="1.0.1f"/>
4256 <affects base="1.0.1" version="1.0.1g"/>
4257 <affects base="1.0.1" version="1.0.1h"/>
4258 <fixed base="1.0.1" version="1.0.1i" date="20140806">
4260 <fixed base="1.0.0" version="1.0.0n" date="20140806">
4262 <fixed base="0.9.8" version="0.9.8zb" date="20140806">
4265 A flaw in handling DTLS anonymous EC(DH) ciphersuites was found.
4266 OpenSSL DTLS clients enabling anonymous (EC)DH ciphersuites are subject to a
4267 denial of service attack. A malicious server can crash the client with a null
4268 pointer dereference (read) by specifying an anonymous (EC)DH ciphersuite and
4269 sending carefully crafted handshake messages.
4271 <reported source="Felix Gröbert (Google)"/>
4272 <advisory url="/news/secadv/20140806.txt"/>
4275 <issue public="20140806">
4276 <cve name="2014-3511"/>
4277 <affects base="1.0.1" version="1.0.1"/>
4278 <affects base="1.0.1" version="1.0.1a"/>
4279 <affects base="1.0.1" version="1.0.1b"/>
4280 <affects base="1.0.1" version="1.0.1c"/>
4281 <affects base="1.0.1" version="1.0.1d"/>
4282 <affects base="1.0.1" version="1.0.1e"/>
4283 <affects base="1.0.1" version="1.0.1f"/>
4284 <affects base="1.0.1" version="1.0.1g"/>
4285 <affects base="1.0.1" version="1.0.1h"/>
4286 <fixed base="1.0.1" version="1.0.1i" date="20140806">
4289 A flaw in the OpenSSL SSL/TLS server code causes the server to negotiate
4290 TLS 1.0 instead of higher protocol versions when the ClientHello message is
4291 badly fragmented. This allows a man-in-the-middle attacker to force a
4292 downgrade to TLS 1.0 even if both the server and the client support a higher
4293 protocol version, by modifying the client's TLS records.
4295 <reported source="David Benjamin and Adam Langley (Google)"/>
4296 <advisory url="/news/secadv/20140806.txt"/>
4299 <issue public="20140806">
4300 <cve name="2014-3512"/>
4301 <affects base="1.0.1" version="1.0.1"/>
4302 <affects base="1.0.1" version="1.0.1a"/>
4303 <affects base="1.0.1" version="1.0.1b"/>
4304 <affects base="1.0.1" version="1.0.1c"/>
4305 <affects base="1.0.1" version="1.0.1d"/>
4306 <affects base="1.0.1" version="1.0.1e"/>
4307 <affects base="1.0.1" version="1.0.1f"/>
4308 <affects base="1.0.1" version="1.0.1g"/>
4309 <affects base="1.0.1" version="1.0.1h"/>
4310 <fixed base="1.0.1" version="1.0.1i" date="20140806">
4313 A SRP buffer overrun was found.
4314 A malicious client or server can send invalid SRP parameters and overrun
4315 an internal buffer. Only applications which are explicitly set up for SRP
4318 <reported source="Sean Devlin and Watson Ladd (Cryptography Services, NCC Group)"/>
4319 <advisory url="/news/secadv/20140806.txt"/>
4322 <issue public="20020730">
4323 <cve name="2002-0655"/>
4324 <affects base="0.9.6" version="0.9.6"/>
4325 <affects base="0.9.6" version="0.9.6a"/>
4326 <affects base="0.9.6" version="0.9.6b"/>
4327 <affects base="0.9.6" version="0.9.6c"/>
4328 <affects base="0.9.6" version="0.9.6d"/>
4329 <fixed base="0.9.6" version="0.9.6e" date="20020730"/>
4330 <advisory url="/news/secadv/20020730.txt"/>
4331 <reported source="OpenSSL Group (A.L. Digital)"/>
4333 Inproper handling of ASCII representations of integers on
4334 64 bit platforms allowed remote attackers to cause a denial of
4335 service or possibly execute arbitrary code.
4339 <issue public="20020730">
4340 <cve name="2002-0656"/>
4341 <affects base="0.9.6" version="0.9.6"/>
4342 <affects base="0.9.6" version="0.9.6a"/>
4343 <affects base="0.9.6" version="0.9.6b"/>
4344 <affects base="0.9.6" version="0.9.6c"/>
4345 <affects base="0.9.6" version="0.9.6d"/>
4346 <fixed base="0.9.6" version="0.9.6e" date="20020730"/>
4347 <advisory url="/news/secadv/20020730.txt"/>
4348 <reported source="OpenSSL Group (A.L. Digital)"/>
4350 A buffer overflow allowed remote attackers to execute
4351 arbitrary code by sending a large client master key in SSL2 or a
4352 large session ID in SSL3.
4356 <issue public="20020730">
4357 <cve name="2002-0657"/>
4358 <advisory url="/news/secadv/20020730.txt"/>
4359 <affects base="0.9.7" version="0.9.7-beta3"/>
4360 <fixed base="0.9.7" version="0.9.7" date="20021210"/>
4361 <reported source="OpenSSL Group (A.L. Digital)"/>
4363 A buffer overflow when Kerberos is enabled allowed attackers
4364 to execute arbitrary code by sending a long master key. Note that this
4365 flaw did not affect any released version of 0.9.6 or 0.9.7
4369 <issue public="20020730">
4370 <cve name="2002-0659"/>
4371 <advisory url="/news/secadv/20020730.txt"/>
4372 <affects base="0.9.6" version="0.9.6a"/>
4373 <affects base="0.9.6" version="0.9.6b"/>
4374 <affects base="0.9.6" version="0.9.6c"/>
4375 <affects base="0.9.6" version="0.9.6d"/>
4376 <fixed base="0.9.6" version="0.9.6e" date="20020730"/>
4378 A flaw in the ASN1 library allowed remote attackers to cause a denial of
4379 service by sending invalid encodings.
4383 <issue public="20020808">
4384 <cve name="2002-1568"/>
4385 <affects base="0.9.6" version="0.9.6e"/>
4386 <fixed base="0.9.6" version="0.9.6f" date="20020808">
4387 <git hash="517a0e7fa0f5453c860a3aec17b678bd55d5aad7"/>
4390 The use of assertions when detecting buffer overflow attacks
4391 allowed remote attackers to cause a denial of service (crash) by
4392 sending certain messages to cause
4393 OpenSSL to abort from a failed assertion, as demonstrated using SSLv2
4394 CLIENT_MASTER_KEY messages, which were not properly handled in
4399 <issue public="20030219">
4400 <cve name="2003-0078"/>
4401 <affects base="0.9.7" version="0.9.7"/>
4402 <affects base="0.9.6" version="0.9.6"/>
4403 <affects base="0.9.6" version="0.9.6a"/>
4404 <affects base="0.9.6" version="0.9.6b"/>
4405 <affects base="0.9.6" version="0.9.6c"/>
4406 <affects base="0.9.6" version="0.9.6d"/>
4407 <affects base="0.9.6" version="0.9.6e"/>
4408 <affects base="0.9.6" version="0.9.6f"/>
4409 <affects base="0.9.6" version="0.9.6g"/>
4410 <affects base="0.9.6" version="0.9.6h"/>
4411 <fixed base="0.9.7" version="0.9.7a" date="20030219"/>
4412 <fixed base="0.9.6" version="0.9.6i" date="20030219"/>
4413 <advisory url="/news/secadv/20030219.txt"/>
4415 sl3_get_record in s3_pkt.c did not perform a MAC computation if an
4416 incorrect block cipher padding was used, causing an information leak
4417 (timing discrepancy) that may make it easier to launch cryptographic
4418 attacks that rely on distinguishing between padding and MAC
4419 verification errors, possibly leading to extraction of the original
4420 plaintext, aka the "Vaudenay timing attack."
4424 <issue public="20030319">
4425 <cve name="2003-0131"/>
4426 <affects base="0.9.6" version="0.9.6"/>
4427 <affects base="0.9.6" version="0.9.6a"/>
4428 <affects base="0.9.6" version="0.9.6b"/>
4429 <affects base="0.9.6" version="0.9.6c"/>
4430 <affects base="0.9.6" version="0.9.6d"/>
4431 <affects base="0.9.6" version="0.9.6e"/>
4432 <affects base="0.9.6" version="0.9.6f"/>
4433 <affects base="0.9.6" version="0.9.6g"/>
4434 <affects base="0.9.6" version="0.9.6h"/>
4435 <affects base="0.9.6" version="0.9.6i"/>
4436 <affects base="0.9.7" version="0.9.7"/>
4437 <affects base="0.9.7" version="0.9.7a"/>
4438 <fixed base="0.9.6" version="0.9.6j" date="20030410"/>
4439 <fixed base="0.9.7" version="0.9.7b" date="20030410"/>
4440 <advisory url="/news/secadv/20030319.txt"/>
4442 The SSL and TLS components allowed remote attackers to perform an
4443 unauthorized RSA private key operation via a modified Bleichenbacher
4444 attack that uses a large number of SSL or TLS connections using PKCS #1
4445 v1.5 padding that caused OpenSSL to leak information regarding the
4446 relationship between ciphertext and the associated plaintext, aka the
4447 "Klima-Pokorny-Rosa attack"
4451 <issue public="20030314">
4452 <cve name="2003-0147"/>
4453 <affects base="0.9.6" version="0.9.6"/>
4454 <affects base="0.9.6" version="0.9.6a"/>
4455 <affects base="0.9.6" version="0.9.6b"/>
4456 <affects base="0.9.6" version="0.9.6c"/>
4457 <affects base="0.9.6" version="0.9.6d"/>
4458 <affects base="0.9.6" version="0.9.6e"/>
4459 <affects base="0.9.6" version="0.9.6f"/>
4460 <affects base="0.9.6" version="0.9.6g"/>
4461 <affects base="0.9.6" version="0.9.6h"/>
4462 <affects base="0.9.6" version="0.9.6i"/>
4463 <affects base="0.9.7" version="0.9.7"/>
4464 <affects base="0.9.7" version="0.9.7a"/>
4465 <advisory url="/news/secadv/20030317.txt"/>
4466 <fixed base="0.9.7" version="0.9.7b" date="20030410"/>
4467 <fixed base="0.9.6" version="0.9.6j" date="20030410"/>
4469 RSA blinding was not enabled by default, which could allow local and
4470 remote attackers to obtain a server's private key by determining
4471 factors using timing differences on (1) the number of extra reductions
4472 during Montgomery reduction, and (2) the use of different integer
4473 multiplication algorithms ("Karatsuba" and normal).
4477 <issue public="20030930">
4478 <cve name="2003-0543"/>
4479 <affects base="0.9.6" version="0.9.6"/>
4480 <affects base="0.9.6" version="0.9.6a"/>
4481 <affects base="0.9.6" version="0.9.6b"/>
4482 <affects base="0.9.6" version="0.9.6c"/>
4483 <affects base="0.9.6" version="0.9.6d"/>
4484 <affects base="0.9.6" version="0.9.6e"/>
4485 <affects base="0.9.6" version="0.9.6f"/>
4486 <affects base="0.9.6" version="0.9.6g"/>
4487 <affects base="0.9.6" version="0.9.6h"/>
4488 <affects base="0.9.6" version="0.9.6i"/>
4489 <affects base="0.9.6" version="0.9.6j"/>
4490 <affects base="0.9.7" version="0.9.7"/>
4491 <affects base="0.9.7" version="0.9.7a"/>
4492 <affects base="0.9.7" version="0.9.7b"/>
4493 <fixed base="0.9.7" version="0.9.7c" date="20030930"/>
4494 <fixed base="0.9.6" version="0.9.6k" date="20030930"/>
4495 <advisory url="/news/secadv/20030930.txt"/>
4496 <reported source="NISCC"/>
4498 An integer overflow could allow remote attackers to cause a denial of
4499 service (crash) via an SSL client certificate with certain ASN.1 tag
4504 <issue public="20030930">
4505 <cve name="2003-0544"/>
4506 <affects base="0.9.7" version="0.9.7"/>
4507 <affects base="0.9.7" version="0.9.7a"/>
4508 <affects base="0.9.7" version="0.9.7b"/>
4509 <affects base="0.9.6" version="0.9.6"/>
4510 <affects base="0.9.6" version="0.9.6a"/>
4511 <affects base="0.9.6" version="0.9.6b"/>
4512 <affects base="0.9.6" version="0.9.6c"/>
4513 <affects base="0.9.6" version="0.9.6d"/>
4514 <affects base="0.9.6" version="0.9.6e"/>
4515 <affects base="0.9.6" version="0.9.6f"/>
4516 <affects base="0.9.6" version="0.9.6g"/>
4517 <affects base="0.9.6" version="0.9.6h"/>
4518 <affects base="0.9.6" version="0.9.6i"/>
4519 <affects base="0.9.6" version="0.9.6j"/>
4520 <fixed base="0.9.6" version="0.9.6k" date="20030930"/>
4521 <fixed base="0.9.7" version="0.9.7c" date="20030930"/>
4522 <advisory url="/news/secadv/20030930.txt"/>
4523 <reported source="NISCC"/>
4525 Incorrect tracking of the number of characters in certain
4526 ASN.1 inputs could allow remote attackers to cause a denial of
4527 service (crash) by sending an SSL client certificate that causes OpenSSL to
4528 read past the end of a buffer when the long form is used.
4532 <issue public="20030930">
4533 <cve name="2003-0545"/>
4534 <affects base="0.9.7" version="0.9.7"/>
4535 <affects base="0.9.7" version="0.9.7a"/>
4536 <affects base="0.9.7" version="0.9.7b"/>
4537 <fixed base="0.9.7" version="0.9.7c" date="20030930"/>
4538 <advisory url="/news/secadv/20030930.txt"/>
4539 <reported source="NISCC"/>
4541 Certain ASN.1 encodings that were rejected as invalid by the parser could
4542 trigger a bug in the deallocation of the corresponding data structure,
4543 corrupting the stack, leading to a crash.
4547 <issue public="20031104">
4548 <cve name="2003-0851"/>
4549 <affects base="0.9.6" version="0.9.6k"/>
4550 <fixed base="0.9.6" version="0.9.6l" date="20031104"/>
4551 <advisory url="/news/secadv/20031104.txt"/>
4552 <reported source="Novell"/>
4554 A flaw in OpenSSL 0.9.6k (only) would cause certain ASN.1 sequences to
4555 trigger a large recursion. On platforms such as Windows this large
4556 recursion cannot be handled correctly and so the bug causes OpenSSL to
4557 crash. A remote attacker could exploit this flaw if they can send
4558 arbitrary ASN.1 sequences which would cause OpenSSL to crash. This
4559 could be performed for example by sending a client certificate to a
4560 SSL/TLS enabled server which is configured to accept them.
4564 <issue public="20040317">
4565 <cve name="2004-0079"/>
4566 <affects base="0.9.6" version="0.9.6c"/>
4567 <affects base="0.9.6" version="0.9.6d"/>
4568 <affects base="0.9.6" version="0.9.6e"/>
4569 <affects base="0.9.6" version="0.9.6f"/>
4570 <affects base="0.9.6" version="0.9.6g"/>
4571 <affects base="0.9.6" version="0.9.6h"/>
4572 <affects base="0.9.6" version="0.9.6i"/>
4573 <affects base="0.9.6" version="0.9.6j"/>
4574 <affects base="0.9.6" version="0.9.6k"/>
4575 <affects base="0.9.6" version="0.9.6l"/>
4576 <affects base="0.9.7" version="0.9.7"/>
4577 <affects base="0.9.7" version="0.9.7a"/>
4578 <affects base="0.9.7" version="0.9.7b"/>
4579 <affects base="0.9.7" version="0.9.7c"/>
4580 <fixed base="0.9.7" version="0.9.7d" date="20040317"/>
4581 <fixed base="0.9.6" version="0.9.6m" date="20040317"/>
4582 <advisory url="/news/secadv/20040317.txt"/>
4583 <reported source="OpenSSL group"/>
4585 The Codenomicon TLS Test Tool uncovered a null-pointer assignment in the
4586 do_change_cipher_spec() function. A remote attacker could perform a
4587 carefully crafted SSL/TLS handshake against a server that used the
4588 OpenSSL library in such a way as to cause a crash.
4592 <issue public="20040317">
4593 <cve name="2004-0081"/>
4594 <affects base="0.9.6" version="0.9.6"/>
4595 <affects base="0.9.6" version="0.9.6a"/>
4596 <affects base="0.9.6" version="0.9.6b"/>
4597 <affects base="0.9.6" version="0.9.6c"/>
4598 <advisory url="/news/secadv/20030317.txt"/>
4599 <reported source="OpenSSL group"/>
4601 The Codenomicon TLS Test Tool found that some unknown message types
4602 were handled incorrectly, allowing a remote attacker to cause a denial
4603 of service (infinite loop).
4607 <issue public="20040317">
4608 <cve name="2004-0112"/>
4609 <affects base="0.9.7" version="0.9.7a"/>
4610 <affects base="0.9.7" version="0.9.7b"/>
4611 <affects base="0.9.7" version="0.9.7c"/>
4612 <fixed base="0.9.7" version="0.9.7d" date="20040317"/>
4613 <reported source="OpenSSL group (Stephen Henson)"/>
4614 <advisory url="/news/secadv/20040317.txt"/>
4616 A flaw in SSL/TLS handshaking code when using Kerberos ciphersuites.
4617 A remote attacker could perform a carefully crafted SSL/TLS handshake
4618 against a server configured to use Kerberos ciphersuites in such a way
4619 as to cause OpenSSL to crash. Most applications have no ability to
4620 use Kerberos ciphersuites and will therefore be unaffected.
4624 <issue public="20040930">
4625 <cve name="2004-0975"/>
4626 <affects base="0.9.7" version="0.9.7"/>
4627 <affects base="0.9.7" version="0.9.7a"/>
4628 <affects base="0.9.7" version="0.9.7b"/>
4629 <affects base="0.9.7" version="0.9.7c"/>
4630 <affects base="0.9.7" version="0.9.7d"/>
4631 <affects base="0.9.7" version="0.9.7e"/>
4632 <affects base="0.9.6" version="0.9.6"/>
4633 <affects base="0.9.6" version="0.9.6a"/>
4634 <affects base="0.9.6" version="0.9.6b"/>
4635 <affects base="0.9.6" version="0.9.6c"/>
4636 <affects base="0.9.6" version="0.9.6d"/>
4637 <affects base="0.9.6" version="0.9.6e"/>
4638 <affects base="0.9.6" version="0.9.6f"/>
4639 <affects base="0.9.6" version="0.9.6g"/>
4640 <affects base="0.9.6" version="0.9.6h"/>
4641 <affects base="0.9.6" version="0.9.6i"/>
4642 <affects base="0.9.6" version="0.9.6j"/>
4643 <affects base="0.9.6" version="0.9.6k"/>
4644 <affects base="0.9.6" version="0.9.6l"/>
4645 <affects base="0.9.6" version="0.9.6m"/>
4646 <fixed base="0.9.7" version="0.9.7f" date="20050322">
4647 <git hash="5fee606442a6738fd06a756d7076be53b7b7734c"/>
4649 <fixed base="0.9.6" version="0.9.6-cvs" date="20041114"/>
4650 <!-- der_chop was removed 20041114 -->
4653 The der_chop script created temporary files insecurely which could
4654 allow local users to overwrite files via a symlink attack on temporary
4655 files. Note that it is quite unlikely that a user would be using the
4656 redundant der_chop script, and this script was removed from the OpenSSL
4661 <issue public="20051011">
4662 <cve name="2005-2969"/>
4663 <affects base="0.9.7" version="0.9.7"/>
4664 <affects base="0.9.7" version="0.9.7a"/>
4665 <affects base="0.9.7" version="0.9.7b"/>
4666 <affects base="0.9.7" version="0.9.7c"/>
4667 <affects base="0.9.7" version="0.9.7d"/>
4668 <affects base="0.9.7" version="0.9.7e"/>
4669 <affects base="0.9.7" version="0.9.7f"/>
4670 <affects base="0.9.7" version="0.9.7g"/>
4671 <affects base="0.9.8" version="0.9.8"/>
4672 <affects base="0.9.6" version="0.9.6"/>
4673 <affects base="0.9.6" version="0.9.6a"/>
4674 <affects base="0.9.6" version="0.9.6b"/>
4675 <affects base="0.9.6" version="0.9.6c"/>
4676 <affects base="0.9.6" version="0.9.6d"/>
4677 <affects base="0.9.6" version="0.9.6e"/>
4678 <affects base="0.9.6" version="0.9.6f"/>
4679 <affects base="0.9.6" version="0.9.6g"/>
4680 <affects base="0.9.6" version="0.9.6h"/>
4681 <affects base="0.9.6" version="0.9.6i"/>
4682 <affects base="0.9.6" version="0.9.6j"/>
4683 <affects base="0.9.6" version="0.9.6k"/>
4684 <affects base="0.9.6" version="0.9.6l"/>
4685 <affects base="0.9.6" version="0.9.6m"/>
4686 <fixed base="0.9.7" version="0.9.7h" date="20051011"/>
4687 <fixed base="0.9.8" version="0.9.8a" date="20051011"/>
4689 <advisory url="/news/secadv/20051011.txt"/>
4690 <reported source="researcher"/>
4693 A deprecated option, SSL_OP_MISE_SSLV2_RSA_PADDING, could allow an
4694 attacker acting as a "man in the middle" to force a connection to
4695 downgrade to SSL 2.0 even if both parties support better protocols.
4699 <issue public="20060905">
4700 <cve name="2006-4339"/>
4701 <affects base="0.9.7" version="0.9.7"/>
4702 <affects base="0.9.7" version="0.9.7a"/>
4703 <affects base="0.9.7" version="0.9.7b"/>
4704 <affects base="0.9.7" version="0.9.7c"/>
4705 <affects base="0.9.7" version="0.9.7d"/>
4706 <affects base="0.9.7" version="0.9.7e"/>
4707 <affects base="0.9.7" version="0.9.7f"/>
4708 <affects base="0.9.7" version="0.9.7g"/>
4709 <affects base="0.9.7" version="0.9.7h"/>
4710 <affects base="0.9.7" version="0.9.7i"/>
4711 <affects base="0.9.7" version="0.9.7j"/>
4712 <affects base="0.9.8" version="0.9.8"/>
4713 <affects base="0.9.8" version="0.9.8a"/>
4714 <affects base="0.9.8" version="0.9.8b"/>
4715 <affects base="0.9.6" version="0.9.6"/>
4716 <affects base="0.9.6" version="0.9.6a"/>
4717 <affects base="0.9.6" version="0.9.6b"/>
4718 <affects base="0.9.6" version="0.9.6c"/>
4719 <affects base="0.9.6" version="0.9.6d"/>
4720 <affects base="0.9.6" version="0.9.6e"/>
4721 <affects base="0.9.6" version="0.9.6f"/>
4722 <affects base="0.9.6" version="0.9.6g"/>
4723 <affects base="0.9.6" version="0.9.6h"/>
4724 <affects base="0.9.6" version="0.9.6i"/>
4725 <affects base="0.9.6" version="0.9.6j"/>
4726 <affects base="0.9.6" version="0.9.6k"/>
4727 <affects base="0.9.6" version="0.9.6l"/>
4728 <affects base="0.9.6" version="0.9.6m"/>
4729 <fixed base="0.9.7" version="0.9.7k" date="20060905"/>
4730 <fixed base="0.9.8" version="0.9.8c" date="20060905"/>
4732 <advisory url="/news/secadv/20060905.txt"/>
4733 <reported source="openssl"/>
4736 Daniel Bleichenbacher discovered an attack on PKCS #1 v1.5
4737 signatures where under certain circumstances it may be possible
4738 for an attacker to forge a PKCS #1 v1.5 signature that would be incorrectly
4739 verified by OpenSSL.
4743 <issue public="20060928">
4744 <cve name="2006-2937"/>
4745 <affects base="0.9.7" version="0.9.7"/>
4746 <affects base="0.9.7" version="0.9.7a"/>
4747 <affects base="0.9.7" version="0.9.7b"/>
4748 <affects base="0.9.7" version="0.9.7c"/>
4749 <affects base="0.9.7" version="0.9.7d"/>
4750 <affects base="0.9.7" version="0.9.7e"/>
4751 <affects base="0.9.7" version="0.9.7f"/>
4752 <affects base="0.9.7" version="0.9.7g"/>
4753 <affects base="0.9.7" version="0.9.7h"/>
4754 <affects base="0.9.7" version="0.9.7i"/>
4755 <affects base="0.9.7" version="0.9.7j"/>
4756 <affects base="0.9.7" version="0.9.7k"/>
4757 <affects base="0.9.8" version="0.9.8"/>
4758 <affects base="0.9.8" version="0.9.8a"/>
4759 <affects base="0.9.8" version="0.9.8b"/>
4760 <affects base="0.9.8" version="0.9.8c"/>
4761 <fixed base="0.9.7" version="0.9.7l" date="20060928"/>
4762 <fixed base="0.9.8" version="0.9.8d" date="20060928"/>
4764 <advisory url="/news/secadv/20060928.txt"/>
4765 <reported source="openssl"/>
4768 During the parsing of certain invalid ASN.1 structures an error
4769 condition is mishandled. This can result in an infinite loop which
4770 consumes system memory
4774 <issue public="20060928">
4775 <cve name="2006-2940"/>
4776 <affects base="0.9.7" version="0.9.7"/>
4777 <affects base="0.9.7" version="0.9.7a"/>
4778 <affects base="0.9.7" version="0.9.7b"/>
4779 <affects base="0.9.7" version="0.9.7c"/>
4780 <affects base="0.9.7" version="0.9.7d"/>
4781 <affects base="0.9.7" version="0.9.7e"/>
4782 <affects base="0.9.7" version="0.9.7f"/>
4783 <affects base="0.9.7" version="0.9.7g"/>
4784 <affects base="0.9.7" version="0.9.7h"/>
4785 <affects base="0.9.7" version="0.9.7i"/>
4786 <affects base="0.9.7" version="0.9.7j"/>
4787 <affects base="0.9.7" version="0.9.7k"/>
4788 <affects base="0.9.8" version="0.9.8"/>
4789 <affects base="0.9.8" version="0.9.8a"/>
4790 <affects base="0.9.8" version="0.9.8b"/>
4791 <affects base="0.9.8" version="0.9.8c"/>
4792 <affects base="0.9.6" version="0.9.6"/>
4793 <affects base="0.9.6" version="0.9.6a"/>
4794 <affects base="0.9.6" version="0.9.6b"/>
4795 <affects base="0.9.6" version="0.9.6c"/>
4796 <affects base="0.9.6" version="0.9.6d"/>
4797 <affects base="0.9.6" version="0.9.6e"/>
4798 <affects base="0.9.6" version="0.9.6f"/>
4799 <affects base="0.9.6" version="0.9.6g"/>
4800 <affects base="0.9.6" version="0.9.6h"/>
4801 <affects base="0.9.6" version="0.9.6i"/>
4802 <affects base="0.9.6" version="0.9.6j"/>
4803 <affects base="0.9.6" version="0.9.6k"/>
4804 <affects base="0.9.6" version="0.9.6l"/>
4805 <affects base="0.9.6" version="0.9.6m"/>
4806 <fixed base="0.9.7" version="0.9.7l" date="20060928"/>
4807 <fixed base="0.9.8" version="0.9.8d" date="20060928"/>
4809 <advisory url="/news/secadv/20060928.txt"/>
4810 <reported source="openssl"/>
4813 Certain types of public key can take disproportionate amounts of
4814 time to process. This could be used by an attacker in a denial of
4819 <issue public="20060928">
4820 <cve name="2006-3738"/>
4821 <affects base="0.9.7" version="0.9.7"/>
4822 <affects base="0.9.7" version="0.9.7a"/>
4823 <affects base="0.9.7" version="0.9.7b"/>
4824 <affects base="0.9.7" version="0.9.7c"/>
4825 <affects base="0.9.7" version="0.9.7d"/>
4826 <affects base="0.9.7" version="0.9.7e"/>
4827 <affects base="0.9.7" version="0.9.7f"/>
4828 <affects base="0.9.7" version="0.9.7g"/>
4829 <affects base="0.9.7" version="0.9.7h"/>
4830 <affects base="0.9.7" version="0.9.7i"/>
4831 <affects base="0.9.7" version="0.9.7j"/>
4832 <affects base="0.9.7" version="0.9.7k"/>
4833 <affects base="0.9.8" version="0.9.8"/>
4834 <affects base="0.9.8" version="0.9.8a"/>
4835 <affects base="0.9.8" version="0.9.8b"/>
4836 <affects base="0.9.8" version="0.9.8c"/>
4837 <affects base="0.9.6" version="0.9.6"/>
4838 <affects base="0.9.6" version="0.9.6a"/>
4839 <affects base="0.9.6" version="0.9.6b"/>
4840 <affects base="0.9.6" version="0.9.6c"/>
4841 <affects base="0.9.6" version="0.9.6d"/>
4842 <affects base="0.9.6" version="0.9.6e"/>
4843 <affects base="0.9.6" version="0.9.6f"/>
4844 <affects base="0.9.6" version="0.9.6g"/>
4845 <affects base="0.9.6" version="0.9.6h"/>
4846 <affects base="0.9.6" version="0.9.6i"/>
4847 <affects base="0.9.6" version="0.9.6j"/>
4848 <affects base="0.9.6" version="0.9.6k"/>
4849 <affects base="0.9.6" version="0.9.6l"/>
4850 <affects base="0.9.6" version="0.9.6m"/>
4851 <fixed base="0.9.7" version="0.9.7l" date="20060928"/>
4852 <fixed base="0.9.8" version="0.9.8d" date="20060928"/>
4854 <advisory url="/news/secadv/20060928.txt"/>
4855 <reported source="openssl"/>
4858 A buffer overflow was discovered in the SSL_get_shared_ciphers()
4859 utility function. An attacker could send a list of ciphers to an
4860 application that uses this function and overrun a buffer.
4864 <issue public="20060928">
4865 <cve name="2006-4343"/>
4866 <affects base="0.9.7" version="0.9.7"/>
4867 <affects base="0.9.7" version="0.9.7a"/>
4868 <affects base="0.9.7" version="0.9.7b"/>
4869 <affects base="0.9.7" version="0.9.7c"/>
4870 <affects base="0.9.7" version="0.9.7d"/>
4871 <affects base="0.9.7" version="0.9.7e"/>
4872 <affects base="0.9.7" version="0.9.7f"/>
4873 <affects base="0.9.7" version="0.9.7g"/>
4874 <affects base="0.9.7" version="0.9.7h"/>
4875 <affects base="0.9.7" version="0.9.7i"/>
4876 <affects base="0.9.7" version="0.9.7j"/>
4877 <affects base="0.9.7" version="0.9.7k"/>
4878 <affects base="0.9.8" version="0.9.8"/>
4879 <affects base="0.9.8" version="0.9.8a"/>
4880 <affects base="0.9.8" version="0.9.8b"/>
4881 <affects base="0.9.8" version="0.9.8c"/>
4882 <affects base="0.9.6" version="0.9.6"/>
4883 <affects base="0.9.6" version="0.9.6a"/>
4884 <affects base="0.9.6" version="0.9.6b"/>
4885 <affects base="0.9.6" version="0.9.6c"/>
4886 <affects base="0.9.6" version="0.9.6d"/>
4887 <affects base="0.9.6" version="0.9.6e"/>
4888 <affects base="0.9.6" version="0.9.6f"/>
4889 <affects base="0.9.6" version="0.9.6g"/>
4890 <affects base="0.9.6" version="0.9.6h"/>
4891 <affects base="0.9.6" version="0.9.6i"/>
4892 <affects base="0.9.6" version="0.9.6j"/>
4893 <affects base="0.9.6" version="0.9.6k"/>
4894 <affects base="0.9.6" version="0.9.6l"/>
4895 <affects base="0.9.6" version="0.9.6m"/>
4896 <fixed base="0.9.7" version="0.9.7l" date="20060928"/>
4897 <fixed base="0.9.8" version="0.9.8d" date="20060928"/>
4899 <advisory url="/news/secadv/20060928.txt"/>
4900 <reported source="openssl"/>
4903 A flaw in the SSLv2 client code was discovered. When a client
4904 application used OpenSSL to create an SSLv2 connection to a malicious
4905 server, that server could cause the client to crash.
4909 <issue public="20071012">
4910 <cve name="2007-4995"/>
4911 <affects base="0.9.8" version="0.9.8"/>
4912 <affects base="0.9.8" version="0.9.8a"/>
4913 <affects base="0.9.8" version="0.9.8b"/>
4914 <affects base="0.9.8" version="0.9.8c"/>
4915 <affects base="0.9.8" version="0.9.8d"/>
4916 <affects base="0.9.8" version="0.9.8e"/>
4917 <fixed base="0.9.8" version="0.9.8f" date="20071012"/>
4918 <advisory url="/news/secadv/20071012.txt"/>
4919 <reported source="Andy Polyakov"/>
4922 A flaw in DTLS support. An attacker
4923 could create a malicious client or server that could trigger a heap
4924 overflow. This is possibly exploitable to run arbitrary code, but it has
4929 <issue public="20071012">
4930 <cve name="2007-5135"/>
4931 <affects base="0.9.8" version="0.9.8"/>
4932 <affects base="0.9.8" version="0.9.8a"/>
4933 <affects base="0.9.8" version="0.9.8b"/>
4934 <affects base="0.9.8" version="0.9.8c"/>
4935 <affects base="0.9.8" version="0.9.8d"/>
4936 <affects base="0.9.8" version="0.9.8e"/>
4937 <fixed base="0.9.8" version="0.9.8f" date="20071012"/>
4938 <advisory url="/news/secadv/20071012.txt"/>
4939 <reported source="Moritz Jodeit"/>
4942 A flaw was found in the SSL_get_shared_ciphers() utility function. An
4943 attacker could send a list of ciphers to an application that used this
4944 function and overrun a buffer with a single byte. Few
4945 applications make use of this vulnerable function and generally it is used
4946 only when applications are compiled for debugging.
4950 <issue public="20071129">
4951 <cve name="2007-5502"/>
4952 <advisory url="/news/secadv/20071129.txt"/>
4953 <reported source="Geoff Lowe"/>
4954 <affects base="fips-1.1" version="fips-1.1.1"/>
4955 <fixed base="fips-1.1" version="fips-1.1.2" date="20071201"/>
4957 The PRNG implementation for the OpenSSL FIPS Object Module 1.1.1 does
4958 not perform auto-seeding during the FIPS self-test, which generates
4959 random data that is more predictable than expected and makes it easier
4960 for attackers to bypass protection mechanisms that rely on the
4965 <issue public="20080528">
4966 <cve name="2008-0891"/>
4967 <affects base="0.9.8" version="0.9.8f"/>
4968 <affects base="0.9.8" version="0.9.8g"/>
4969 <fixed base="0.9.8" version="0.9.8h" date="20080528"/>
4970 <advisory url="/news/secadv/20080528.txt"/>
4971 <reported source="codenomicon"/>
4973 Testing using the Codenomicon TLS test suite discovered a flaw in the
4974 handling of server name extension data in OpenSSL 0.9.8f and OpenSSL
4975 0.9.8g. If OpenSSL has been compiled using the non-default TLS server
4976 name extensions, a remote attacker could send a carefully crafted
4977 packet to a server application using OpenSSL and cause it to crash.
4981 <issue public="20080528">
4982 <cve name="2008-1672"/>
4983 <affects base="0.9.8" version="0.9.8f"/>
4984 <affects base="0.9.8" version="0.9.8g"/>
4985 <fixed base="0.9.8" version="0.9.8h" date="20080528"/>
4986 <advisory url="/news/secadv/20080528.txt"/>
4987 <reported source="codenomicon"/>
4989 Testing using the Codenomicon TLS test suite discovered a flaw if the
4990 'Server Key exchange message' is omitted from a TLS handshake in
4991 OpenSSL 0.9.8f and OpenSSL 0.9.8g. If a client connects to a
4992 malicious server with particular cipher suites, the server could cause
4993 the client to crash.
4997 <issue public="20090107">
4998 <cve name="2008-5077"/>
4999 <affects base="0.9.8" version="0.9.8"/>
5000 <affects base="0.9.8" version="0.9.8a"/>
5001 <affects base="0.9.8" version="0.9.8b"/>
5002 <affects base="0.9.8" version="0.9.8c"/>
5003 <affects base="0.9.8" version="0.9.8d"/>
5004 <affects base="0.9.8" version="0.9.8e"/>
5005 <affects base="0.9.8" version="0.9.8f"/>
5006 <affects base="0.9.8" version="0.9.8g"/>
5007 <affects base="0.9.8" version="0.9.8h"/>
5008 <affects base="0.9.8" version="0.9.8i"/>
5009 <fixed base="0.9.8" version="0.9.8j" date="20090107"/>
5010 <advisory url="/news/secadv/20090107.txt"/>
5011 <reported source="google"/>
5014 The Google Security Team discovered several functions inside OpenSSL
5015 incorrectly checked the result after calling the EVP_VerifyFinal
5016 function, allowing a malformed signature to be treated as a good
5017 signature rather than as an error. This issue affected the signature
5018 checks on DSA and ECDSA keys used with SSL/TLS. One way to exploit
5019 this flaw would be for a remote attacker who is in control of a
5020 malicious server or who can use a 'man in the middle' attack to
5021 present a malformed SSL/TLS signature from a certificate chain to a
5022 vulnerable client, bypassing validation.
5026 <issue public="20090325">
5027 <cve name="2009-0590"/>
5028 <affects base="0.9.8" version="0.9.8"/>
5029 <affects base="0.9.8" version="0.9.8a"/>
5030 <affects base="0.9.8" version="0.9.8b"/>
5031 <affects base="0.9.8" version="0.9.8c"/>
5032 <affects base="0.9.8" version="0.9.8d"/>
5033 <affects base="0.9.8" version="0.9.8e"/>
5034 <affects base="0.9.8" version="0.9.8f"/>
5035 <affects base="0.9.8" version="0.9.8g"/>
5036 <affects base="0.9.8" version="0.9.8h"/>
5037 <affects base="0.9.8" version="0.9.8i"/>
5038 <affects base="0.9.8" version="0.9.8j"/>
5039 <fixed base="0.9.8" version="0.9.8k" date="20090325"/>
5040 <advisory url="/news/secadv/20090325.txt"/>
5042 The function ASN1_STRING_print_ex() when used to print a BMPString or
5043 UniversalString will crash with an invalid memory access if the
5044 encoded length of the string is illegal. Any OpenSSL application
5045 which prints out the contents of a certificate could be affected by
5046 this bug, including SSL servers, clients and S/MIME software.
5050 <issue public="20090325">
5051 <cve name="2009-0591"/>
5052 <affects base="0.9.8" version="0.9.8h"/>
5053 <affects base="0.9.8" version="0.9.8i"/>
5054 <affects base="0.9.8" version="0.9.8j"/>
5055 <fixed base="0.9.8" version="0.9.8k" date="20090325"/>
5056 <advisory url="/news/secadv/20090325.txt"/>
5057 <reported source="Ivan Nestlerode, IBM"/>
5059 The function CMS_verify() does not correctly handle an error condition
5060 involving malformed signed attributes. This will cause an invalid set
5061 of signed attributes to appear valid and content digests will not be
5066 <issue public="20090325">
5067 <cve name="2009-0789"/>
5068 <affects base="0.9.8" version="0.9.8"/>
5069 <affects base="0.9.8" version="0.9.8a"/>
5070 <affects base="0.9.8" version="0.9.8b"/>
5071 <affects base="0.9.8" version="0.9.8c"/>
5072 <affects base="0.9.8" version="0.9.8d"/>
5073 <affects base="0.9.8" version="0.9.8e"/>
5074 <affects base="0.9.8" version="0.9.8f"/>
5075 <affects base="0.9.8" version="0.9.8g"/>
5076 <affects base="0.9.8" version="0.9.8h"/>
5077 <affects base="0.9.8" version="0.9.8i"/>
5078 <affects base="0.9.8" version="0.9.8j"/>
5079 <fixed base="0.9.8" version="0.9.8k" date="20090325"/>
5080 <reported source="Paolo Ganci"/>
5081 <advisory url="/news/secadv/20090325.txt"/>
5083 When a malformed ASN1 structure is received it's contents are freed up and
5084 zeroed and an error condition returned. On a small number of platforms where
5085 sizeof(long) < sizeof(void *) (for example WIN64) this can cause an invalid
5086 memory access later resulting in a crash when some invalid structures are
5087 read, for example RSA public keys.
5091 <issue public="20090602">
5092 <cve name="2009-1386"/>
5093 <affects base="0.9.8" version="0.9.8"/>
5094 <affects base="0.9.8" version="0.9.8a"/>
5095 <affects base="0.9.8" version="0.9.8b"/>
5096 <affects base="0.9.8" version="0.9.8c"/>
5097 <affects base="0.9.8" version="0.9.8d"/>
5098 <affects base="0.9.8" version="0.9.8e"/>
5099 <affects base="0.9.8" version="0.9.8f"/>
5100 <affects base="0.9.8" version="0.9.8g"/>
5101 <affects base="0.9.8" version="0.9.8h"/>
5102 <fixed base="0.9.8" version="0.9.8i" date="20080915">
5103 <git hash="1cbf663a6c89dcf8f7706d30a8bae675e2e0199a"/>
5105 <reported source="Alex Lam"/>
5107 Fix a NULL pointer dereference if a DTLS server recieved
5108 ChangeCipherSpec as first record.
5109 A remote attacker could use this flaw to cause a DTLS server to crash
5113 <issue public="20091105">
5114 <cve name="2009-3555"/>
5115 <affects base="0.9.8" version="0.9.8"/>
5116 <affects base="0.9.8" version="0.9.8a"/>
5117 <affects base="0.9.8" version="0.9.8b"/>
5118 <affects base="0.9.8" version="0.9.8c"/>
5119 <affects base="0.9.8" version="0.9.8d"/>
5120 <affects base="0.9.8" version="0.9.8e"/>
5121 <affects base="0.9.8" version="0.9.8f"/>
5122 <affects base="0.9.8" version="0.9.8g"/>
5123 <affects base="0.9.8" version="0.9.8h"/>
5124 <affects base="0.9.8" version="0.9.8i"/>
5125 <affects base="0.9.8" version="0.9.8j"/>
5126 <affects base="0.9.8" version="0.9.8k"/>
5127 <affects base="0.9.8" version="0.9.8l"/>
5128 <fixed base="0.9.8" version="0.9.8m" date="20100120"/>
5129 <advisory url="/news/secadv/20091111.txt"/>
5131 Implement RFC5746 to address vulnerabilities in SSL/TLS renegotiation.
5135 <issue public="20090205">
5136 <cve name="2009-1387"/>
5137 <advisory url="https://rt.openssl.org/Ticket/Display.html?id=1838&user=guest&pass=guest"/>
5138 <affects base="0.9.8" version="0.9.8"/>
5139 <affects base="0.9.8" version="0.9.8a"/>
5140 <affects base="0.9.8" version="0.9.8b"/>
5141 <affects base="0.9.8" version="0.9.8c"/>
5142 <affects base="0.9.8" version="0.9.8d"/>
5143 <affects base="0.9.8" version="0.9.8e"/>
5144 <affects base="0.9.8" version="0.9.8f"/>
5145 <affects base="0.9.8" version="0.9.8g"/>
5146 <affects base="0.9.8" version="0.9.8h"/>
5147 <affects base="0.9.8" version="0.9.8i"/>
5148 <affects base="0.9.8" version="0.9.8j"/>
5149 <affects base="0.9.8" version="0.9.8k"/>
5150 <affects base="0.9.8" version="0.9.8l"/>
5151 <fixed base="0.9.8" version="0.9.8m" date="20100120"/>
5152 <reported source="Robin Seggelmann"/>
5154 Fix denial of service flaw due in the DTLS implementation. A
5155 remote attacker could use this flaw to cause a DTLS server to crash.
5159 <issue public="20090512">
5160 <cve name="2009-1377"/>
5161 <advisory url="https://rt.openssl.org/Ticket/Display.html?id=1930&user=guest&pass=guest"/>
5162 <affects base="0.9.8" version="0.9.8"/>
5163 <affects base="0.9.8" version="0.9.8a"/>
5164 <affects base="0.9.8" version="0.9.8b"/>
5165 <affects base="0.9.8" version="0.9.8c"/>
5166 <affects base="0.9.8" version="0.9.8d"/>
5167 <affects base="0.9.8" version="0.9.8e"/>
5168 <affects base="0.9.8" version="0.9.8f"/>
5169 <affects base="0.9.8" version="0.9.8g"/>
5170 <affects base="0.9.8" version="0.9.8h"/>
5171 <affects base="0.9.8" version="0.9.8i"/>
5172 <affects base="0.9.8" version="0.9.8j"/>
5173 <affects base="0.9.8" version="0.9.8k"/>
5174 <affects base="0.9.8" version="0.9.8l"/>
5175 <fixed base="0.9.8" version="0.9.8m" date="20100120">
5176 <git hash="88b48dc68024dcc437da4296c9fb04419b0ccbe1"/>
5178 <reported source="Daniel Mentz, Robin Seggelmann"/>
5180 Fix a denial of service flaw in the DTLS implementation.
5181 Records are buffered if they arrive with a future epoch to be
5182 processed after finishing the corresponding handshake. There is
5183 currently no limitation to this buffer allowing an attacker to perform
5184 a DOS attack to a DTLS server by sending records with future epochs until there is no
5189 <issue public="20090512">
5190 <cve name="2009-1378"/>
5191 <advisory url="https://rt.openssl.org/Ticket/Display.html?id=1931&user=guest&pass=guest"/>
5192 <affects base="0.9.8" version="0.9.8"/>
5193 <affects base="0.9.8" version="0.9.8a"/>
5194 <affects base="0.9.8" version="0.9.8b"/>
5195 <affects base="0.9.8" version="0.9.8c"/>
5196 <affects base="0.9.8" version="0.9.8d"/>
5197 <affects base="0.9.8" version="0.9.8e"/>
5198 <affects base="0.9.8" version="0.9.8f"/>
5199 <affects base="0.9.8" version="0.9.8g"/>
5200 <affects base="0.9.8" version="0.9.8h"/>
5201 <affects base="0.9.8" version="0.9.8i"/>
5202 <affects base="0.9.8" version="0.9.8j"/>
5203 <affects base="0.9.8" version="0.9.8k"/>
5204 <affects base="0.9.8" version="0.9.8l"/>
5205 <fixed base="0.9.8" version="0.9.8m" date="20100120">
5206 <git hash="abda7c114791fa7fe95672ec7a66fc4733c40dbc"/>
5208 <reported source="Daniel Mentz, Robin Seggelmann"/>
5210 Fix a denial of service flaw in the DTLS implementation.
5211 In dtls1_process_out_of_seq_message() the check if the current message
5212 is already buffered was missing. For every new message was memory
5213 allocated, allowing an attacker to perform an denial of service attack
5214 against a DTLS server by sending out of seq handshake messages until there is no memory
5219 <issue public="20090512">
5220 <cve name="2009-1379"/>
5221 <advisory url="https://rt.openssl.org/Ticket/Display.html?id=1923&user=guest&pass=guest"/>
5222 <affects base="0.9.8" version="0.9.8"/>
5223 <affects base="0.9.8" version="0.9.8a"/>
5224 <affects base="0.9.8" version="0.9.8b"/>
5225 <affects base="0.9.8" version="0.9.8c"/>
5226 <affects base="0.9.8" version="0.9.8d"/>
5227 <affects base="0.9.8" version="0.9.8e"/>
5228 <affects base="0.9.8" version="0.9.8f"/>
5229 <affects base="0.9.8" version="0.9.8g"/>
5230 <affects base="0.9.8" version="0.9.8h"/>
5231 <affects base="0.9.8" version="0.9.8i"/>
5232 <affects base="0.9.8" version="0.9.8j"/>
5233 <affects base="0.9.8" version="0.9.8k"/>
5234 <affects base="0.9.8" version="0.9.8l"/>
5235 <fixed base="0.9.8" version="0.9.8m" date="20100120">
5236 <git hash="561cbe567846a376153bea7f1f2d061e78029c2d"/>
5238 <reported source="Daniel Mentz, Robin Seggelmann"/>
5240 Use-after-free vulnerability in the dtls1_retrieve_buffered_fragment
5241 function could cause a client accessing a malicious DTLS server to
5246 <issue public="20100113">
5247 <cve name="2009-4355"/>
5248 <affects base="0.9.8" version="0.9.8"/>
5249 <affects base="0.9.8" version="0.9.8a"/>
5250 <affects base="0.9.8" version="0.9.8b"/>
5251 <affects base="0.9.8" version="0.9.8c"/>
5252 <affects base="0.9.8" version="0.9.8d"/>
5253 <affects base="0.9.8" version="0.9.8e"/>
5254 <affects base="0.9.8" version="0.9.8f"/>
5255 <affects base="0.9.8" version="0.9.8g"/>
5256 <affects base="0.9.8" version="0.9.8h"/>
5257 <affects base="0.9.8" version="0.9.8i"/>
5258 <affects base="0.9.8" version="0.9.8j"/>
5259 <affects base="0.9.8" version="0.9.8k"/>
5260 <affects base="0.9.8" version="0.9.8l"/>
5261 <fixed base="0.9.8" version="0.9.8m" date="20100120">
5262 <git hash="1b31b5ad560b16e2fe1cad54a755e3e6b5e778a3"/>
5264 <reported source="Michael K Johnson and Andy Grimm (rPath)"/>
5266 A memory leak in the zlib_stateful_finish function in crypto/comp/c_zlib.c
5267 allows remote attackers to cause a denial of service
5268 via vectors that trigger incorrect calls to the CRYPTO_cleanup_all_ex_data
5273 <issue public="20100223">
5274 <cve name="2009-3245"/>
5275 <affects base="0.9.8" version="0.9.8"/>
5276 <affects base="0.9.8" version="0.9.8a"/>
5277 <affects base="0.9.8" version="0.9.8b"/>
5278 <affects base="0.9.8" version="0.9.8c"/>
5279 <affects base="0.9.8" version="0.9.8d"/>
5280 <affects base="0.9.8" version="0.9.8e"/>
5281 <affects base="0.9.8" version="0.9.8f"/>
5282 <affects base="0.9.8" version="0.9.8g"/>
5283 <affects base="0.9.8" version="0.9.8h"/>
5284 <affects base="0.9.8" version="0.9.8i"/>
5285 <affects base="0.9.8" version="0.9.8j"/>
5286 <affects base="0.9.8" version="0.9.8k"/>
5287 <affects base="0.9.8" version="0.9.8l"/>
5288 <fixed base="0.9.8" version="0.9.8m" date="20100120">
5289 <git hash="7e4cae1d2f555cbe9226b377aff4b56c9f7ddd4d"/>
5291 <reported source="Martin Olsson, Neel Mehta"/>
5293 It was discovered that OpenSSL did not always check the return value of the
5294 bn_wexpand() function. An attacker able to trigger a memory allocation failure
5295 in that function could cause an application using the OpenSSL library to crash
5296 or, possibly, execute arbitrary code
5300 <issue public="20100119">
5301 <cve name="2010-0433"/>
5302 <affects base="0.9.8" version="0.9.8"/>
5303 <affects base="0.9.8" version="0.9.8a"/>
5304 <affects base="0.9.8" version="0.9.8b"/>
5305 <affects base="0.9.8" version="0.9.8c"/>
5306 <affects base="0.9.8" version="0.9.8d"/>
5307 <affects base="0.9.8" version="0.9.8e"/>
5308 <affects base="0.9.8" version="0.9.8f"/>
5309 <affects base="0.9.8" version="0.9.8g"/>
5310 <affects base="0.9.8" version="0.9.8h"/>
5311 <affects base="0.9.8" version="0.9.8i"/>
5312 <affects base="0.9.8" version="0.9.8j"/>
5313 <affects base="0.9.8" version="0.9.8k"/>
5314 <affects base="0.9.8" version="0.9.8l"/>
5315 <affects base="0.9.8" version="0.9.8m"/>
5316 <fixed base="0.9.8" version="0.9.8n" date="20100324">
5317 <git hash="cca1cd9a3447dd067503e4a85ebd1679ee78a48e"/>
5319 <reported source="Todd Rinaldo, Tomas Hoger (Red Hat)"/>
5321 A missing return value check flaw was discovered in OpenSSL, that could
5322 possibly cause OpenSSL to call a Kerberos library function with invalid
5323 arguments, resulting in a NULL pointer dereference crash in the MIT
5324 Kerberos library. In certain configurations, a remote attacker could use
5325 this flaw to crash a TLS/SSL server using OpenSSL by requesting Kerberos
5326 cipher suites during the TLS handshake
5330 <issue public="20100324">
5331 <cve name="2010-0740"/>
5332 <affects base="0.9.8" version="0.9.8f"/>
5333 <affects base="0.9.8" version="0.9.8g"/>
5334 <affects base="0.9.8" version="0.9.8h"/>
5335 <affects base="0.9.8" version="0.9.8i"/>
5336 <affects base="0.9.8" version="0.9.8j"/>
5337 <affects base="0.9.8" version="0.9.8k"/>
5338 <affects base="0.9.8" version="0.9.8l"/>
5339 <affects base="0.9.8" version="0.9.8m"/>
5340 <fixed base="0.9.8" version="0.9.8n" date="20100324"/>
5341 <advisory url="/news/secadv/20100324.txt"/>
5342 <reported source="Bodo Moeller and Adam Langley (Google)"/>
5344 In TLS connections, certain incorrectly formatted records can cause an
5345 OpenSSL client or server to crash due to a read attempt at NULL.
5349 <issue public="20100601">
5350 <cve name="2010-0742"/>
5351 <affects base="1.0.0" version="1.0.0"/>
5352 <affects base="0.9.8" version="0.9.8h"/>
5353 <affects base="0.9.8" version="0.9.8i"/>
5354 <affects base="0.9.8" version="0.9.8j"/>
5355 <affects base="0.9.8" version="0.9.8k"/>
5356 <affects base="0.9.8" version="0.9.8l"/>
5357 <affects base="0.9.8" version="0.9.8m"/>
5358 <affects base="0.9.8" version="0.9.8n"/>
5359 <fixed base="0.9.8" version="0.9.8o" date="20100601"/>
5360 <fixed base="1.0.0" version="1.0.0a" date="20100601"/>
5361 <advisory url="/news/secadv/20100601.txt"/>
5362 <reported source="Ronald Moesbergen"/>
5364 A flaw in the handling of CMS structures containing OriginatorInfo was found which
5365 could lead to a write to invalid memory address or double free. CMS support is
5366 disabled by default in OpenSSL 0.9.8 versions.
5370 <issue public="20100601">
5371 <cve name="2010-1633"/>
5372 <affects base="1.0.0" version="1.0.0"/>
5373 <fixed base="1.0.0" version="1.0.0a" date="20100601"/>
5374 <advisory url="/news/secadv/20100601.txt"/>
5375 <reported source="Peter-Michael Hager"/>
5377 An invalid Return value check in pkey_rsa_verifyrecover was
5378 discovered. When verification recovery fails for RSA keys an
5379 uninitialised buffer with an undefined length is returned instead of
5380 an error code. This could lead to an information leak.
5384 <issue public="20101116">
5385 <cve name="2010-3864"/>
5386 <affects base="0.9.8" version="0.9.8"/>
5387 <affects base="0.9.8" version="0.9.8a"/>
5388 <affects base="0.9.8" version="0.9.8b"/>
5389 <affects base="0.9.8" version="0.9.8c"/>
5390 <affects base="0.9.8" version="0.9.8d"/>
5391 <affects base="0.9.8" version="0.9.8e"/>
5392 <affects base="0.9.8" version="0.9.8f"/>
5393 <affects base="0.9.8" version="0.9.8g"/>
5394 <affects base="0.9.8" version="0.9.8h"/>
5395 <affects base="0.9.8" version="0.9.8i"/>
5396 <affects base="0.9.8" version="0.9.8j"/>
5397 <affects base="0.9.8" version="0.9.8k"/>
5398 <affects base="0.9.8" version="0.9.8l"/>
5399 <affects base="0.9.8" version="0.9.8m"/>
5400 <affects base="0.9.8" version="0.9.8n"/>
5401 <affects base="0.9.8" version="0.9.8o"/>
5402 <affects base="1.0.0" version="1.0.0"/>
5403 <affects base="1.0.0" version="1.0.0a"/>
5404 <fixed base="1.0.0" version="1.0.0b" date="20101116"/>
5405 <fixed base="0.9.8" version="0.9.8p" date="20101116"/>
5406 <advisory url="/news/secadv/20101116.txt"/>
5407 <reported source="Rob Hulswit"/>
5410 A flaw in the OpenSSL TLS server extension code parsing which on
5411 affected servers can be exploited in a buffer overrun attack. Any
5412 OpenSSL based TLS server is vulnerable if it is multi-threaded and
5413 uses OpenSSL's internal caching mechanism. Servers that are
5414 multi-process and/or disable internal session caching are NOT
5420 <issue public="20101202">
5421 <cve name="2010-4252"/>
5422 <affects base="1.0.0" version="1.0.0"/>
5423 <affects base="1.0.0" version="1.0.0a"/>
5424 <affects base="1.0.0" version="1.0.0b"/>
5425 <fixed base="1.0.0" version="1.0.0c" date="20101202"/>
5426 <advisory url="/news/secadv/20101202.txt"/>
5427 <reported source="Sebastian Martini"/>
5429 An error in OpenSSL's experimental J-PAKE implementation which could
5430 lead to successful validation by someone with no knowledge of the
5431 shared secret. The OpenSSL Team still consider the implementation of
5432 J-PAKE to be experimental and is not compiled by default.
5436 <issue public="20101202">
5437 <cve name="2010-4180"/>
5438 <affects base="0.9.8" version="0.9.8"/>
5439 <affects base="0.9.8" version="0.9.8a"/>
5440 <affects base="0.9.8" version="0.9.8b"/>
5441 <affects base="0.9.8" version="0.9.8c"/>
5442 <affects base="0.9.8" version="0.9.8d"/>
5443 <affects base="0.9.8" version="0.9.8e"/>
5444 <affects base="0.9.8" version="0.9.8f"/>
5445 <affects base="0.9.8" version="0.9.8g"/>
5446 <affects base="0.9.8" version="0.9.8h"/>
5447 <affects base="0.9.8" version="0.9.8i"/>
5448 <affects base="0.9.8" version="0.9.8j"/>
5449 <affects base="0.9.8" version="0.9.8k"/>
5450 <affects base="0.9.8" version="0.9.8l"/>
5451 <affects base="0.9.8" version="0.9.8m"/>
5452 <affects base="0.9.8" version="0.9.8n"/>
5453 <affects base="0.9.8" version="0.9.8o"/>
5454 <affects base="0.9.8" version="0.9.8p"/>
5455 <affects base="1.0.0" version="1.0.0"/>
5456 <affects base="1.0.0" version="1.0.0a"/>
5457 <affects base="1.0.0" version="1.0.0b"/>
5458 <fixed base="1.0.0" version="1.0.0c" date="20101202"/>
5459 <fixed base="0.9.8" version="0.9.8q" date="20101202"/>
5460 <advisory url="/news/secadv/20101202.txt"/>
5461 <reported source="Martin Rex"/>
5463 A flaw in the OpenSSL SSL/TLS server code where an old bug workaround
5464 allows malicious clients to modify the stored session cache
5465 ciphersuite. In some cases the ciphersuite can be downgraded to a
5466 weaker one on subsequent connections. This issue only affects OpenSSL
5467 based SSL/TLS server if it uses OpenSSL's internal caching mechanisms
5468 and the SSL_OP_NETSCAPE_REUSE_CIPHER_CHANGE_BUG flag (many
5469 applications enable this by using the SSL_OP_ALL option).
5473 <issue public="20110906">
5474 <cve name="2011-3207"/>
5475 <affects base="1.0.0" version="1.0.0"/>
5476 <affects base="1.0.0" version="1.0.0a"/>
5477 <affects base="1.0.0" version="1.0.0b"/>
5478 <affects base="1.0.0" version="1.0.0c"/>
5479 <affects base="1.0.0" version="1.0.0d"/>
5480 <fixed base="1.0.0" version="1.0.0e" date="20110906"/>
5481 <advisory url="/news/secadv/20110906.txt"/>
5482 <reported source="Kaspar Brand"/>
5484 Under certain circumstances OpenSSL's internal certificate
5485 verification routines can incorrectly accept a CRL whose nextUpdate
5486 field is in the past. Applications are only affected by the CRL
5487 checking vulnerability if they enable OpenSSL's internal CRL checking
5488 which is off by default. Applications which use their own custom CRL
5489 checking (such as Apache) are not affected.
5493 <issue public="20110906">
5494 <cve name="2011-3210"/>
5495 <affects base="0.9.8" version="0.9.8"/>
5496 <affects base="0.9.8" version="0.9.8a"/>
5497 <affects base="0.9.8" version="0.9.8b"/>
5498 <affects base="0.9.8" version="0.9.8c"/>
5499 <affects base="0.9.8" version="0.9.8d"/>
5500 <affects base="0.9.8" version="0.9.8e"/>
5501 <affects base="0.9.8" version="0.9.8f"/>
5502 <affects base="0.9.8" version="0.9.8g"/>
5503 <affects base="0.9.8" version="0.9.8h"/>
5504 <affects base="0.9.8" version="0.9.8i"/>
5505 <affects base="0.9.8" version="0.9.8j"/>
5506 <affects base="0.9.8" version="0.9.8k"/>
5507 <affects base="0.9.8" version="0.9.8l"/>
5508 <affects base="0.9.8" version="0.9.8m"/>
5509 <affects base="0.9.8" version="0.9.8n"/>
5510 <affects base="0.9.8" version="0.9.8o"/>
5511 <affects base="0.9.8" version="0.9.8p"/>
5512 <affects base="0.9.8" version="0.9.8q"/>
5513 <affects base="0.9.8" version="0.9.8r"/>
5514 <affects base="1.0.0" version="1.0.0"/>
5515 <affects base="1.0.0" version="1.0.0a"/>
5516 <affects base="1.0.0" version="1.0.0b"/>
5517 <affects base="1.0.0" version="1.0.0c"/>
5518 <affects base="1.0.0" version="1.0.0d"/>
5519 <fixed base="1.0.0" version="1.0.0e" date="20110906"/>
5520 <advisory url="/news/secadv/20110906.txt"/>
5521 <reported source="Adam Langley"/>
5523 OpenSSL server code for ephemeral ECDH ciphersuites is not
5524 thread-safe, and furthermore can crash if a client violates the
5525 protocol by sending handshake messages in incorrect order. Only
5526 server-side applications that specifically support ephemeral ECDH
5527 ciphersuites are affected, and only if ephemeral ECDH ciphersuites are
5528 enabled in the configuration.
5532 <issue public="20120104">
5533 <cve name="2011-4108"/>
5534 <affects base="0.9.8" version="0.9.8"/>
5535 <affects base="0.9.8" version="0.9.8a"/>
5536 <affects base="0.9.8" version="0.9.8b"/>
5537 <affects base="0.9.8" version="0.9.8c"/>
5538 <affects base="0.9.8" version="0.9.8d"/>
5539 <affects base="0.9.8" version="0.9.8e"/>
5540 <affects base="0.9.8" version="0.9.8f"/>
5541 <affects base="0.9.8" version="0.9.8g"/>
5542 <affects base="0.9.8" version="0.9.8h"/>
5543 <affects base="0.9.8" version="0.9.8i"/>
5544 <affects base="0.9.8" version="0.9.8j"/>
5545 <affects base="0.9.8" version="0.9.8k"/>
5546 <affects base="0.9.8" version="0.9.8l"/>
5547 <affects base="0.9.8" version="0.9.8m"/>
5548 <affects base="0.9.8" version="0.9.8n"/>
5549 <affects base="0.9.8" version="0.9.8o"/>
5550 <affects base="0.9.8" version="0.9.8p"/>
5551 <affects base="0.9.8" version="0.9.8q"/>
5552 <affects base="0.9.8" version="0.9.8r"/>
5553 <affects base="1.0.0" version="1.0.0"/>
5554 <affects base="1.0.0" version="1.0.0a"/>
5555 <affects base="1.0.0" version="1.0.0b"/>
5556 <affects base="1.0.0" version="1.0.0c"/>
5557 <affects base="1.0.0" version="1.0.0d"/>
5558 <affects base="1.0.0" version="1.0.0e"/>
5559 <fixed base="1.0.0" version="1.0.0f" date="20120104"/>
5560 <fixed base="0.9.8" version="0.9.8s" date="20120104"/>
5561 <advisory url="/news/secadv/20120104.txt"/>
5562 <reported source="Nadhem Alfardan and Kenny Paterson"/>
5564 OpenSSL was susceptable an extension of the
5565 Vaudenay padding oracle attack on CBC mode encryption which enables an
5566 efficient plaintext recovery attack against the OpenSSL implementation
5567 of DTLS by exploiting timing differences arising during
5568 decryption processing.
5572 <issue public="20120104">
5573 <cve name="2011-4109"/>
5574 <affects base="0.9.8" version="0.9.8"/>
5575 <affects base="0.9.8" version="0.9.8a"/>
5576 <affects base="0.9.8" version="0.9.8b"/>
5577 <affects base="0.9.8" version="0.9.8c"/>
5578 <affects base="0.9.8" version="0.9.8d"/>
5579 <affects base="0.9.8" version="0.9.8e"/>
5580 <affects base="0.9.8" version="0.9.8f"/>
5581 <affects base="0.9.8" version="0.9.8g"/>
5582 <affects base="0.9.8" version="0.9.8h"/>
5583 <affects base="0.9.8" version="0.9.8i"/>
5584 <affects base="0.9.8" version="0.9.8j"/>
5585 <affects base="0.9.8" version="0.9.8k"/>
5586 <affects base="0.9.8" version="0.9.8l"/>
5587 <affects base="0.9.8" version="0.9.8m"/>
5588 <affects base="0.9.8" version="0.9.8n"/>
5589 <affects base="0.9.8" version="0.9.8o"/>
5590 <affects base="0.9.8" version="0.9.8p"/>
5591 <affects base="0.9.8" version="0.9.8q"/>
5592 <affects base="0.9.8" version="0.9.8r"/>
5593 <fixed base="0.9.8" version="0.9.8s" date="20120104"/>
5594 <advisory url="/news/secadv/20120104.txt"/>
5595 <reported source="Ben Laurie"/>
5597 If X509_V_FLAG_POLICY_CHECK is set in OpenSSL 0.9.8, then a policy
5598 check failure can lead to a double-free. The bug does not occur
5599 unless this flag is set. Users of OpenSSL 1.0.0 are not affected
5603 <issue public="20120104">
5604 <cve name="2011-4576"/>
5605 <affects base="0.9.8" version="0.9.8"/>
5606 <affects base="0.9.8" version="0.9.8a"/>
5607 <affects base="0.9.8" version="0.9.8b"/>
5608 <affects base="0.9.8" version="0.9.8c"/>
5609 <affects base="0.9.8" version="0.9.8d"/>
5610 <affects base="0.9.8" version="0.9.8e"/>
5611 <affects base="0.9.8" version="0.9.8f"/>
5612 <affects base="0.9.8" version="0.9.8g"/>
5613 <affects base="0.9.8" version="0.9.8h"/>
5614 <affects base="0.9.8" version="0.9.8i"/>
5615 <affects base="0.9.8" version="0.9.8j"/>
5616 <affects base="0.9.8" version="0.9.8k"/>
5617 <affects base="0.9.8" version="0.9.8l"/>
5618 <affects base="0.9.8" version="0.9.8m"/>
5619 <affects base="0.9.8" version="0.9.8n"/>
5620 <affects base="0.9.8" version="0.9.8o"/>
5621 <affects base="0.9.8" version="0.9.8p"/>
5622 <affects base="0.9.8" version="0.9.8q"/>
5623 <affects base="0.9.8" version="0.9.8r"/>
5624 <affects base="1.0.0" version="1.0.0"/>
5625 <affects base="1.0.0" version="1.0.0a"/>
5626 <affects base="1.0.0" version="1.0.0b"/>
5627 <affects base="1.0.0" version="1.0.0c"/>
5628 <affects base="1.0.0" version="1.0.0d"/>
5629 <affects base="1.0.0" version="1.0.0e"/>
5630 <fixed base="1.0.0" version="1.0.0f" date="20120104"/>
5631 <fixed base="0.9.8" version="0.9.8s" date="20120104"/>
5632 <advisory url="/news/secadv/20120104.txt"/>
5633 <reported source="Adam Langley"/>
5635 OpenSSL failed to clear the bytes used as
5636 block cipher padding in SSL 3.0 records which could leak
5637 the contents of memory in some circumstances.
5641 <issue public="20120104">
5642 <cve name="2011-4577"/>
5643 <affects base="0.9.8" version="0.9.8"/>
5644 <affects base="0.9.8" version="0.9.8a"/>
5645 <affects base="0.9.8" version="0.9.8b"/>
5646 <affects base="0.9.8" version="0.9.8c"/>
5647 <affects base="0.9.8" version="0.9.8d"/>
5648 <affects base="0.9.8" version="0.9.8e"/>
5649 <affects base="0.9.8" version="0.9.8f"/>
5650 <affects base="0.9.8" version="0.9.8g"/>
5651 <affects base="0.9.8" version="0.9.8h"/>
5652 <affects base="0.9.8" version="0.9.8i"/>
5653 <affects base="0.9.8" version="0.9.8j"/>
5654 <affects base="0.9.8" version="0.9.8k"/>
5655 <affects base="0.9.8" version="0.9.8l"/>
5656 <affects base="0.9.8" version="0.9.8m"/>
5657 <affects base="0.9.8" version="0.9.8n"/>
5658 <affects base="0.9.8" version="0.9.8o"/>
5659 <affects base="0.9.8" version="0.9.8p"/>
5660 <affects base="0.9.8" version="0.9.8q"/>
5661 <affects base="0.9.8" version="0.9.8r"/>
5662 <affects base="1.0.0" version="1.0.0"/>
5663 <affects base="1.0.0" version="1.0.0a"/>
5664 <affects base="1.0.0" version="1.0.0b"/>
5665 <affects base="1.0.0" version="1.0.0c"/>
5666 <affects base="1.0.0" version="1.0.0d"/>
5667 <affects base="1.0.0" version="1.0.0e"/>
5668 <fixed base="1.0.0" version="1.0.0f" date="20120104"/>
5669 <fixed base="0.9.8" version="0.9.8s" date="20120104"/>
5670 <advisory url="/news/secadv/20120104.txt"/>
5671 <reported source="Andrew Chi"/>
5673 RFC 3779 data can be included in certificates, and if it is malformed,
5674 may trigger an assertion failure. This could be used in a
5675 denial-of-service attack. Builds of OpenSSL are only vulnerable if configured with
5676 "enable-rfc3779", which is not a default.
5680 <issue public="20120104">
5681 <cve name="2011-4619"/>
5682 <affects base="0.9.8" version="0.9.8"/>
5683 <affects base="0.9.8" version="0.9.8a"/>
5684 <affects base="0.9.8" version="0.9.8b"/>
5685 <affects base="0.9.8" version="0.9.8c"/>
5686 <affects base="0.9.8" version="0.9.8d"/>
5687 <affects base="0.9.8" version="0.9.8e"/>
5688 <affects base="0.9.8" version="0.9.8f"/>
5689 <affects base="0.9.8" version="0.9.8g"/>
5690 <affects base="0.9.8" version="0.9.8h"/>
5691 <affects base="0.9.8" version="0.9.8i"/>
5692 <affects base="0.9.8" version="0.9.8j"/>
5693 <affects base="0.9.8" version="0.9.8k"/>
5694 <affects base="0.9.8" version="0.9.8l"/>
5695 <affects base="0.9.8" version="0.9.8m"/>
5696 <affects base="0.9.8" version="0.9.8n"/>
5697 <affects base="0.9.8" version="0.9.8o"/>
5698 <affects base="0.9.8" version="0.9.8p"/>
5699 <affects base="0.9.8" version="0.9.8q"/>
5700 <affects base="0.9.8" version="0.9.8r"/>
5701 <affects base="1.0.0" version="1.0.0"/>
5702 <affects base="1.0.0" version="1.0.0a"/>
5703 <affects base="1.0.0" version="1.0.0b"/>
5704 <affects base="1.0.0" version="1.0.0c"/>
5705 <affects base="1.0.0" version="1.0.0d"/>
5706 <affects base="1.0.0" version="1.0.0e"/>
5707 <fixed base="1.0.0" version="1.0.0f" date="20120104"/>
5708 <fixed base="0.9.8" version="0.9.8s" date="20120104"/>
5709 <advisory url="/news/secadv/20120104.txt"/>
5710 <reported source="George Kadianakis"/>
5712 Support for handshake restarts for server gated cryptograpy (SGC) can
5713 be used in a denial-of-service attack.
5717 <issue public="20120104">
5718 <cve name="2012-0027"/>
5719 <affects base="1.0.0" version="1.0.0"/>
5720 <affects base="1.0.0" version="1.0.0a"/>
5721 <affects base="1.0.0" version="1.0.0b"/>
5722 <affects base="1.0.0" version="1.0.0c"/>
5723 <affects base="1.0.0" version="1.0.0d"/>
5724 <affects base="1.0.0" version="1.0.0e"/>
5725 <fixed base="1.0.0" version="1.0.0f" date="20120104"/>
5726 <advisory url="/news/secadv/20120104.txt"/>
5727 <reported source="Andrey Kulikov"/>
5729 A malicious TLS client can send an invalid set of GOST parameters
5730 which will cause the server to crash due to lack of error checking.
5731 This could be used in a denial-of-service attack.
5732 Only users of the OpenSSL GOST ENGINE are affected by this bug.
5736 <issue public="20120104">
5737 <cve name="2012-0050"/>
5738 <affects base="0.9.8" version="0.9.8s"/>
5739 <affects base="1.0.0" version="1.0.0f"/>
5740 <fixed base="1.0.0" version="1.0.0g" date="20120118"/>
5741 <fixed base="0.9.8" version="0.9.8t" date="20120118"/>
5742 <advisory url="/news/secadv/20120118.txt"/>
5743 <reported source="Antonio Martin"/>
5745 A flaw in the fix to CVE-2011-4108 can be exploited in a denial of
5746 service attack. Only DTLS applications are affected.
5750 <issue public="20120312">
5751 <cve name="2012-0884"/>
5752 <affects base="0.9.8" version="0.9.8"/>
5753 <affects base="0.9.8" version="0.9.8a"/>
5754 <affects base="0.9.8" version="0.9.8b"/>
5755 <affects base="0.9.8" version="0.9.8c"/>
5756 <affects base="0.9.8" version="0.9.8d"/>
5757 <affects base="0.9.8" version="0.9.8e"/>
5758 <affects base="0.9.8" version="0.9.8f"/>
5759 <affects base="0.9.8" version="0.9.8g"/>
5760 <affects base="0.9.8" version="0.9.8h"/>
5761 <affects base="0.9.8" version="0.9.8i"/>
5762 <affects base="0.9.8" version="0.9.8j"/>
5763 <affects base="0.9.8" version="0.9.8k"/>
5764 <affects base="0.9.8" version="0.9.8l"/>
5765 <affects base="0.9.8" version="0.9.8m"/>
5766 <affects base="0.9.8" version="0.9.8n"/>
5767 <affects base="0.9.8" version="0.9.8o"/>
5768 <affects base="0.9.8" version="0.9.8p"/>
5769 <affects base="0.9.8" version="0.9.8q"/>
5770 <affects base="0.9.8" version="0.9.8r"/>
5771 <affects base="0.9.8" version="0.9.8s"/>
5772 <affects base="0.9.8" version="0.9.8t"/>
5773 <affects base="1.0.0" version="1.0.0"/>
5774 <affects base="1.0.0" version="1.0.0a"/>
5775 <affects base="1.0.0" version="1.0.0b"/>
5776 <affects base="1.0.0" version="1.0.0c"/>
5777 <affects base="1.0.0" version="1.0.0d"/>
5778 <affects base="1.0.0" version="1.0.0e"/>
5779 <affects base="1.0.0" version="1.0.0f"/>
5780 <affects base="1.0.0" version="1.0.0g"/>
5781 <fixed base="1.0.0" version="1.0.0h" date="20120312"/>
5782 <fixed base="0.9.8" version="0.9.8u" date="20120312"/>
5783 <advisory url="/news/secadv/20120312.txt"/>
5784 <reported source="Ivan Nestlerode"/>
5786 A weakness in the OpenSSL CMS and PKCS #7 code can be exploited
5787 using Bleichenbacher's attack on PKCS #1 v1.5 RSA padding
5788 also known as the million message attack (MMA).
5789 Only users of CMS, PKCS #7, or S/MIME decryption operations are affected,
5790 SSL/TLS applications are not affected by this issue.
5795 <issue public="20110208">
5796 <cve name="2011-0014"/>
5797 <affects base="0.9.8" version="0.9.8h"/>
5798 <affects base="0.9.8" version="0.9.8i"/>
5799 <affects base="0.9.8" version="0.9.8j"/>
5800 <affects base="0.9.8" version="0.9.8k"/>
5801 <affects base="0.9.8" version="0.9.8l"/>
5802 <affects base="0.9.8" version="0.9.8m"/>
5803 <affects base="0.9.8" version="0.9.8n"/>
5804 <affects base="0.9.8" version="0.9.8o"/>
5805 <affects base="0.9.8" version="0.9.8p"/>
5806 <affects base="0.9.8" version="0.9.8q"/>
5807 <affects base="1.0.0" version="1.0.0"/>
5808 <affects base="1.0.0" version="1.0.0a"/>
5809 <affects base="1.0.0" version="1.0.0b"/>
5810 <affects base="1.0.0" version="1.0.0c"/>
5811 <fixed base="1.0.0" version="1.0.0d" date="20110208"/>
5812 <fixed base="0.9.8" version="0.9.8r" date="20110208"/>
5813 <advisory url="/news/secadv/20110208.txt"/>
5814 <reported source="Neel Mehta"/>
5816 A buffer over-read flaw was discovered in the way OpenSSL parsed the
5817 Certificate Status Request TLS extensions in ClientHello TLS handshake
5818 messages. A remote attacker could possibly use this flaw to crash an SSL
5819 server using the affected OpenSSL functionality.
5823 <issue public="20120424">
5824 <cve name="2012-2131"/>
5825 <affects base="0.9.8" version="0.9.8v"/>
5826 <fixed base="0.9.8" version="0.9.8w" date="20120424"/>
5827 <advisory url="/news/secadv/20120424.txt"/>
5828 <reported source="Red Hat"/>
5830 It was discovered that the fix for CVE-2012-2110 released on 19 Apr
5831 2012 was not sufficient to correct the issue for OpenSSL 0.9.8. This
5832 issue only affects OpenSSL 0.9.8v. OpenSSL 1.0.1a and 1.0.0i already
5833 contain a patch sufficient to correct CVE-2012-2110.
5838 <issue public="20120419">
5839 <cve name="2012-2110"/>
5840 <affects base="0.9.8" version="0.9.8"/>
5841 <affects base="0.9.8" version="0.9.8a"/>
5842 <affects base="0.9.8" version="0.9.8b"/>
5843 <affects base="0.9.8" version="0.9.8c"/>
5844 <affects base="0.9.8" version="0.9.8d"/>
5845 <affects base="0.9.8" version="0.9.8e"/>
5846 <affects base="0.9.8" version="0.9.8f"/>
5847 <affects base="0.9.8" version="0.9.8g"/>
5848 <affects base="0.9.8" version="0.9.8h"/>
5849 <affects base="0.9.8" version="0.9.8i"/>
5850 <affects base="0.9.8" version="0.9.8j"/>
5851 <affects base="0.9.8" version="0.9.8k"/>
5852 <affects base="0.9.8" version="0.9.8l"/>
5853 <affects base="0.9.8" version="0.9.8m"/>
5854 <affects base="0.9.8" version="0.9.8n"/>
5855 <affects base="0.9.8" version="0.9.8o"/>
5856 <affects base="0.9.8" version="0.9.8p"/>
5857 <affects base="0.9.8" version="0.9.8q"/>
5858 <affects base="0.9.8" version="0.9.8r"/>
5859 <affects base="0.9.8" version="0.9.8s"/>
5860 <affects base="0.9.8" version="0.9.8t"/>
5861 <affects base="0.9.8" version="0.9.8u"/>
5862 <affects base="1.0.0" version="1.0.0"/>
5863 <affects base="1.0.0" version="1.0.0a"/>
5864 <affects base="1.0.0" version="1.0.0b"/>
5865 <affects base="1.0.0" version="1.0.0c"/>
5866 <affects base="1.0.0" version="1.0.0d"/>
5867 <affects base="1.0.0" version="1.0.0e"/>
5868 <affects base="1.0.0" version="1.0.0f"/>
5869 <affects base="1.0.0" version="1.0.0g"/>
5870 <affects base="1.0.1" version="1.0.1"/>
5871 <fixed base="1.0.1" version="1.0.1a" date="20120419"/>
5872 <fixed base="1.0.0" version="1.0.0i" date="20120419"/>
5873 <fixed base="0.9.8" version="0.9.8v" date="20120419"/>
5874 <advisory url="/news/secadv/20120419.txt"/>
5875 <reported source="Tavis Ormandy"/>
5877 Multiple numeric conversion errors, leading to a buffer overflow, were
5878 found in the way OpenSSL parsed ASN.1 (Abstract Syntax Notation One) data
5879 from BIO (OpenSSL's I/O abstraction) inputs. Specially-crafted DER
5880 (Distinguished Encoding Rules) encoded data read from a file or other BIO
5881 input could cause an application using the OpenSSL library to crash or,
5882 potentially, execute arbitrary code.
5886 <issue public="20120510">
5887 <cve name="2012-2333"/>
5888 <affects base="0.9.8" version="0.9.8"/>
5889 <affects base="0.9.8" version="0.9.8a"/>
5890 <affects base="0.9.8" version="0.9.8b"/>
5891 <affects base="0.9.8" version="0.9.8c"/>
5892 <affects base="0.9.8" version="0.9.8d"/>
5893 <affects base="0.9.8" version="0.9.8e"/>
5894 <affects base="0.9.8" version="0.9.8f"/>
5895 <affects base="0.9.8" version="0.9.8g"/>
5896 <affects base="0.9.8" version="0.9.8h"/>
5897 <affects base="0.9.8" version="0.9.8i"/>
5898 <affects base="0.9.8" version="0.9.8j"/>
5899 <affects base="0.9.8" version="0.9.8k"/>
5900 <affects base="0.9.8" version="0.9.8l"/>
5901 <affects base="0.9.8" version="0.9.8m"/>
5902 <affects base="0.9.8" version="0.9.8n"/>
5903 <affects base="0.9.8" version="0.9.8o"/>
5904 <affects base="0.9.8" version="0.9.8p"/>
5905 <affects base="0.9.8" version="0.9.8q"/>
5906 <affects base="0.9.8" version="0.9.8r"/>
5907 <affects base="0.9.8" version="0.9.8s"/>
5908 <affects base="0.9.8" version="0.9.8t"/>
5909 <affects base="0.9.8" version="0.9.8u"/>
5910 <affects base="0.9.8" version="0.9.8v"/>
5911 <affects base="0.9.8" version="0.9.8w"/>
5912 <affects base="1.0.0" version="1.0.0"/>
5913 <affects base="1.0.0" version="1.0.0a"/>
5914 <affects base="1.0.0" version="1.0.0b"/>
5915 <affects base="1.0.0" version="1.0.0c"/>
5916 <affects base="1.0.0" version="1.0.0d"/>
5917 <affects base="1.0.0" version="1.0.0e"/>
5918 <affects base="1.0.0" version="1.0.0f"/>
5919 <affects base="1.0.0" version="1.0.0g"/>
5920 <affects base="1.0.0" version="1.0.0i"/>
5921 <affects base="1.0.1" version="1.0.1"/>
5922 <affects base="1.0.1" version="1.0.1a"/>
5923 <affects base="1.0.1" version="1.0.1b"/>
5924 <fixed base="1.0.1" version="1.0.1c" date="20120510"/>
5925 <fixed base="1.0.0" version="1.0.0j" date="20120510"/>
5926 <fixed base="0.9.8" version="0.9.8x" date="20120510"/>
5927 <advisory url="/news/secadv/20120510.txt"/>
5928 <reported source="Codenomicon"/>
5930 An integer underflow flaw, leading to a buffer over-read, was found in
5931 the way OpenSSL handled TLS 1.1, TLS 1.2, and DTLS (Datagram Transport
5932 Layer Security) application data record lengths when using a block
5933 cipher in CBC (cipher-block chaining) mode. A malicious TLS 1.1, TLS
5934 1.2, or DTLS client or server could use this flaw to crash its connection
5939 <issue public="20130204">
5940 <cve name="2013-0169"/>
5941 <affects base="0.9.8" version="0.9.8"/>
5942 <affects base="0.9.8" version="0.9.8a"/>
5943 <affects base="0.9.8" version="0.9.8b"/>
5944 <affects base="0.9.8" version="0.9.8c"/>
5945 <affects base="0.9.8" version="0.9.8d"/>
5946 <affects base="0.9.8" version="0.9.8e"/>
5947 <affects base="0.9.8" version="0.9.8f"/>
5948 <affects base="0.9.8" version="0.9.8g"/>
5949 <affects base="0.9.8" version="0.9.8h"/>
5950 <affects base="0.9.8" version="0.9.8i"/>
5951 <affects base="0.9.8" version="0.9.8j"/>
5952 <affects base="0.9.8" version="0.9.8k"/>
5953 <affects base="0.9.8" version="0.9.8l"/>
5954 <affects base="0.9.8" version="0.9.8m"/>
5955 <affects base="0.9.8" version="0.9.8n"/>
5956 <affects base="0.9.8" version="0.9.8o"/>
5957 <affects base="0.9.8" version="0.9.8p"/>
5958 <affects base="0.9.8" version="0.9.8q"/>
5959 <affects base="0.9.8" version="0.9.8r"/>
5960 <affects base="0.9.8" version="0.9.8s"/>
5961 <affects base="0.9.8" version="0.9.8t"/>
5962 <affects base="0.9.8" version="0.9.8u"/>
5963 <affects base="0.9.8" version="0.9.8v"/>
5964 <affects base="0.9.8" version="0.9.8w"/>
5965 <affects base="0.9.8" version="0.9.8x"/>
5966 <affects base="1.0.0" version="1.0.0"/>
5967 <affects base="1.0.0" version="1.0.0a"/>
5968 <affects base="1.0.0" version="1.0.0b"/>
5969 <affects base="1.0.0" version="1.0.0c"/>
5970 <affects base="1.0.0" version="1.0.0d"/>
5971 <affects base="1.0.0" version="1.0.0e"/>
5972 <affects base="1.0.0" version="1.0.0f"/>
5973 <affects base="1.0.0" version="1.0.0g"/>
5974 <affects base="1.0.0" version="1.0.0i"/>
5975 <affects base="1.0.0" version="1.0.0j"/>
5976 <affects base="1.0.1" version="1.0.1"/>
5977 <affects base="1.0.1" version="1.0.1a"/>
5978 <affects base="1.0.1" version="1.0.1b"/>
5979 <affects base="1.0.1" version="1.0.1c"/>
5980 <fixed base="1.0.1" version="1.0.1d" date="20130205"/>
5981 <fixed base="1.0.0" version="1.0.0k" date="20130205"/>
5982 <fixed base="0.9.8" version="0.9.8y" date="20130205"/>
5983 <advisory url="/news/secadv/20130205.txt"/>
5984 <reported source="Nadhem J. AlFardan and Kenneth G. Paterson of the Information Security Group Royal Holloway, University of London"/>
5986 A weakness in the handling of CBC ciphersuites in SSL, TLS and DTLS which could
5987 lead to plaintext recovery by exploiting timing differences
5988 arising during MAC processing.
5992 <issue public="20130205">
5993 <cve name="2012-2686"/>
5994 <affects base="1.0.1" version="1.0.1"/>
5995 <affects base="1.0.1" version="1.0.1a"/>
5996 <affects base="1.0.1" version="1.0.1b"/>
5997 <affects base="1.0.1" version="1.0.1c"/>
5998 <fixed base="1.0.1" version="1.0.1d" date="20130205"/>
5999 <advisory url="/news/secadv/20130205.txt"/>
6000 <reported source="Adam Langley and Wolfgang Ettlinger"/>
6002 A flaw in the OpenSSL handling of CBC ciphersuites in TLS 1.1 and TLS 1.2 on
6003 AES-NI supporting platforms can be exploited in a DoS attack.
6007 <issue public="20130205">
6008 <cve name="2013-0166"/>
6009 <affects base="0.9.8" version="0.9.8"/>
6010 <affects base="0.9.8" version="0.9.8a"/>
6011 <affects base="0.9.8" version="0.9.8b"/>
6012 <affects base="0.9.8" version="0.9.8c"/>
6013 <affects base="0.9.8" version="0.9.8d"/>
6014 <affects base="0.9.8" version="0.9.8e"/>
6015 <affects base="0.9.8" version="0.9.8f"/>
6016 <affects base="0.9.8" version="0.9.8g"/>
6017 <affects base="0.9.8" version="0.9.8h"/>
6018 <affects base="0.9.8" version="0.9.8i"/>
6019 <affects base="0.9.8" version="0.9.8j"/>
6020 <affects base="0.9.8" version="0.9.8k"/>
6021 <affects base="0.9.8" version="0.9.8l"/>
6022 <affects base="0.9.8" version="0.9.8m"/>
6023 <affects base="0.9.8" version="0.9.8n"/>
6024 <affects base="0.9.8" version="0.9.8o"/>
6025 <affects base="0.9.8" version="0.9.8p"/>
6026 <affects base="0.9.8" version="0.9.8q"/>
6027 <affects base="0.9.8" version="0.9.8r"/>
6028 <affects base="0.9.8" version="0.9.8s"/>
6029 <affects base="0.9.8" version="0.9.8t"/>
6030 <affects base="0.9.8" version="0.9.8u"/>
6031 <affects base="0.9.8" version="0.9.8v"/>
6032 <affects base="0.9.8" version="0.9.8w"/>
6033 <affects base="0.9.8" version="0.9.8x"/>
6034 <affects base="1.0.0" version="1.0.0"/>
6035 <affects base="1.0.0" version="1.0.0a"/>
6036 <affects base="1.0.0" version="1.0.0b"/>
6037 <affects base="1.0.0" version="1.0.0c"/>
6038 <affects base="1.0.0" version="1.0.0d"/>
6039 <affects base="1.0.0" version="1.0.0e"/>
6040 <affects base="1.0.0" version="1.0.0f"/>
6041 <affects base="1.0.0" version="1.0.0g"/>
6042 <affects base="1.0.0" version="1.0.0i"/>
6043 <affects base="1.0.0" version="1.0.0j"/>
6044 <affects base="1.0.1" version="1.0.1"/>
6045 <affects base="1.0.1" version="1.0.1a"/>
6046 <affects base="1.0.1" version="1.0.1b"/>
6047 <affects base="1.0.1" version="1.0.1c"/>
6048 <fixed base="1.0.1" version="1.0.1d" date="20130205"/>
6049 <fixed base="1.0.0" version="1.0.0k" date="20130205"/>
6050 <fixed base="0.9.8" version="0.9.8y" date="20130205"/>
6051 <advisory url="/news/secadv/20130205.txt"/>
6052 <reported source="Stephen Henson"/>
6054 A flaw in the OpenSSL handling of OCSP response verification can be exploited in
6055 a denial of service attack.
6059 <issue public="20131213">
6060 <cve name="2013-6450"/>
6061 <affects base="1.0.0" version="1.0.0"/>
6062 <affects base="1.0.0" version="1.0.0a"/>
6063 <affects base="1.0.0" version="1.0.0b"/>
6064 <affects base="1.0.0" version="1.0.0c"/>
6065 <affects base="1.0.0" version="1.0.0d"/>
6066 <affects base="1.0.0" version="1.0.0e"/>
6067 <affects base="1.0.0" version="1.0.0f"/>
6068 <affects base="1.0.0" version="1.0.0g"/>
6069 <affects base="1.0.0" version="1.0.0i"/>
6070 <affects base="1.0.0" version="1.0.0j"/>
6071 <affects base="1.0.0" version="1.0.0k"/>
6072 <affects base="1.0.1" version="1.0.1"/>
6073 <affects base="1.0.1" version="1.0.1a"/>
6074 <affects base="1.0.1" version="1.0.1b"/>
6075 <affects base="1.0.1" version="1.0.1c"/>
6076 <affects base="1.0.1" version="1.0.1d"/>
6077 <affects base="1.0.1" version="1.0.1e"/>
6078 <fixed base="1.0.1" version="1.0.1f" date="20140106">
6079 <git hash="3462896"/>
6081 <fixed base="1.0.0" version="1.0.0l" date="20140106"/>
6082 <reported source="Dmitry Sobinov"/>
6084 A flaw in DTLS handling can cause an application using OpenSSL and DTLS to crash.
6085 This is not a vulnerability for OpenSSL prior to 1.0.0.
6089 <issue public="20131214">
6090 <cve name="2013-6449"/>
6091 <affects base="1.0.1" version="1.0.1"/>
6092 <affects base="1.0.1" version="1.0.1a"/>
6093 <affects base="1.0.1" version="1.0.1b"/>
6094 <affects base="1.0.1" version="1.0.1c"/>
6095 <affects base="1.0.1" version="1.0.1d"/>
6096 <affects base="1.0.1" version="1.0.1e"/>
6097 <fixed base="1.0.1" version="1.0.1f" date="20140106">
6098 <git hash="ca98926"/>
6100 <reported source="Ron Barber"/>
6102 A flaw in OpenSSL can cause an application using OpenSSL to crash when using TLS version 1.2.
6103 This issue only affected OpenSSL 1.0.1 versions.
6107 <issue public="20140106">
6108 <cve name="2013-4353"/>
6109 <affects base="1.0.1" version="1.0.1"/>
6110 <affects base="1.0.1" version="1.0.1a"/>
6111 <affects base="1.0.1" version="1.0.1b"/>
6112 <affects base="1.0.1" version="1.0.1c"/>
6113 <affects base="1.0.1" version="1.0.1d"/>
6114 <affects base="1.0.1" version="1.0.1e"/>
6115 <fixed base="1.0.1" version="1.0.1f" date="20140106">
6116 <git hash="197e0ea817ad64820789d86711d55ff50d71f631"/>
6118 <reported source="Anton Johansson"/>
6120 A carefully crafted invalid TLS handshake could crash OpenSSL with a NULL pointer exception. A malicious
6121 server could use this flaw to crash a connecting client. This issue only affected OpenSSL 1.0.1 versions.
6125 <issue public="20140214">
6126 <cve name="2014-0076"/>
6127 <advisory url="/news/secadv/20140605.txt"/>
6128 <affects base="0.9.8" version="0.9.8"/>
6129 <affects base="0.9.8" version="0.9.8a"/>
6130 <affects base="0.9.8" version="0.9.8b"/>
6131 <affects base="0.9.8" version="0.9.8c"/>
6132 <affects base="0.9.8" version="0.9.8d"/>
6133 <affects base="0.9.8" version="0.9.8e"/>
6134 <affects base="0.9.8" version="0.9.8f"/>
6135 <affects base="0.9.8" version="0.9.8g"/>
6136 <affects base="0.9.8" version="0.9.8h"/>
6137 <affects base="0.9.8" version="0.9.8i"/>
6138 <affects base="0.9.8" version="0.9.8j"/>
6139 <affects base="0.9.8" version="0.9.8k"/>
6140 <affects base="0.9.8" version="0.9.8l"/>
6141 <affects base="0.9.8" version="0.9.8m"/>
6142 <affects base="0.9.8" version="0.9.8n"/>
6143 <affects base="0.9.8" version="0.9.8o"/>
6144 <affects base="0.9.8" version="0.9.8p"/>
6145 <affects base="0.9.8" version="0.9.8q"/>
6146 <affects base="0.9.8" version="0.9.8r"/>
6147 <affects base="0.9.8" version="0.9.8s"/>
6148 <affects base="0.9.8" version="0.9.8t"/>
6149 <affects base="0.9.8" version="0.9.8u"/>
6150 <affects base="0.9.8" version="0.9.8v"/>
6151 <affects base="0.9.8" version="0.9.8w"/>
6152 <affects base="0.9.8" version="0.9.8x"/>
6153 <affects base="0.9.8" version="0.9.8y"/>
6154 <affects base="1.0.0" version="1.0.0"/>
6155 <affects base="1.0.0" version="1.0.0a"/>
6156 <affects base="1.0.0" version="1.0.0b"/>
6157 <affects base="1.0.0" version="1.0.0c"/>
6158 <affects base="1.0.0" version="1.0.0d"/>
6159 <affects base="1.0.0" version="1.0.0e"/>
6160 <affects base="1.0.0" version="1.0.0f"/>
6161 <affects base="1.0.0" version="1.0.0g"/>
6162 <affects base="1.0.0" version="1.0.0i"/>
6163 <affects base="1.0.0" version="1.0.0j"/>
6164 <affects base="1.0.0" version="1.0.0k"/>
6165 <affects base="1.0.0" version="1.0.0l"/>
6166 <affects base="1.0.1" version="1.0.1"/>
6167 <affects base="1.0.1" version="1.0.1a"/>
6168 <affects base="1.0.1" version="1.0.1b"/>
6169 <affects base="1.0.1" version="1.0.1c"/>
6170 <affects base="1.0.1" version="1.0.1d"/>
6171 <affects base="1.0.1" version="1.0.1e"/>
6172 <affects base="1.0.1" version="1.0.1f"/>
6173 <fixed base="1.0.1" version="1.0.1g" date="20140409">
6174 <git hash="4b7a4ba29cafa432fc4266fe6e59e60bc1c96332"/>
6176 <fixed base="1.0.0" version="1.0.0m" date="20140312">
6177 <git hash="2198be3483259de374f91e57d247d0fc667aef29"/>
6179 <fixed base="0.9.8" version="0.9.8za" date="20140605">
6181 <reported source="Yuval Yarom and Naomi Benger"/>
6183 Fix for the attack described in the paper "Recovering OpenSSL
6184 ECDSA Nonces Using the FLUSH+RELOAD Cache Side-channel Attack"
6188 <issue public="20140407">
6189 <cve name="2014-0160"/>
6190 <affects base="1.0.1" version="1.0.1"/>
6191 <affects base="1.0.1" version="1.0.1a"/>
6192 <affects base="1.0.1" version="1.0.1b"/>
6193 <affects base="1.0.1" version="1.0.1c"/>
6194 <affects base="1.0.1" version="1.0.1d"/>
6195 <affects base="1.0.1" version="1.0.1e"/>
6196 <affects base="1.0.1" version="1.0.1f"/>
6197 <fixed base="1.0.1" version="1.0.1g" date="20140409">
6199 <advisory url="/news/secadv/20140407.txt"/>
6200 <reported source="Neel Mehta"/>
6202 A missing bounds check in the handling of the TLS heartbeat extension can be
6203 used to reveal up to 64kB of memory to a connected client or server (a.k.a. Heartbleed). This
6204 issue did not affect versions of OpenSSL prior to 1.0.1.
6208 <issue public="20140605">
6209 <cve name="2014-0224"/>
6210 <affects base="0.9.8" version="0.9.8"/>
6211 <affects base="0.9.8" version="0.9.8a"/>
6212 <affects base="0.9.8" version="0.9.8b"/>
6213 <affects base="0.9.8" version="0.9.8c"/>
6214 <affects base="0.9.8" version="0.9.8d"/>
6215 <affects base="0.9.8" version="0.9.8e"/>
6216 <affects base="0.9.8" version="0.9.8f"/>
6217 <affects base="0.9.8" version="0.9.8g"/>
6218 <affects base="0.9.8" version="0.9.8h"/>
6219 <affects base="0.9.8" version="0.9.8i"/>
6220 <affects base="0.9.8" version="0.9.8j"/>
6221 <affects base="0.9.8" version="0.9.8k"/>
6222 <affects base="0.9.8" version="0.9.8l"/>
6223 <affects base="0.9.8" version="0.9.8m"/>
6224 <affects base="0.9.8" version="0.9.8n"/>
6225 <affects base="0.9.8" version="0.9.8o"/>
6226 <affects base="0.9.8" version="0.9.8p"/>
6227 <affects base="0.9.8" version="0.9.8q"/>
6228 <affects base="0.9.8" version="0.9.8r"/>
6229 <affects base="0.9.8" version="0.9.8s"/>
6230 <affects base="0.9.8" version="0.9.8t"/>
6231 <affects base="0.9.8" version="0.9.8u"/>
6232 <affects base="0.9.8" version="0.9.8v"/>
6233 <affects base="0.9.8" version="0.9.8w"/>
6234 <affects base="0.9.8" version="0.9.8x"/>
6235 <affects base="0.9.8" version="0.9.8y"/>
6236 <affects base="1.0.0" version="1.0.0"/>
6237 <affects base="1.0.0" version="1.0.0a"/>
6238 <affects base="1.0.0" version="1.0.0b"/>
6239 <affects base="1.0.0" version="1.0.0c"/>
6240 <affects base="1.0.0" version="1.0.0d"/>
6241 <affects base="1.0.0" version="1.0.0e"/>
6242 <affects base="1.0.0" version="1.0.0f"/>
6243 <affects base="1.0.0" version="1.0.0g"/>
6244 <affects base="1.0.0" version="1.0.0i"/>
6245 <affects base="1.0.0" version="1.0.0j"/>
6246 <affects base="1.0.0" version="1.0.0k"/>
6247 <affects base="1.0.0" version="1.0.0l"/>
6248 <affects base="1.0.1" version="1.0.1"/>
6249 <affects base="1.0.1" version="1.0.1a"/>
6250 <affects base="1.0.1" version="1.0.1b"/>
6251 <affects base="1.0.1" version="1.0.1c"/>
6252 <affects base="1.0.1" version="1.0.1d"/>
6253 <affects base="1.0.1" version="1.0.1e"/>
6254 <affects base="1.0.1" version="1.0.1f"/>
6255 <affects base="1.0.1" version="1.0.1g"/>
6256 <fixed base="1.0.1" version="1.0.1h" date="20140605">
6258 <fixed base="1.0.0" version="1.0.0m" date="20140605">
6260 <fixed base="0.9.8" version="0.9.8za" date="20140605">
6263 An attacker can force the use of weak
6264 keying material in OpenSSL SSL/TLS clients and servers. This can be exploited
6265 by a Man-in-the-middle (MITM) attack where the attacker can decrypt and
6266 modify traffic from the attacked client and server.
6268 <advisory url="/news/secadv/20140605.txt"/>
6269 <reported source="KIKUCHI Masashi (Lepidum Co. Ltd.)"/>
6272 <issue public="20140605">
6273 <cve name="2014-0221"/>
6274 <affects base="0.9.8" version="0.9.8"/>
6275 <affects base="0.9.8" version="0.9.8a"/>
6276 <affects base="0.9.8" version="0.9.8b"/>
6277 <affects base="0.9.8" version="0.9.8c"/>
6278 <affects base="0.9.8" version="0.9.8d"/>
6279 <affects base="0.9.8" version="0.9.8e"/>
6280 <affects base="0.9.8" version="0.9.8f"/>
6281 <affects base="0.9.8" version="0.9.8g"/>
6282 <affects base="0.9.8" version="0.9.8h"/>
6283 <affects base="0.9.8" version="0.9.8i"/>
6284 <affects base="0.9.8" version="0.9.8j"/>
6285 <affects base="0.9.8" version="0.9.8k"/>
6286 <affects base="0.9.8" version="0.9.8l"/>
6287 <affects base="0.9.8" version="0.9.8m"/>
6288 <affects base="0.9.8" version="0.9.8n"/>
6289 <affects base="0.9.8" version="0.9.8o"/>
6290 <affects base="0.9.8" version="0.9.8p"/>
6291 <affects base="0.9.8" version="0.9.8q"/>
6292 <affects base="0.9.8" version="0.9.8r"/>
6293 <affects base="0.9.8" version="0.9.8s"/>
6294 <affects base="0.9.8" version="0.9.8t"/>
6295 <affects base="0.9.8" version="0.9.8u"/>
6296 <affects base="0.9.8" version="0.9.8v"/>
6297 <affects base="0.9.8" version="0.9.8w"/>
6298 <affects base="0.9.8" version="0.9.8x"/>
6299 <affects base="0.9.8" version="0.9.8y"/>
6300 <affects base="1.0.0" version="1.0.0"/>
6301 <affects base="1.0.0" version="1.0.0a"/>
6302 <affects base="1.0.0" version="1.0.0b"/>
6303 <affects base="1.0.0" version="1.0.0c"/>
6304 <affects base="1.0.0" version="1.0.0d"/>
6305 <affects base="1.0.0" version="1.0.0e"/>
6306 <affects base="1.0.0" version="1.0.0f"/>
6307 <affects base="1.0.0" version="1.0.0g"/>
6308 <affects base="1.0.0" version="1.0.0i"/>
6309 <affects base="1.0.0" version="1.0.0j"/>
6310 <affects base="1.0.0" version="1.0.0k"/>
6311 <affects base="1.0.0" version="1.0.0l"/>
6312 <affects base="1.0.1" version="1.0.1"/>
6313 <affects base="1.0.1" version="1.0.1a"/>
6314 <affects base="1.0.1" version="1.0.1b"/>
6315 <affects base="1.0.1" version="1.0.1c"/>
6316 <affects base="1.0.1" version="1.0.1d"/>
6317 <affects base="1.0.1" version="1.0.1e"/>
6318 <affects base="1.0.1" version="1.0.1f"/>
6319 <affects base="1.0.1" version="1.0.1g"/>
6320 <fixed base="1.0.1" version="1.0.1h" date="20140605">
6322 <fixed base="1.0.0" version="1.0.0m" date="20140605">
6324 <fixed base="0.9.8" version="0.9.8za" date="20140605">
6326 <description>By sending an invalid DTLS handshake to an OpenSSL DTLS client the code can be made to recurse eventually crashing in a DoS attack. Only applications using OpenSSL as a DTLS client are affected.</description>
6327 <advisory url="/news/secadv/20140605.txt"/>
6328 <reported source="Imre Rad (Search-Lab Ltd.)"/>
6331 <issue public="20140605">
6332 <cve name="2014-0195"/>
6333 <affects base="0.9.8" version="0.9.8o"/>
6334 <affects base="0.9.8" version="0.9.8p"/>
6335 <affects base="0.9.8" version="0.9.8q"/>
6336 <affects base="0.9.8" version="0.9.8r"/>
6337 <affects base="0.9.8" version="0.9.8s"/>
6338 <affects base="0.9.8" version="0.9.8t"/>
6339 <affects base="0.9.8" version="0.9.8u"/>
6340 <affects base="0.9.8" version="0.9.8v"/>
6341 <affects base="0.9.8" version="0.9.8w"/>
6342 <affects base="0.9.8" version="0.9.8x"/>
6343 <affects base="0.9.8" version="0.9.8y"/>
6344 <affects base="1.0.0" version="1.0.0"/>
6345 <affects base="1.0.0" version="1.0.0a"/>
6346 <affects base="1.0.0" version="1.0.0b"/>
6347 <affects base="1.0.0" version="1.0.0c"/>
6348 <affects base="1.0.0" version="1.0.0d"/>
6349 <affects base="1.0.0" version="1.0.0e"/>
6350 <affects base="1.0.0" version="1.0.0f"/>
6351 <affects base="1.0.0" version="1.0.0g"/>
6352 <affects base="1.0.0" version="1.0.0i"/>
6353 <affects base="1.0.0" version="1.0.0j"/>
6354 <affects base="1.0.0" version="1.0.0k"/>
6355 <affects base="1.0.0" version="1.0.0l"/>
6356 <affects base="1.0.1" version="1.0.1"/>
6357 <affects base="1.0.1" version="1.0.1a"/>
6358 <affects base="1.0.1" version="1.0.1b"/>
6359 <affects base="1.0.1" version="1.0.1c"/>
6360 <affects base="1.0.1" version="1.0.1d"/>
6361 <affects base="1.0.1" version="1.0.1e"/>
6362 <affects base="1.0.1" version="1.0.1f"/>
6363 <affects base="1.0.1" version="1.0.1g"/>
6364 <fixed base="1.0.1" version="1.0.1h" date="20140605">
6366 <fixed base="1.0.0" version="1.0.0m" date="20140605">
6368 <fixed base="0.9.8" version="0.9.8za" date="20140605">
6370 <description>A buffer overrun attack can be triggered by sending invalid DTLS fragments
6371 to an OpenSSL DTLS client or server. This is potentially exploitable to
6372 run arbitrary code on a vulnerable client or server. Only applications using OpenSSL as a DTLS client or server affected.
6374 <advisory url="/news/secadv/20140605.txt"/>
6375 <reported source="Jüri Aedla"/>
6378 <issue public="20140421">
6379 <cve name="2014-0198"/>
6380 <affects base="1.0.0" version="1.0.0"/>
6381 <affects base="1.0.0" version="1.0.0a"/>
6382 <affects base="1.0.0" version="1.0.0b"/>
6383 <affects base="1.0.0" version="1.0.0c"/>
6384 <affects base="1.0.0" version="1.0.0d"/>
6385 <affects base="1.0.0" version="1.0.0e"/>
6386 <affects base="1.0.0" version="1.0.0f"/>
6387 <affects base="1.0.0" version="1.0.0g"/>
6388 <affects base="1.0.0" version="1.0.0i"/>
6389 <affects base="1.0.0" version="1.0.0j"/>
6390 <affects base="1.0.0" version="1.0.0k"/>
6391 <affects base="1.0.0" version="1.0.0l"/>
6392 <affects base="1.0.1" version="1.0.1"/>
6393 <affects base="1.0.1" version="1.0.1a"/>
6394 <affects base="1.0.1" version="1.0.1b"/>
6395 <affects base="1.0.1" version="1.0.1c"/>
6396 <affects base="1.0.1" version="1.0.1d"/>
6397 <affects base="1.0.1" version="1.0.1e"/>
6398 <affects base="1.0.1" version="1.0.1f"/>
6399 <affects base="1.0.1" version="1.0.1g"/>
6400 <fixed base="1.0.1" version="1.0.1h" date="20140605">
6402 <fixed base="1.0.0" version="1.0.0m" date="20140605">
6404 <description>A flaw in the do_ssl3_write function can allow remote attackers to
6405 cause a denial of service via a NULL pointer dereference. This flaw
6406 only affects OpenSSL 1.0.0 and 1.0.1 where SSL_MODE_RELEASE_BUFFERS is
6407 enabled, which is not the default and not common.</description>
6408 <advisory url="/news/secadv/20140605.txt"/>
6411 <issue public="20140408">
6412 <cve name="2010-5298"/>
6413 <affects base="1.0.0" version="1.0.0"/>
6414 <affects base="1.0.0" version="1.0.0a"/>
6415 <affects base="1.0.0" version="1.0.0b"/>
6416 <affects base="1.0.0" version="1.0.0c"/>
6417 <affects base="1.0.0" version="1.0.0d"/>
6418 <affects base="1.0.0" version="1.0.0e"/>
6419 <affects base="1.0.0" version="1.0.0f"/>
6420 <affects base="1.0.0" version="1.0.0g"/>
6421 <affects base="1.0.0" version="1.0.0i"/>
6422 <affects base="1.0.0" version="1.0.0j"/>
6423 <affects base="1.0.0" version="1.0.0k"/>
6424 <affects base="1.0.0" version="1.0.0l"/>
6425 <affects base="1.0.1" version="1.0.1"/>
6426 <affects base="1.0.1" version="1.0.1a"/>
6427 <affects base="1.0.1" version="1.0.1b"/>
6428 <affects base="1.0.1" version="1.0.1c"/>
6429 <affects base="1.0.1" version="1.0.1d"/>
6430 <affects base="1.0.1" version="1.0.1e"/>
6431 <affects base="1.0.1" version="1.0.1f"/>
6432 <affects base="1.0.1" version="1.0.1g"/>
6433 <fixed base="1.0.1" version="1.0.1h" date="20140605">
6435 <fixed base="1.0.0" version="1.0.0m" date="20140605">
6437 <description>A race condition in the ssl3_read_bytes function can allow remote
6438 attackers to inject data across sessions or cause a denial of service.
6439 This flaw only affects multithreaded applications using OpenSSL 1.0.0
6440 and 1.0.1, where SSL_MODE_RELEASE_BUFFERS is enabled, which is not the
6441 default and not common.</description>
6442 <advisory url="/news/secadv/20140605.txt"/>
6445 <issue public="20140530">
6446 <cve name="2014-3470"/>
6447 <affects base="0.9.8" version="0.9.8"/>
6448 <affects base="0.9.8" version="0.9.8a"/>
6449 <affects base="0.9.8" version="0.9.8b"/>
6450 <affects base="0.9.8" version="0.9.8c"/>
6451 <affects base="0.9.8" version="0.9.8d"/>
6452 <affects base="0.9.8" version="0.9.8e"/>
6453 <affects base="0.9.8" version="0.9.8f"/>
6454 <affects base="0.9.8" version="0.9.8g"/>
6455 <affects base="0.9.8" version="0.9.8h"/>
6456 <affects base="0.9.8" version="0.9.8i"/>
6457 <affects base="0.9.8" version="0.9.8j"/>
6458 <affects base="0.9.8" version="0.9.8k"/>
6459 <affects base="0.9.8" version="0.9.8l"/>
6460 <affects base="0.9.8" version="0.9.8m"/>
6461 <affects base="0.9.8" version="0.9.8n"/>
6462 <affects base="0.9.8" version="0.9.8o"/>
6463 <affects base="0.9.8" version="0.9.8p"/>
6464 <affects base="0.9.8" version="0.9.8q"/>
6465 <affects base="0.9.8" version="0.9.8r"/>
6466 <affects base="0.9.8" version="0.9.8s"/>
6467 <affects base="0.9.8" version="0.9.8t"/>
6468 <affects base="0.9.8" version="0.9.8u"/>
6469 <affects base="0.9.8" version="0.9.8v"/>
6470 <affects base="0.9.8" version="0.9.8w"/>
6471 <affects base="0.9.8" version="0.9.8x"/>
6472 <affects base="0.9.8" version="0.9.8y"/>
6473 <affects base="1.0.0" version="1.0.0"/>
6474 <affects base="1.0.0" version="1.0.0a"/>
6475 <affects base="1.0.0" version="1.0.0b"/>
6476 <affects base="1.0.0" version="1.0.0c"/>
6477 <affects base="1.0.0" version="1.0.0d"/>
6478 <affects base="1.0.0" version="1.0.0e"/>
6479 <affects base="1.0.0" version="1.0.0f"/>
6480 <affects base="1.0.0" version="1.0.0g"/>
6481 <affects base="1.0.0" version="1.0.0i"/>
6482 <affects base="1.0.0" version="1.0.0j"/>
6483 <affects base="1.0.0" version="1.0.0k"/>
6484 <affects base="1.0.0" version="1.0.0l"/>
6485 <affects base="1.0.1" version="1.0.1"/>
6486 <affects base="1.0.1" version="1.0.1a"/>
6487 <affects base="1.0.1" version="1.0.1b"/>
6488 <affects base="1.0.1" version="1.0.1c"/>
6489 <affects base="1.0.1" version="1.0.1d"/>
6490 <affects base="1.0.1" version="1.0.1e"/>
6491 <affects base="1.0.1" version="1.0.1f"/>
6492 <affects base="1.0.1" version="1.0.1g"/>
6493 <fixed base="1.0.1" version="1.0.1h" date="20140605">
6495 <fixed base="1.0.0" version="1.0.0m" date="20140605">
6497 <fixed base="0.9.8" version="0.9.8za" date="20140605">
6499 <description>OpenSSL TLS clients enabling anonymous ECDH ciphersuites are subject to a
6500 denial of service attack.</description>
6501 <reported source="Felix Gröbert and Ivan Fratrić (Google)"/>
6502 <advisory url="/news/secadv/20140605.txt"/>