Certificate ServerApplication · Redhat
CVE-2007-4994
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCertificate 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceCertificate Server 7.2 in Red Hat Certificate System has a race condition where new revocations occurring during CRL generation are not properly captured, causing those revoked certificates to be omitted from the current CRL and remain valid until the next CRL cycle.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Certificate ServerApplication
= 7.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Red Hat Certificate Server is installedCheck for the presence of the Red Hat Certificate System package using the system package manager. For RHEL-based systems: rpm -qa | grep -i certserver or yum list installed | grep -i certificate-serverAffected if The package is not present on the system - the vulnerability does not apply.
-
Identify the installed version of Red Hat Certificate ServerRun 'rpm -q redhat-certificate-system' or check the specific package version installed. Compare the version number against the affected version 7.2.Affected if The installed version is exactly 7.2 - this version is affected by the race condition in CRL generation.
-
Determine if Certificate Server CRL generation is enabledCheck the Certificate Server configuration files (typically in /var/lib/pki-ca or /etc/pki-ca) for CRL generation settings. Look for CRL generation schedules or enablement flags in the CS.cfg or similar configuration files.Affected if CRL generation is disabled or not configured - the race condition does not apply since CRLs are not being generated.
-
Check the current CRL generation intervalReview the CRL publish interval or generation schedule in the Certificate Server configuration. This is typically found in the CA subsystem configuration under CRL settings.Affected if CRL generation is enabled - the race condition affects any CRL generation cycle where new revocations occur during the CRL generation window.
The environment is affected if Red Hat Certificate Server version 7.2 is installed and CRL generation is enabled, as the race condition will cause newly revoked certificates to be omitted from the generated CRL.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to a patched version of Red Hat Certificate System, or implement more frequent CRL generation to reduce the window of exposure.
Fix this in Certificate Server
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-4994 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2007-4994 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data