The default configuration for IPA servers in Red Hat Enterprise Linux 6, when revoking a certificate from an Identity Management replica, do
The default configuration for IPA servers in Red Hat Enterprise Linux 6, when revoking a certificate from an Identity Management replica, does not properly update another Identity Management replica, which causes inconsistent Certificate Revocation Lists (CRLs) to be used and might allow remote attackers to bypass intended access restrictions via a revoked certificate.
- Published
- Apr 2, 2013
- Updated
- Jun 16, 2026
- EPSS
- 1.2% · 67th percentile
- CWE
- CWE-16
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
17
Monitor
Low priority for now.
- CVSS
- 17 / 40 · 4.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.2%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| redhat | enterprise linux | cpe:2.3:o:redhat:enterprise_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- redhat enterprise linux6.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Red Hat:enterprise_linux:6::client | ipa | before 0:3.0.0-25.el6 | 0:3.0.0-25.el6 |
| Red Hat:enterprise_linux:6::client | ipa-admintools | before 0:3.0.0-25.el6 | 0:3.0.0-25.el6 |
| Red Hat:enterprise_linux:6::client | ipa-client | before 0:3.0.0-25.el6 | 0:3.0.0-25.el6 |
| Red Hat:enterprise_linux:6::client | ipa-debuginfo | before 0:3.0.0-25.el6 | 0:3.0.0-25.el6 |
| Red Hat:enterprise_linux:6::client | ipa-python | before 0:3.0.0-25.el6 | 0:3.0.0-25.el6 |
| Red Hat:enterprise_linux:6::client | ipa-server | before 0:3.0.0-25.el6 | 0:3.0.0-25.el6 |
| Red Hat:enterprise_linux:6::client | ipa-server-selinux | before 0:3.0.0-25.el6 | 0:3.0.0-25.el6 |
| Red Hat:enterprise_linux:6::client | ipa-server-trust-ad | before 0:3.0.0-25.el6 | 0:3.0.0-25.el6 |
Same product
redhat: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-50387Certain DNSSEC aspects of the DNS protocol (in RFC 4033, 4034, 4035, 6840, and related RFCs) allow remote attackers to cause a denial of ser60This week
- CVE-2015-3246libuser before 0.56.13-8 and 0.60 before 0.60-7, as used in the userhelper program in the usermode package, directly modifies /etc/passwd, wKEV53Plan
- CVE-2017-5456A mechanism to bypass file system access protections in the sandbox using the file system request constructor through an IPC message.40Plan
- CVE-2017-5428An integer overflow in "createImageBitmap()" was reported through the Pwn2Own contest.40Plan
- CVE-2021-20325Missing fixes for CVE-2021-40438 and CVE-2021-26691 in the versions of httpd, as shipped in Red Hat Enterprise Linux 8.5.0, causes a securit39Monitor
- CVE-2008-3844Certain Red Hat Enterprise Linux (RHEL) 4 and 5 packages for OpenSSH, as signed in August 2008 using a legitimate Red Hat GPG key, contain a38Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| red hat:ipa | 0:3.0.0-25.el6 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:ipa-admintools | 0:3.0.0-25.el6 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:ipa-client | 0:3.0.0-25.el6 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:ipa-debuginfo | 0:3.0.0-25.el6 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:ipa-python | 0:3.0.0-25.el6 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:ipa-server | 0:3.0.0-25.el6 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:ipa-server-selinux | 0:3.0.0-25.el6 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:ipa-server-trust-ad | 0:3.0.0-25.el6 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
If successful
- Confidentiality
- none
- Integrity
- P · data or configuration can be modified
- Availability
- none
- Attack complexity
- M
- Confidentiality impact
- None
- Integrity impact
- P
- Availability impact
- None
Weakness class (CWE)
CWE-16 · ConfigurationCVSS vector
AV:N/AC:M/Au:N/C:N/I:P/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.