Polarssl vulnerabilitiesNone on the known-exploited list.
Polarssl has 15 published vulnerabilities across 1 product in our catalogue. None of them is on the list of flaws known to be exploited today. The most affected product is Polarssl, with 15. If you run Polarssl software, patch the exploited flaws first.
We keep watching the known-exploited list.
Which Polarssl products have the most vulnerabilities?
Polarssl leads with 15 published vulnerabilities. Open a product to see its versions and which of its flaws criminals are already using.
Which Polarssl vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Polarssl's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Polarssl flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 36%
The TLS protocol 1.1 and 1.2 and the DTLS protocol 1.0 and 1.2, as used in OpenSSL, OpenJDK, PolarSSL, and other products, do not properly consider timing side-channel attacks on a MAC check requirement during the...
- 3.7%CVE-2015-5291Medium
Heap-based buffer overflow in PolarSSL 1.x before 1.2.17 and ARM mbed TLS (formerly PolarSSL) 1.3.x before 1.3.14 and 2.x before 2.1.2 allows remote SSL servers to cause a denial of service (client crash) and...
- 3.1%CVE-2015-1182High
The asn1_get_sequence_of function in library/asn1parse.c in PolarSSL 1.0 through 1.2.12 and 1.3.x through 1.3.9 does not properly initialize a pointer in the asn1_sequence linked list, which allows remote attackers...
- 3.0%CVE-2013-5914Medium
Buffer overflow in the ssl_read_record function in ssl_tls.c in PolarSSL before 1.1.8, when using TLS 1.1, might allow remote attackers to execute arbitrary code via a long packet.
- 2.9%CVE-2015-8036Medium
Heap-based buffer overflow in ARM mbed TLS (formerly PolarSSL) 1.3.x before 1.3.14 and 2.x before 2.1.2 allows remote SSL servers to cause a denial of service (client crash) and possibly execute arbitrary code via a...
- 2.4%CVE-2014-4911Medium
The ssl_decrypt_buf function in library/ssl_tls.c in PolarSSL before 1.2.11 and 1.3.x before 1.3.8 allows remote attackers to cause a denial of service (crash) via vectors related to the GCM ciphersuites, as...
- 2.2%CVE-2012-2130High
A Security Bypass vulnerability exists in PolarSSL 0.99pre4 through 1.1.1 due to a weak encryption error when generating Diffie-Hellman values and RSA keys.
- 2.1%CVE-2013-5915Medium
The RSA-CRT implementation in PolarSSL before 1.2.9 does not properly perform Montgomery multiplication, which might allow remote attackers to conduct a timing side-channel attack and retrieve RSA private keys.
- 2.1%CVE-2014-8627Medium
PolarSSL 1.3.8 does not properly negotiate the signature algorithm to use, which allows remote attackers to conduct downgrade attacks via unspecified vectors.
- 2.1%CVE-2013-1621Medium
Array index error in the SSL module in PolarSSL before 1.2.5 might allow remote attackers to cause a denial of service via vectors involving a crafted padding-length value during validation of CBC padding in a TLS...
All Polarssl products we track.
1 products, most vulnerabilities first. Find the ones you run, then open a product to see its versions and exploited flaws.
Running Polarssl? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
The TLS protocol 1.1 and 1.2 and the DTLS protocol 1.0 and 1.2, as used in OpenSSL, OpenJDK, PolarSSL, and other products, do not properly consider timing side-channel attacks on a MAC check requirement during the processing of malformed CBC padding, which allows remote attackers to conduct distinguishing attacks and plaintext-recovery attacks via statistical analysis of timing data for crafted packets, aka the "Lucky Thirteen" issue.
- Matched to
- Polarssl on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
Our catalogue lists 15 published vulnerabilities across 1 product and 51 versions from Polarssl.
None of Polarssl's vulnerabilities is on the list of flaws known to be exploited today.
Polarssl, with 15 published vulnerabilities. Its own page lists the ones known to be exploited.
Create a Precursor Intelligence account and track the Polarssl products you run. We match them against every published flaw, give each one a risk score from 0 to 100 and tell you as soon as we spot one that affects you, by email, in the app or by webhook.