CVE-2018-1080: Dogtag PKI, through version 10.6.1, has a vulnerability in AAclAuthz.java that, under certain configurations, causes the application of ACL…
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.4% (FIRST EPSS); higher than 74.5% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: dogtag-pki (Debian:11) 10.6.6-1; pki-base (Red Hat:enterprise_linux:7::client) 0:10.5.1-13.1.el7_5; pki-base-java (Red Hat:enterprise_linux:7::client) 0:10.5.1-13.1.el7_5.
Low priority for now. Upgrade to dogtag-pki (Debian:11) 10.6.6-1; pki-base (Red Hat:enterprise_linux:7::client) 0:10.5.1-13.1.el7_5; pki-base-java (Red Hat:enterprise_linux:7::client) 0:10.5.1-13.1.el7_5 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
Dogtag PKI, through version 10.6.1, has a vulnerability in AAclAuthz.java that, under certain configurations, causes the application of ACL allow and deny rules to be reversed. If a server is configured to process allow rules before deny rules (authz.evaluateOrder=allow,deny), then allow rules will deny access and deny rules will grant access. This may result in an escalation of privileges or have other unintended consequences.
- Published
- Jul 2, 2018
- Updated
- Jun 16, 2026
- EPSS
- 1.4% · 74th percentile
- CWE
- CWE-284
Report tools
Action score
32
Low priority for now.
- CVSS
- 32 / 40 · 8.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.4%
CNA vs NVD score
- NVD
- 8.1
- CNA · redhat
- 7.5
- 0.6 point gap
CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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.
Is your version affected? Check itNoroxi 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 |
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.
[UNKNOWN] pki-core
- PKI 10.6.1affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- dogtagpki dogtagpkiup to 10.6.1 inclusive
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.6.6-1 | 10.6.6-1 |
| Red Hat:enterprise_linux:7::client | pki-base | before 0:10.5.1-13.1.el7_5 | 0:10.5.1-13.1.el7_5 |
| Red Hat:enterprise_linux:7::client | pki-base-java | before 0:10.5.1-13.1.el7_5 | 0:10.5.1-13.1.el7_5 |
| Red Hat:enterprise_linux:7::client | pki-ca | before 0:10.5.1-13.1.el7_5 | 0:10.5.1-13.1.el7_5 |
| Red Hat:enterprise_linux:7::client | pki-core | before 0:10.5.1-13.1.el7_5 | 0:10.5.1-13.1.el7_5 |
| Red Hat:enterprise_linux:7::client | pki-core-debuginfo | before 0:10.5.1-13.1.el7_5 | 0:10.5.1-13.1.el7_5 |
| Red Hat:enterprise_linux:7::client | pki-javadoc | before 0:10.5.1-13.1.el7_5 | 0:10.5.1-13.1.el7_5 |
| Red Hat:enterprise_linux:7::client | pki-kra | before 0:10.5.1-13.1.el7_5 | 0:10.5.1-13.1.el7_5 |
| Red Hat:enterprise_linux:7::client | pki-server | before 0:10.5.1-13.1.el7_5 | 0:10.5.1-13.1.el7_5 |
| Red Hat:enterprise_linux:7::client | pki-symkey | before 0:10.5.1-13.1.el7_5 | 0:10.5.1-13.1.el7_5 |
| Red Hat:enterprise_linux:7::client | pki-tools | before 0:10.5.1-13.1.el7_5 | 0:10.5.1-13.1.el7_5 |
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-2021-20179A flaw was found in pki-core.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…31Monitor
Published before and after this one in the same product
- Later →CVE-2019-10178Mar 18, 2020 · It was found that the Token Processing Service (TPS) did not properly sanitize the Token IDs from the "Activity" page, enabling a Stored…24Monitor
- Later →CVE-2019-10180Mar 31, 2020 · A vulnerability was found in all pki-core 10.x.x version, where the Token Processing Service (TPS) did not properly sanitize several…19Monitor
- Later →CVE-2020-15720Jul 14, 2020 · In Dogtag PKI through 10.8.3, the pki.client.PKIConnection class did not enable python-requests certificate validation.27Monitor
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.6.6-1 · Debian:11 | Package registry (OSV) |
| red hat:pki-base | 0:10.5.1-13.1.el7_5 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:pki-base-java | 0:10.5.1-13.1.el7_5 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:pki-ca | 0:10.5.1-13.1.el7_5 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:pki-core | 0:10.5.1-13.1.el7_5 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:pki-core-debuginfo | 0:10.5.1-13.1.el7_5 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:pki-javadoc | 0:10.5.1-13.1.el7_5 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:pki-kra | 0:10.5.1-13.1.el7_5 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:pki-server | 0:10.5.1-13.1.el7_5 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:pki-symkey | 0:10.5.1-13.1.el7_5 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:pki-tools | 0:10.5.1-13.1.el7_5 · Red Hat:enterprise_linux:7::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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-284 · Improper Access ControlCVSS vector
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
Attack patterns (CAPEC)
- Embedding Scripts within ScriptsCAPEC-19likelihood: High · High
- Malicious Logic InsertionCAPEC-441likelihood: Medium · High
- Modification of Windows Service ConfigurationCAPEC-478likelihood: Low · High
- Malicious Root CertificateCAPEC-479likelihood: Low · Low
- Intent SpoofCAPEC-502
- WebView ExposureCAPEC-503
- Data Injected During ConfigurationCAPEC-536likelihood: Low · High
- Incomplete Data Deletion in a Multi-Tenant EnvironmentCAPEC-546likelihood: Low · Medium
ATT&CK techniques
- RootkitT1014
- Obfuscated Files or Information: Embedded PayloadsT1027.009
- Boot or Logon Initialization ScriptsT1037
- Taint shared contentT1080
- Server Software Component: Terminal Services DLLT1505.005
- Pre-OS Boot:BootkitT1542.003
- Create or Modify System ProcessT1543
- Create or Modify System Process: Launch AgentT1543.001
- Create or Modify System Process:Windows ServiceT1543.003
- Create or Modify System Process: Launch DaemonT1543.004
- Event Triggered Execution:Change Default File AssociationT1546.001
- Event Triggered Execution:.bash_profile and .bashrcT1546.004
- Event Triggered Execution: Accessibility FeaturesT1546.008
- Event Triggered Execution: Installer PackagesT1546.016
- Boot or Logon Autostart ExecutionT1547
- Boot or Logon Autostart Execution:Kernel Modules and ExtensionsT1547.006
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.