CVE-2013-5914 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 e
Medium 6.8
Published
Updated
Check this codebase for CVE-2013-5914 and fix it if it is affected.
What it is: CVE-2013-5914 is a medium-severity vulnerability in n/a, published on 26 Oct 2013.
Exploitation: There is no known exploitation of CVE-2013-5914 in the wild and no public exploit code.
Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2013-5914/ (Markdown: https://insights.sbomify.com/CVE-2013-5914/index.md)
- Exploited in the wild
- Not known
- Fix
- Available
What is CVE-2013-5914?
CVE-2013-5914 is a medium-severity vulnerability in n/a, published on 26 Oct 2013.
Official description
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.
Weakness: CWE-119
Which versions are affected by CVE-2013-5914?
It affects 1 product.
Products include Polarssl Polarssl.
How do I fix CVE-2013-5914?
Upgrade to a fixed version.
Is CVE-2013-5914 being exploited?
There is no known exploitation of CVE-2013-5914 in the wild and no public exploit code.
Other vulnerabilities in n/a
Sources
Also known as GHSA-vpwv-hwrv-72hw.