CVE-2014-2901 Other in n/a
High 7.5
Published
Updated
Check this codebase for CVE-2014-2901 and fix it if it is affected.
What it is: CVE-2014-2901 is a high-severity vulnerability in Wolfssl Wolfssl, published on 21 Nov 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-2901 in the wild and no public exploit code.
Affected product: Wolfssl Wolfssl. 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-2014-2901/ (Markdown: https://insights.sbomify.com/CVE-2014-2901/index.md)
wolfSSL fails to properly validate server hostnames in certificates, allowing potential man-in-the-middle attacks.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2014-2901?
CVE-2014-2901 is a high-severity vulnerability in Wolfssl Wolfssl, published on 21 Nov 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
wolfssl before 3.2.0 does not properly issue certificates for a server's hostname.
Weakness: CWE-295
Which versions are affected by CVE-2014-2901?
It affects 1 product.
Products include Wolfssl Wolfssl.
How do I fix CVE-2014-2901?
Upgrade to a fixed version.
Is CVE-2014-2901 being exploited?
There is no known exploitation of CVE-2014-2901 in the wild and no public exploit code.
Other vulnerabilities in Wolfssl Wolfssl
Sources
Also known as DEBIAN-CVE-2014-2901, GHSA-grv9-x6wx-fw8r.