First published: Fri Aug 16 2013(Updated: )
From the PolarSSL Security Advisory 2013-03 advisory: "A bug in the logic of the parsing of PEM encoded certificates in x509parse_crt() can result in an infinite loop, thus hogging processing power." A remote attacker could use this flaw to make a TLS/SSL server using PolarSSL consume an excessive amount of CPU. This issue was corrected in PolarSSL versions 1.1.7 and 1.2.8. (Versions prior to these are affected.) External References: <a href="https://polarssl.org/tech-updates/security-advisories/polarssl-security-advisory-2013-03">https://polarssl.org/tech-updates/security-advisories/polarssl-security-advisory-2013-03</a>
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
PolarSSL | =1.1.0 | |
PolarSSL | =1.1.0-rc0 | |
PolarSSL | =1.1.0-rc1 | |
PolarSSL | =1.1.1 | |
PolarSSL | =1.1.2 | |
PolarSSL | =1.1.3 | |
PolarSSL | =1.1.4 | |
PolarSSL | =1.1.5 | |
PolarSSL | =1.1.6 | |
PolarSSL | =1.2.0 | |
PolarSSL | =1.2.1 | |
PolarSSL | =1.2.2 | |
PolarSSL | =1.2.3 | |
PolarSSL | =1.2.4 | |
PolarSSL | =1.2.5 | |
PolarSSL | =1.2.6 | |
PolarSSL | =1.2.7 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2013-4623 has a severity rating that indicates it can lead to denial of service due to infinite looping during certificate parsing.
To fix CVE-2013-4623, upgrade PolarSSL to a version that has addressed the infinite loop bug in x509parse_crt() functionality.
CVE-2013-4623 affects PolarSSL versions 1.1.0 through 1.2.7 across various release candidates and regular releases.
Yes, CVE-2013-4623 can be exploited by a remote attacker to cause a TLS/SSL server using PolarSSL to consume excessive processing power.
Currently, the recommended action for CVE-2013-4623 is to update to a patched version of PolarSSL, as no effective workaround exists.