CVE-2013-5915
UnknownEPSS 2.14%
Last modified
CVE-2013-5915 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 2.14% chance of exploitation in the next 30 days.
Description
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Polarssl | Polarssl | <= 1.2.8 | — |
| 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.1.6 | — |
| Polarssl | Polarssl | 1.1.8 | — |
| Polarssl | Polarssl | 1.2.0 | — |
| Polarssl | Polarssl | 1.2.1 | — |
| Polarssl | Polarssl | 1.2.2 | — |
| Polarssl | Polarssl | 1.2.3 | — |
| Polarssl | Polarssl | 1.2.4 | — |
| Polarssl | Polarssl | 1.2.5 | — |
| Polarssl | Polarssl | 1.2.6 | — |
| Polarssl | Polarssl | 1.2.7 | — |
References
- http://secunia.com/advisories/55084Vendor Advisory
- http://secunia.com/advisories/55084Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2013-5915?
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.
How severe is CVE-2013-5915?
Severity scoring for CVE-2013-5915 is pending analysis. The EPSS model estimates a 2.14% probability of exploitation in the next 30 days.
How do I fix CVE-2013-5915?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2013
- CVE-2013-5909Unspecified vulnerability in the PeopleSoft Enterprise HRMS …
- CVE-2013-5910Unspecified vulnerability in Oracle Java SE 6u65 and 7u45, J…
- CVE-2013-5911Cross-site scripting (XSS) vulnerability in devform.php in T…
- CVE-2013-5912VhttpdMgr in Thomson Reuters Velocity Analytics Vhayu Analyt…
- CVE-2013-5913Cross-site scripting (XSS) vulnerability in the getRecommSea…
- CVE-2013-5914Buffer overflow in the ssl_read_record function in ssl_tls.c…
- CVE-2013-5916Cross-site scripting (XSS) vulnerability in falha.php in the…
- CVE-2013-5917SQL injection vulnerability in wp-comments-post.php in the N…
- CVE-2013-5918Cross-site scripting (XSS) vulnerability in platinum_seo_pac…
- CVE-2013-5919Suricata before 1.4.6 allows remote attackers to cause a den…
- CVE-2013-5930Cross-site scripting (XSS) vulnerability in search_residenti…
- CVE-2013-5931SQL injection vulnerability in property_listings_detail.php …
Are you affected by CVE-2013-5915?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST