# CVE-2012-4450: Auth bypass in n/a > Authenticated users can bypass ACL restrictions to access directory entries after a rename operation in 389 Directory Server. - **Severity:** Medium 6.0 (`AV:N/AC:M/Au:S/C:P/I:P/A:P`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 1 Oct 2012 - **Updated:** 6 Aug 2024 - **Also known as:** DEBIAN-CVE-2012-4450, GHSA-hxpc-5pf5-9xxg, RHSA-2013:0503 ## What is CVE-2012-4450? CVE-2012-4450 is a medium-severity authentication bypass vulnerability in n/a, published on 1 Oct 2012. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description 389 Directory Server 1.2.10 does not properly update the ACL when a DN entry is moved by a modrdn operation, which allows remote authenticated users with certain permissions to bypass ACL restrictions and access the DN entry. Weakness: CWE-264 ## Which versions are affected by CVE-2012-4450? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `389-ds-base` | Red Hat:enterprise_linux:6::client | All versions | 0:1.2.11.15-11.el6 | | `389-ds-base-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 0:1.2.11.15-11.el6 | | `389-ds-base-devel` | Red Hat:enterprise_linux:6::client | All versions | 0:1.2.11.15-11.el6 | | `389-ds-base-libs` | Red Hat:enterprise_linux:6::client | All versions | 0:1.2.11.15-11.el6 | | `389-ds-base` | Red Hat:enterprise_linux:6::computenode | All versions | 0:1.2.11.15-11.el6 | | `389-ds-base-debuginfo` | Red Hat:enterprise_linux:6::computenode | All versions | 0:1.2.11.15-11.el6 | | `389-ds-base-devel` | Red Hat:enterprise_linux:6::computenode | All versions | 0:1.2.11.15-11.el6 | | `389-ds-base-libs` | Red Hat:enterprise_linux:6::computenode | All versions | 0:1.2.11.15-11.el6 | | `389-ds-base` | Red Hat:enterprise_linux:6::server | All versions | 0:1.2.11.15-11.el6 | | `389-ds-base-debuginfo` | Red Hat:enterprise_linux:6::server | All versions | 0:1.2.11.15-11.el6 | | `389-ds-base-devel` | Red Hat:enterprise_linux:6::server | All versions | 0:1.2.11.15-11.el6 | | `389-ds-base-libs` | Red Hat:enterprise_linux:6::server | All versions | 0:1.2.11.15-11.el6 | | `389-ds-base` | Red Hat:enterprise_linux:6::workstation | All versions | 0:1.2.11.15-11.el6 | | `389-ds-base-debuginfo` | Red Hat:enterprise_linux:6::workstation | All versions | 0:1.2.11.15-11.el6 | | `389-ds-base-devel` | Red Hat:enterprise_linux:6::workstation | All versions | 0:1.2.11.15-11.el6 | | `389-ds-base-libs` | Red Hat:enterprise_linux:6::workstation | All versions | 0:1.2.11.15-11.el6 | Products: Fedoraproject 389 Directory Server. ## How do I fix CVE-2012-4450? Apply the vendor's patch. ## Is CVE-2012-4450 being exploited? There is no known exploitation of CVE-2012-4450 in the wild and no public exploit code. ## Other vulnerabilities in n/a - [CVE-2017-7551](https://insights.sbomify.com/CVE-2017-7551/): Information disclosure in 389-ds-base (critical 9.8) - [CVE-2017-15135](https://insights.sbomify.com/CVE-2017-15135/): Auth bypass in 389-ds-base (high 8.1) - [CVE-2019-10171](https://insights.sbomify.com/CVE-2019-10171/): Denial of service in 389-ds-base (high 7.5) - [CVE-2018-14638](https://insights.sbomify.com/CVE-2018-14638/): Denial of service in 389-ds-base (high 7.5) - [CVE-2018-1054](https://insights.sbomify.com/CVE-2018-1054/): Denial of service in 389-ds-base (high 7.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2012-4450 and fix it if it is affected. What it is: CVE-2012-4450 is a medium-severity authentication bypass vulnerability in n/a, published on 1 Oct 2012. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2012-4450 in the wild and no public exploit code. Affected product: n/a. 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-2012-4450/ (Markdown: https://insights.sbomify.com/CVE-2012-4450/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2012-4450 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2012-4450 - OSV: https://osv.dev/vulnerability/CVE-2012-4450 --- From sbomify Insights: https://insights.sbomify.com/CVE-2012-4450/ Summaries are generated and may contain mistakes; the official description above is the record.