# CVE-2018-1080: Auth bypass in pki-core > Reversed ACL rule processing in Dogtag PKI allows privilege escalation when configured to evaluate allow rules before deny rules. - **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 2 Jul 2018 - **Updated:** 5 Aug 2024 - **Also known as:** DEBIAN-CVE-2018-1080, GHSA-h277-5r6v-m3gv, RHSA-2018:1979, UBUNTU-CVE-2018-1080 ## What is CVE-2018-1080? CVE-2018-1080 is a high-severity authentication bypass vulnerability in [UNKNOWN] pki-core, published on 2 Jul 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description 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. Weakness: CWE-284 (Improper Access Control) ## Which versions are affected by CVE-2018-1080? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `pki-base` | Red Hat:enterprise_linux:7::client | All versions | 0:10.5.1-13.1.el7_5 | | `pki-base-java` | Red Hat:enterprise_linux:7::client | All versions | 0:10.5.1-13.1.el7_5 | | `pki-ca` | Red Hat:enterprise_linux:7::client | All versions | 0:10.5.1-13.1.el7_5 | | `pki-core` | Red Hat:enterprise_linux:7::client | All versions | 0:10.5.1-13.1.el7_5 | | `pki-core-debuginfo` | Red Hat:enterprise_linux:7::client | All versions | 0:10.5.1-13.1.el7_5 | | `pki-javadoc` | Red Hat:enterprise_linux:7::client | All versions | 0:10.5.1-13.1.el7_5 | | `pki-kra` | Red Hat:enterprise_linux:7::client | All versions | 0:10.5.1-13.1.el7_5 | | `pki-server` | Red Hat:enterprise_linux:7::client | All versions | 0:10.5.1-13.1.el7_5 | | `pki-symkey` | Red Hat:enterprise_linux:7::client | All versions | 0:10.5.1-13.1.el7_5 | | `pki-tools` | Red Hat:enterprise_linux:7::client | All versions | 0:10.5.1-13.1.el7_5 | | `pki-base` | Red Hat:enterprise_linux:7::computenode | All versions | 0:10.5.1-13.1.el7_5 | | `pki-base-java` | Red Hat:enterprise_linux:7::computenode | All versions | 0:10.5.1-13.1.el7_5 | | `pki-ca` | Red Hat:enterprise_linux:7::computenode | All versions | 0:10.5.1-13.1.el7_5 | | `pki-core` | Red Hat:enterprise_linux:7::computenode | All versions | 0:10.5.1-13.1.el7_5 | | `pki-core-debuginfo` | Red Hat:enterprise_linux:7::computenode | All versions | 0:10.5.1-13.1.el7_5 | | `pki-javadoc` | Red Hat:enterprise_linux:7::computenode | All versions | 0:10.5.1-13.1.el7_5 | | `pki-kra` | Red Hat:enterprise_linux:7::computenode | All versions | 0:10.5.1-13.1.el7_5 | | `pki-server` | Red Hat:enterprise_linux:7::computenode | All versions | 0:10.5.1-13.1.el7_5 | | `pki-symkey` | Red Hat:enterprise_linux:7::computenode | All versions | 0:10.5.1-13.1.el7_5 | | `pki-tools` | Red Hat:enterprise_linux:7::computenode | All versions | 0:10.5.1-13.1.el7_5 | | `pki-base` | Red Hat:enterprise_linux:7::server | All versions | 0:10.5.1-13.1.el7_5 | | `pki-base-java` | Red Hat:enterprise_linux:7::server | All versions | 0:10.5.1-13.1.el7_5 | | `pki-ca` | Red Hat:enterprise_linux:7::server | All versions | 0:10.5.1-13.1.el7_5 | | `pki-core` | Red Hat:enterprise_linux:7::server | All versions | 0:10.5.1-13.1.el7_5 | | `pki-core-debuginfo` | Red Hat:enterprise_linux:7::server | All versions | 0:10.5.1-13.1.el7_5 | | `pki-javadoc` | Red Hat:enterprise_linux:7::server | All versions | 0:10.5.1-13.1.el7_5 | | `pki-kra` | Red Hat:enterprise_linux:7::server | All versions | 0:10.5.1-13.1.el7_5 | | `pki-server` | Red Hat:enterprise_linux:7::server | All versions | 0:10.5.1-13.1.el7_5 | | `pki-symkey` | Red Hat:enterprise_linux:7::server | All versions | 0:10.5.1-13.1.el7_5 | | `pki-tools` | Red Hat:enterprise_linux:7::server | All versions | 0:10.5.1-13.1.el7_5 | | `pki-base` | Red Hat:enterprise_linux:7::workstation | All versions | 0:10.5.1-13.1.el7_5 | | `pki-base-java` | Red Hat:enterprise_linux:7::workstation | All versions | 0:10.5.1-13.1.el7_5 | | `pki-ca` | Red Hat:enterprise_linux:7::workstation | All versions | 0:10.5.1-13.1.el7_5 | | `pki-core` | Red Hat:enterprise_linux:7::workstation | All versions | 0:10.5.1-13.1.el7_5 | | `pki-core-debuginfo` | Red Hat:enterprise_linux:7::workstation | All versions | 0:10.5.1-13.1.el7_5 | | `pki-javadoc` | Red Hat:enterprise_linux:7::workstation | All versions | 0:10.5.1-13.1.el7_5 | | `pki-kra` | Red Hat:enterprise_linux:7::workstation | All versions | 0:10.5.1-13.1.el7_5 | | `pki-server` | Red Hat:enterprise_linux:7::workstation | All versions | 0:10.5.1-13.1.el7_5 | | `pki-symkey` | Red Hat:enterprise_linux:7::workstation | All versions | 0:10.5.1-13.1.el7_5 | | `pki-tools` | Red Hat:enterprise_linux:7::workstation | All versions | 0:10.5.1-13.1.el7_5 | Products: Dogtagpki Dogtagpki. ## How do I fix CVE-2018-1080? Apply the vendor's patch. ## Is CVE-2018-1080 being exploited? There is no known exploitation of CVE-2018-1080 in the wild and no public exploit code. ## Other vulnerabilities in [UNKNOWN] pki-core - [CVE-2021-20179](https://insights.sbomify.com/CVE-2021-20179/): Business logic in pki-core (high 8.1) - [CVE-2021-3551](https://insights.sbomify.com/CVE-2021-3551/): Information disclosure in pki-server (high 7.8) - [CVE-2022-2414](https://insights.sbomify.com/CVE-2022-2414/): XML external entity in Dogtag PKI (high 7.5) - [CVE-2020-15720](https://insights.sbomify.com/CVE-2020-15720/): Security feature bypass in n/a (medium 6.8) - [CVE-2020-25715](https://insights.sbomify.com/CVE-2020-25715/): Cross-site scripting in pki-core (medium 6.1) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2018-1080 and fix it if it is affected. What it is: CVE-2018-1080 is a high-severity authentication bypass vulnerability in [UNKNOWN] pki-core, published on 2 Jul 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2018-1080 in the wild and no public exploit code. Affected product: [UNKNOWN] pki-core. 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-2018-1080/ (Markdown: https://insights.sbomify.com/CVE-2018-1080/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2018-1080 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-1080 - OSV: https://osv.dev/vulnerability/CVE-2018-1080 --- From sbomify Insights: https://insights.sbomify.com/CVE-2018-1080/ Summaries are generated and may contain mistakes; the official description above is the record.