CVE-2013-1621
Last modified
CVE-2013-1621 is a vulnerability of currently unknown severity. 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 session, a different vulnerability than CVE-2013-0169.. EPSS estimates a 2.07% chance of exploitation in the next 30 days.
Description
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 session, a different vulnerability than CVE-2013-0169.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Polarssl | Polarssl | <= 1.2.4 | — |
| Polarssl | Polarssl | 0.10.0 | — |
| Polarssl | Polarssl | 0.10.1 | — |
| Polarssl | Polarssl | 0.11.0 | — |
| Polarssl | Polarssl | 0.11.1 | — |
| Polarssl | Polarssl | 0.12.0 | — |
| Polarssl | Polarssl | 0.12.1 | — |
| Polarssl | Polarssl | 0.13.1 | — |
| Polarssl | Polarssl | 0.14.0 | — |
| Polarssl | Polarssl | 0.14.2 | — |
| Polarssl | Polarssl | 0.14.3 | — |
| Polarssl | Polarssl | 0.99 | Pre1 |
| Polarssl | Polarssl | 1.0.0 | — |
| Polarssl | Polarssl | 1.1.0 | — |
| Polarssl | Polarssl | 1.1.1 | — |
| Polarssl | Polarssl | 1.1.2 | — |
| Polarssl | Polarssl | 1.1.3 | — |
| Polarssl | Polarssl | 1.1.4 | — |
| Polarssl | Polarssl | 1.1.5 | — |
| Polarssl | Polarssl | 1.2.0 | — |
| Polarssl | Polarssl | 1.2.1 | — |
| Polarssl | Polarssl | 1.2.2 | — |
| Polarssl | Polarssl | 1.2.3 | — |
References
- https://polarssl.org/tech-updates/releases/polarssl-1.2.5-releasedPatch, Vendor Advisory
- https://polarssl.org/tech-updates/releases/polarssl-1.2.5-releasedPatch, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2013-1621?
How severe is CVE-2013-1621?
How do I fix CVE-2013-1621?
Are you affected by CVE-2013-1621?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
