Memory corruption via incorrect DoAlert length check
Published Jan 28, 2020 · Updated Aug 6, 2024
Improper alert length validation in wolfSSL CyaSSL before 2.9.4 allows remote attackers to trigger memory corruption or an out-of-bounds read. The DoAlert function applies an incorrect length check while processing an incoming TLS or DTLS alert, permitting access beyond the supplied message buffer. No authentication or user interaction is required, but published sources do not specify the crafted alert fields or whether the outcome is a crash or data exposure.
Summary
What happened
Improper alert length validation in wolfSSL CyaSSL before 2.9.4 allows remote attackers to trigger memory corruption or an out-of-bounds read. The DoAlert function applies an incorrect length check while processing an incoming TLS or DTLS alert, permitting access beyond the supplied message buffer. No authentication or user interaction is required, but published sources do not specify the crafted alert fields or whether the outcome is a crash or data exposure.
The record
- CVE
- CVE-2014-2896
- Published
- Jan 28, 2020
- Updated
- Aug 6, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-125
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 28, 2020CVE publishedPublication date reported by the CVE source.
- Aug 6, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo