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>
Affected Software | Affected Version | How to fix |
---|---|---|
PolarSSL | <1.1.7<1.2.8 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-997767 is considered high due to the potential for an infinite loop that can consume excessive processing power.
To fix REDHAT-BUG-997767, update PolarSSL to a version later than 1.2.8.
All users of PolarSSL versions up to 1.2.8 are affected by REDHAT-BUG-997767.
Yes, a remote attacker can exploit REDHAT-BUG-997767 to cause denial of service on a TLS/SSL server.
The products vulnerable due to REDHAT-BUG-997767 are the PolarSSL libraries below version 1.2.8.