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

> Remote attackers can bypass certificate blacklists by crafting data in the unsigned portion of certificates, defeating fingerprint-based protection mechanisms.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/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:** Yes
- **Published:** 9 Jan 2015
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2014-8275, GHSA-85qv-mgh4-gm8w, UBUNTU-CVE-2014-8275

## What is CVE-2014-8275?

CVE-2014-8275 is a medium-severity vulnerability in Openssl Openssl, published on 9 Jan 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OpenSSL before 0.9.8zd, 1.0.0 before 1.0.0p, and 1.0.1 before 1.0.1k does not enforce certain constraints on certificate data, which allows remote attackers to defeat a fingerprint-based certificate-blacklist protection mechanism by including crafted data within a certificate's unsigned portion, related to crypto/asn1/a_verify.c, crypto/dsa/dsa_asn1.c, crypto/ecdsa/ecs_vrf.c, and crypto/x509/x_all.c.

Weakness: CWE-310

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

It affects 1 product.


Products: Openssl Openssl.

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

Upgrade to a fixed version.

## Is CVE-2014-8275 being exploited?

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

Public exploit code:

- https://github.com/uthrasri/Openssl_G2.5_CVE-2014-8275 (github_poc): https://github.com/uthrasri/Openssl_G2.5_CVE-2014-8275
- https://github.com/uthrasri/CVE-2014-8275_openssl_g2.5 (github_poc): https://github.com/uthrasri/CVE-2014-8275_openssl_g2.5

## Other vulnerabilities in Openssl Openssl

- [CVE-2009-3245](https://insights.sbomify.com/CVE-2009-3245/): Null dereference in n/a (critical 10.0)
- [CVE-2006-3738](https://insights.sbomify.com/CVE-2006-3738/): Memory corruption in n/a (critical 10.0)
- [CVE-2026-63073](https://insights.sbomify.com/CVE-2026-63073/): Untrusted Sender DN Used as Format String in CMP Response Validation (critical 9.8)
- [CVE-2016-6309](https://insights.sbomify.com/CVE-2016-6309/): Use after free in n/a (critical 9.8)
- [CVE-2016-0799](https://insights.sbomify.com/CVE-2016-0799/): Integer overflow in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-8275 is a medium-severity vulnerability in Openssl Openssl, published on 9 Jan 2015. 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-8275 in the wild and no public exploit code.

Affected product: Openssl Openssl. 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-8275/ (Markdown: https://insights.sbomify.com/CVE-2014-8275/index.md)
```

## Sources

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

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