# CVE-2007-4594: Security feature bypass in n/a

> Attackers can bypass certificate validation in Entrust ESP by exploiting improper handling of missing root CAs or ignored revocation statuses, enabling authentication spoofing.

- **Severity:** Medium 6.4 (`AV:N/AC:L/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:** 29 Aug 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-g72c-x5vr-f3wv

## What is CVE-2007-4594?

CVE-2007-4594 is a medium-severity vulnerability in n/a, published on 29 Aug 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Entrust Entelligence Security Provider (ESP) 8 does not properly validate certificates in certain circumstances involving (1) a chain that omits the root Certification Authority (CA) certificate, or an application that specifies disregarding (2) unknown revocation statuses during path validation or (3) certain errors in the certification path, which might allow context-dependent attackers to spoof certificate authentication.  NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.

Weakness: CWE-255

## Which versions are affected by CVE-2007-4594?

It affects 1 product.


Products: Entrust Entelligence Security Provider.

## How do I fix CVE-2007-4594?

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

## Is CVE-2007-4594 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-4594 and fix it if it is affected.

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

## Sources

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

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