# CVE-2015-1793: Security feature bypass in n/a

> Remote attackers can spoof Certification Authority roles and trigger unintended certificate verifications by exploiting improper Basic Constraints processing in OpenSSL.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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 Jul 2015
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2015-1793, GHSA-4j29-v246-6w5w, MGASA-2015-0274

## What is CVE-2015-1793?

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

### Official description

The X509_verify_cert function in crypto/x509/x509_vfy.c in OpenSSL 1.0.1n, 1.0.1o, 1.0.2b, and 1.0.2c does not properly process X.509 Basic Constraints cA values during identification of alternative certificate chains, which allows remote attackers to spoof a Certification Authority role and trigger unintended certificate verifications via a valid leaf certificate.

Weakness: CWE-254

## Which versions are affected by CVE-2015-1793?

It affects 4 products.


Products: Openssl Openssl, Oracle Jd Edwards Enterpriseone Tools, Oracle Opus 10g Ethernet Switch Family, Oracle Supply Chain Products Suite.

## How do I fix CVE-2015-1793?

Upgrade to a fixed version.

## Is CVE-2015-1793 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2015-1793 exists.

Public exploit code:

- OpenSSL Alternative Chains Certificate Forgery MITM Proxy (metasploit)
- OpenSSL - Alternative Chains Certificate Forgery (exploitdb)

## 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-2015-1793 and fix it if it is affected.

What it is: CVE-2015-1793 is a medium-severity vulnerability in Openssl Openssl, published on 9 Jul 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2015-1793 exists.

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-2015-1793/ (Markdown: https://insights.sbomify.com/CVE-2015-1793/index.md)
```

## Sources

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

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