# CVE-2023-4727: Ca: token authentication bypass vulnerability > Attackers can bypass token authentication via LDAP injection to hijack sessions and escalate privileges in Red Hat Certificate System. - **Severity:** High 7.5 (`CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 11 Jun 2024 - **Updated:** 26 Jun 2026 - **Also known as:** ALSA-2024:4165, ALSA-2024:4367, DEBIAN-CVE-2023-4727, GHSA-rvm7-rc5g-c98q, OESA-2025-1238, OESA-2025-1269, OESA-2025-1270, RHSA-2024:4051, RHSA-2024:4070, RHSA-2024:4164, RHSA-2024:4165, RHSA-2024:4179, RHSA-2024:4222, RHSA-2024:4367, RHSA-2024:4403, RHSA-2024:4413, RLSA-2024:4165, RLSA-2024:4367, UBUNTU-CVE-2023-4727 ## What is CVE-2023-4727? CVE-2023-4727 is a high-severity authentication bypass vulnerability in Red Hat Certificate System 10.4 EUS for RHEL-8, published on 11 Jun 2024. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description A flaw was found in dogtag-pki and pki-core. The token authentication scheme can be bypassed with a LDAP injection. By passing the query string parameter sessionID=*, an attacker can authenticate with an existing session saved in the LDAP directory server, which may lead to escalation of privilege. Weakness: CWE-305 (Authentication Bypass by Primary Weakness) ## Which versions are affected by CVE-2023-4727? | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `idm-jss` | AlmaLinux:8 | All versions | 4.11.0-1.module_el8.10.0+3801+17b19a60 | | `idm-jss-javadoc` | AlmaLinux:8 | All versions | 4.11.0-1.module_el8.10.0+3801+17b19a60 | | `idm-ldapjdk` | AlmaLinux:8 | All versions | 4.24.0-1.module_el8.10.0+3801+17b19a60 | | `idm-ldapjdk-javadoc` | AlmaLinux:8 | All versions | 4.24.0-1.module_el8.10.0+3801+17b19a60 | | `idm-pki-acme` | AlmaLinux:8 | All versions | 10.15.1-1.module_el8.10.0+3868+cdab0fd8 | | `idm-pki-base` | AlmaLinux:8 | All versions | 10.15.1-1.module_el8.10.0+3868+cdab0fd8 | | `idm-pki-base-java` | AlmaLinux:8 | All versions | 10.15.1-1.module_el8.10.0+3868+cdab0fd8 | | `idm-pki-ca` | AlmaLinux:8 | All versions | 10.15.1-1.module_el8.10.0+3868+cdab0fd8 | | `idm-pki-kra` | AlmaLinux:8 | All versions | 10.15.1-1.module_el8.10.0+3868+cdab0fd8 | | `idm-pki-server` | AlmaLinux:8 | All versions | 10.15.1-1.module_el8.10.0+3868+cdab0fd8 | | `idm-pki-symkey` | AlmaLinux:8 | All versions | 10.15.1-1.module_el8.10.0+3868+cdab0fd8 | | `idm-pki-tools` | AlmaLinux:8 | All versions | 10.15.1-1.module_el8.10.0+3868+cdab0fd8 | | `idm-tomcatjss` | AlmaLinux:8 | All versions | 7.8.0-1.module_el8.10.0+3801+17b19a60 | | `python3-idm-pki` | AlmaLinux:8 | All versions | 10.15.1-1.module_el8.10.0+3868+cdab0fd8 | | `resteasy` | AlmaLinux:8 | All versions | 3.0.26-7.module_el8.10.0+3808+9d4ab1fb | | `resteasy-javadoc` | AlmaLinux:8 | All versions | 3.0.26-7.module_el8.10.0+3808+9d4ab1fb | | `idm-pki-acme` | AlmaLinux:9 | All versions | 11.5.0-2.el9_4.alma.1 | | `idm-pki-base` | AlmaLinux:9 | All versions | 11.5.0-2.el9_4.alma.1 | | `idm-pki-ca` | AlmaLinux:9 | All versions | 11.5.0-2.el9_4.alma.1 | | `idm-pki-est` | AlmaLinux:9 | All versions | 11.5.0-2.el9_4.alma.1 | | `idm-pki-java` | AlmaLinux:9 | All versions | 11.5.0-2.el9_4.alma.1 | | `idm-pki-kra` | AlmaLinux:9 | All versions | 11.5.0-2.el9_4.alma.1 | | `idm-pki-server` | AlmaLinux:9 | All versions | 11.5.0-2.el9_4.alma.1 | | `idm-pki-tools` | AlmaLinux:9 | All versions | 11.5.0-2.el9_4.alma.1 | | `python3-idm-pki` | AlmaLinux:9 | All versions | 11.5.0-2.el9_4.alma.1 | | `idm-console-framework` | Red Hat:certificate_system_eus:10.4::el8 | All versions | 0:1.3.0-1.module+el8pki+14677+1ef79a68 | | `jss` | Red Hat:certificate_system_eus:10.4::el8 | All versions | 0:4.9.10-1.module+el8pki+21949+4b2d0700 | | `jss-debuginfo` | Red Hat:certificate_system_eus:10.4::el8 | All versions | 0:4.9.10-1.module+el8pki+21949+4b2d0700 | | `jss-debugsource` | Red Hat:certificate_system_eus:10.4::el8 | All versions | 0:4.9.10-1.module+el8pki+21949+4b2d0700 | | `jss-javadoc` | Red Hat:certificate_system_eus:10.4::el8 | All versions | 0:4.9.10-1.module+el8pki+21949+4b2d0700 | | `ldapjdk` | Red Hat:certificate_system_eus:10.4::el8 | All versions | 0:4.23.0-1.module+el8pki+14677+1ef79a68 | | `ldapjdk-javadoc` | Red Hat:certificate_system_eus:10.4::el8 | All versions | 0:4.23.0-1.module+el8pki+14677+1ef79a68 | | `python3-redhat-pki` | Red Hat:certificate_system_eus:10.4::el8 | All versions | 0:10.13.11-1.module+el8pki+21949+4b2d0700 | | `redhat-pki` | Red Hat:certificate_system_eus:10.4::el8 | All versions | 0:10.13.11-1.module+el8pki+21949+4b2d0700 | | `redhat-pki-acme` | Red Hat:certificate_system_eus:10.4::el8 | All versions | 0:10.13.11-1.module+el8pki+21949+4b2d0700 | | `redhat-pki-base` | Red Hat:certificate_system_eus:10.4::el8 | All versions | 0:10.13.11-1.module+el8pki+21949+4b2d0700 | | `redhat-pki-base-java` | Red Hat:certificate_system_eus:10.4::el8 | All versions | 0:10.13.11-1.module+el8pki+21949+4b2d0700 | | `redhat-pki-ca` | Red Hat:certificate_system_eus:10.4::el8 | All versions | 0:10.13.11-1.module+el8pki+21949+4b2d0700 | | `redhat-pki-console` | Red Hat:certificate_system_eus:10.4::el8 | All versions | 0:10.13.11-1.module+el8pki+21949+4b2d0700 | | `redhat-pki-console-theme` | Red Hat:certificate_system_eus:10.4::el8 | All versions | 0:10.13.11-1.module+el8pki+21949+4b2d0700 | ## How do I fix CVE-2023-4727? Apply the vendor's patch. ## Is CVE-2023-4727 being exploited? There is no known exploitation of CVE-2023-4727 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2023-4727 and fix it if it is affected. What it is: CVE-2023-4727 is a high-severity authentication bypass vulnerability in Red Hat Certificate System 10.4 EUS for RHEL-8, published on 11 Jun 2024. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2023-4727 in the wild and no public exploit code. Affected product: Red Hat Certificate System 10.4 EUS for RHEL-8. 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-2023-4727/ (Markdown: https://insights.sbomify.com/CVE-2023-4727/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-4727 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-4727 - OSV: https://osv.dev/vulnerability/CVE-2023-4727 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-4727/ Summaries are generated and may contain mistakes; the official description above is the record.