First published: Mon Aug 24 2015(Updated: )
Memory leak in PolarSSL before 1.2.12 and 1.3.x before 1.3.9 allows remote attackers to cause a denial of service (memory consumption) via a large number of crafted X.509 certificates. NOTE: this identifier has been SPLIT per ADT3 due to different affected versions. See CVE-2014-9744 for the ClientHello message issue.
Credit: meissner@suse.de
Affected Software | Affected Version | How to fix |
---|---|---|
PolarSSL | <=1.2.11 | |
PolarSSL | =1.3.0 | |
PolarSSL | =1.3.1 | |
PolarSSL | =1.3.2 | |
PolarSSL | =1.3.3 | |
PolarSSL | =1.3.4 | |
PolarSSL | =1.3.5 | |
PolarSSL | =1.3.6 | |
PolarSSL | =1.3.7 | |
PolarSSL | =1.3.8 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2014-8628 is classified as a high severity vulnerability due to its potential to cause denial of service via memory consumption.
To fix CVE-2014-8628, users should upgrade to PolarSSL version 1.2.12 or 1.3.9 and above.
Applications using affected versions of PolarSSL could experience denial of service due to memory leaks triggered by crafted X.509 certificates.
CVE-2014-8628 affects PolarSSL versions earlier than 1.2.12 and 1.3.x earlier than 1.3.9.
No, CVE-2014-8628 primarily leads to denial of service and does not directly result in data exposure.