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

> Attackers with revoked certificates can bypass CRL checks due to race conditions during list generation, allowing unauthorized access.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Nov 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-25hg-rr9r-5w7v, RHSA-2007:0934, RHSA-2008:0566

## What is CVE-2007-4994?

CVE-2007-4994 is a high-severity vulnerability in n/a, published on 6 Nov 2007. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Certificate Server 7.2 in Red Hat Certificate System (RHCS) does not properly handle new revocations that occur while a Certificate Revocation List (CRL) is being generated, which might prevent certain revoked certificates from appearing on the CRL quickly and allow users with revoked certificates to bypass the intended CRL.

Weakness: CWE-255

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `rhpki-ca` | Red Hat:certificate_system:7.2 | All versions | 0:7.2.0-4 |
| `rhpki-common` | Red Hat:certificate_system:7.2 | All versions | 0:7.2.0-8 |
| `rhpki-util` | Red Hat:certificate_system:7.2 | All versions | 0:7.2.0-4 |
| `rhpki-ca` | Red Hat:certificate_system:7.3 | All versions | 0:7.3.0-11.el4 |
| `rhpki-common` | Red Hat:certificate_system:7.3 | All versions | 0:7.3.0-34.el4 |
| `rhpki-util` | Red Hat:certificate_system:7.3 | All versions | 0:7.3.0-18.el4 |

Products: Redhat Certificate Server.

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

Apply the vendor's patch.

## Is CVE-2007-4994 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2007-4994 is a high-severity vulnerability in n/a, published on 6 Nov 2007. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-4994 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-4994/ (Markdown: https://insights.sbomify.com/CVE-2007-4994/index.md)
```

## Sources

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

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