A flaw was found in pki-core.
Noroxi assessment
Priority: Monitor (action score 32/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.2% (FIRST EPSS); higher than 68.1% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: dogtag-pki (Debian:11) 10.10.2-2; pki-base (Red Hat:enterprise_linux:7::client) 0:10.5.18-12.el7_9; pki-base-java (Red Hat:enterprise_linux:7::client) 0:10.5.18-12.el7_9.
Low priority for now. Upgrade to dogtag-pki (Debian:11) 10.10.2-2; pki-base (Red Hat:enterprise_linux:7::client) 0:10.5.18-12.el7_9; pki-base-java (Red Hat:enterprise_linux:7::client) 0:10.5.18-12.el7_9 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
A flaw was found in pki-core. An attacker who has successfully compromised a key could use this flaw to renew the corresponding certificate over and over again, as long as it is not explicitly revoked. The highest threat from this vulnerability is to data confidentiality and integrity.
- Published
- Mar 15, 2021
- Updated
- Jun 16, 2026
- EPSS
- 1.2% · 68th percentile
- CWE
- CWE-863
Report tools
Action score
32
Monitor
Low priority for now.
- CVSS
- 32 / 40 · 8.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| dogtagpki | dogtagpki | cpe:2.3:a:dogtagpki:dogtagpki |
| redhat | certificate system | cpe:2.3:a:redhat:certificate_system |
| redhat | enterprise linux | cpe:2.3:o:redhat:enterprise_linux |
| fedoraproject | fedora | cpe:2.3:o:fedoraproject:fedora |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- dogtagpki dogtagpki10.9.1 and later · before 10.10.0
- dogtagpki dogtagpki10.5.1 and later · before 10.8.0
- dogtagpki dogtagpki10.8.1 and later · before 10.9.0
- dogtagpki dogtagpki10.10.1 and later · before 10.11.0
- dogtagpki dogtagpkibefore 10.5.0
- fedoraproject fedora32
- fedoraproject fedora33
- fedoraproject fedora34
- redhat certificate system10.0
- redhat enterprise linux7.0
- redhat enterprise linux8.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.
n/a pki-core
- pki-core 10.5, pki-core 10.8, pki-core 10.9, pki-core 10.10, pki-core 10.11affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:11 | dogtag-pki | before 10.10.2-2 | 10.10.2-2 |
| Red Hat:enterprise_linux:7::client | pki-base | before 0:10.5.18-12.el7_9 | 0:10.5.18-12.el7_9 |
| Red Hat:enterprise_linux:7::client | pki-base-java | before 0:10.5.18-12.el7_9 | 0:10.5.18-12.el7_9 |
| Red Hat:enterprise_linux:7::client | pki-ca | before 0:10.5.18-12.el7_9 | 0:10.5.18-12.el7_9 |
| Red Hat:enterprise_linux:7::client | pki-core | before 0:10.5.18-12.el7_9 | 0:10.5.18-12.el7_9 |
| Red Hat:enterprise_linux:7::client | pki-core-debuginfo | before 0:10.5.18-12.el7_9 | 0:10.5.18-12.el7_9 |
| Red Hat:enterprise_linux:7::client | pki-javadoc | before 0:10.5.18-12.el7_9 | 0:10.5.18-12.el7_9 |
| Red Hat:enterprise_linux:7::client | pki-kra | before 0:10.5.18-12.el7_9 | 0:10.5.18-12.el7_9 |
| Red Hat:enterprise_linux:7::client | pki-server | before 0:10.5.18-12.el7_9 | 0:10.5.18-12.el7_9 |
| Red Hat:enterprise_linux:7::client | pki-symkey | before 0:10.5.18-12.el7_9 | 0:10.5.18-12.el7_9 |
| Red Hat:enterprise_linux:7::client | pki-tools | before 0:10.5.18-12.el7_9 | 0:10.5.18-12.el7_9 |
| Red Hat:enterprise_linux:8::appstream | jss | before 0:4.7.3-1.module+el8.3.0+8058+d5cd4219 | 0:4.7.3-1.module+el8.3.0+8058+d5cd4219 |
| Red Hat:enterprise_linux:8::appstream | jss-debuginfo | before 0:4.7.3-1.module+el8.3.0+8058+d5cd4219 | 0:4.7.3-1.module+el8.3.0+8058+d5cd4219 |
| Red Hat:enterprise_linux:8::appstream | jss-debugsource | before 0:4.7.3-1.module+el8.3.0+8058+d5cd4219 | 0:4.7.3-1.module+el8.3.0+8058+d5cd4219 |
| Red Hat:enterprise_linux:8::appstream | jss-javadoc | before 0:4.7.3-1.module+el8.3.0+8058+d5cd4219 | 0:4.7.3-1.module+el8.3.0+8058+d5cd4219 |
| Red Hat:enterprise_linux:8::appstream | ldapjdk | before 0:4.22.0-1.module+el8.3.0+6784+6e1e4c62 | 0:4.22.0-1.module+el8.3.0+6784+6e1e4c62 |
| Red Hat:enterprise_linux:8::appstream | ldapjdk-javadoc | before 0:4.22.0-1.module+el8.3.0+6784+6e1e4c62 | 0:4.22.0-1.module+el8.3.0+6784+6e1e4c62 |
| Red Hat:enterprise_linux:8::appstream | pki-base | before 0:10.9.4-3.module+el8.3.0+10353+73f6df5b | 0:10.9.4-3.module+el8.3.0+10353+73f6df5b |
| Red Hat:enterprise_linux:8::appstream | pki-base-java | before 0:10.9.4-3.module+el8.3.0+10353+73f6df5b | 0:10.9.4-3.module+el8.3.0+10353+73f6df5b |
| Red Hat:enterprise_linux:8::appstream | pki-ca | before 0:10.9.4-3.module+el8.3.0+10353+73f6df5b | 0:10.9.4-3.module+el8.3.0+10353+73f6df5b |
| Red Hat:enterprise_linux:8::appstream | pki-core | before 0:10.9.4-3.module+el8.3.0+10353+73f6df5b | 0:10.9.4-3.module+el8.3.0+10353+73f6df5b |
| Red Hat:enterprise_linux:8::appstream | pki-core-debuginfo | before 0:10.9.4-3.module+el8.3.0+10353+73f6df5b | 0:10.9.4-3.module+el8.3.0+10353+73f6df5b |
| Red Hat:enterprise_linux:8::appstream | pki-core-debugsource | before 0:10.9.4-3.module+el8.3.0+10353+73f6df5b | 0:10.9.4-3.module+el8.3.0+10353+73f6df5b |
| Red Hat:enterprise_linux:8::appstream | pki-kra | before 0:10.9.4-3.module+el8.3.0+10353+73f6df5b | 0:10.9.4-3.module+el8.3.0+10353+73f6df5b |
+48
Same product
dogtagpki: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-2414Access to external entities when parsing XML documents can lead to XML external entity (XXE) attacks.56Plan
- CVE-2018-1080Dogtag PKI, through version 10.6.1, has a vulnerability in AAclAuthz.java that, under certain configurations, causes the application of ACL 32Monitor
- CVE-2021-3551A flaw was found in the PKI-server, where the spkispawn command, when run in debug mode, stores admin credentials in the installation log fi31Monitor
- CVE-2020-15720In Dogtag PKI through 10.8.3, the pki.client.PKIConnection class did not enable python-requests certificate validation.27Monitor
- CVE-2020-25715A flaw was found in pki-core 10.9.0.24Monitor
- CVE-2020-1721A flaw was found in the Key Recovery Authority (KRA) Agent Service in pki-core 10.10.5 where it did not properly sanitize the recovery ID du24Monitor
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 |
|---|---|---|
| debian:dogtag-pki | 10.10.2-2 · Debian:11 | Package registry (OSV) |
| red hat:jss | 0:4.7.3-1.module+el8.3.0+8058+d5cd4219 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:jss-debuginfo | 0:4.7.3-1.module+el8.3.0+8058+d5cd4219 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:pki-base | 0:10.5.9-15.el7_6 · Red Hat:rhel_eus:7.6::computenode | Package registry (OSV) |
| red hat:pki-base-java | 0:10.5.9-15.el7_6 · Red Hat:rhel_eus:7.6::computenode | Package registry (OSV) |
| red hat:pki-ca | 0:10.5.9-15.el7_6 · Red Hat:rhel_eus:7.6::computenode | Package registry (OSV) |
| red hat:pki-core | 0:10.5.9-15.el7_6 · Red Hat:rhel_eus:7.6::computenode | Package registry (OSV) |
| red hat:pki-core-debuginfo | 0:10.5.9-15.el7_6 · Red Hat:rhel_eus:7.6::computenode | Package registry (OSV) |
| red hat:pki-javadoc | 0:10.5.9-15.el7_6 · Red Hat:rhel_eus:7.6::computenode | Package registry (OSV) |
| red hat:pki-kra | 0:10.5.9-15.el7_6 · Red Hat:rhel_eus:7.6::computenode | Package registry (OSV) |
| red hat:pki-server | 0:10.5.9-15.el7_6 · Red Hat:rhel_eus:7.6::computenode | Package registry (OSV) |
| red hat:pki-symkey | 0:10.5.9-15.el7_6 · Red Hat:rhel_eus:7.6::computenode | Package registry (OSV) |
| red hat:pki-tools | 0:10.5.9-15.el7_6 · Red Hat:rhel_eus:7.6::computenode | Package registry (OSV) |
| rocky linux:ldapjdk | 0:4.22.0-1.module+el8.4.0+418+b7ae1d4a · Rocky Linux:8 | 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.
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
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-863 · Incorrect AuthorizationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (8 more)Show less
- github.com/dogtagpki/pki/pull/3474
- github.com/dogtagpki/pki/pull/3475
- github.com/dogtagpki/pki/pull/3476
- github.com/dogtagpki/pki/pull/3477
- github.com/dogtagpki/pki/pull/3478
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/DDOLFOLEIV7I4EUC3SCZBXL6E2ER7ZEN/
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/HRE44N6P24AEDKRMWK7RPRLMCUUBRJII/
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/R3I7BRAHLE2WWSY76W3CKFCF5WSSAE24/
Vendor advisories and official records. Exploit/PoC links are deliberately left out.