# CVE-2014-2900: Security feature bypass in n/a

> Man-in-the-middle attackers can spoof servers by exploiting improper validation of X.509 certificates with unknown critical extensions in wolfSSL.

- **Severity:** Medium 5.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Apr 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-rjjg-j224-h375

## What is CVE-2014-2900?

CVE-2014-2900 is a medium-severity vulnerability in n/a, published on 22 Apr 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

wolfSSL CyaSSL before 2.9.4 does not properly validate X.509 certificates with unknown critical extensions, which allows man-in-the-middle attackers to spoof servers via crafted X.509 certificate.

Weakness: CWE-310

## Which versions are affected by CVE-2014-2900?

It affects 1 product.


Products: Yassl Cyassl.

## How do I fix CVE-2014-2900?

No fix has been published for CVE-2014-2900 yet. Limit exposure of the affected software until one is available.

## Is CVE-2014-2900 being exploited?

There is no known exploitation of CVE-2014-2900 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2014-2899](https://insights.sbomify.com/CVE-2014-2899/): Null dereference in n/a (medium 5.0)
- [CVE-2012-1558](https://insights.sbomify.com/CVE-2012-1558/): Null dereference in n/a (medium 5.0)
- [CVE-2013-1623](https://insights.sbomify.com/CVE-2013-1623/): The TLS and DTLS implementations in wolfSSL CyaSSL before 2.5.0 do not properly consider timing side-channel attacks on a noncompliant MAC c (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-2900 and fix it if it is affected.

What it is: CVE-2014-2900 is a medium-severity vulnerability in n/a, published on 22 Apr 2014. 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-2900 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-2014-2900/ (Markdown: https://insights.sbomify.com/CVE-2014-2900/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2014-2900
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2014-2900
- OSV: https://osv.dev/vulnerability/CVE-2014-2900

---
From sbomify Insights: https://insights.sbomify.com/CVE-2014-2900/
Summaries are generated and may contain mistakes; the official description above is the record.