# CVE-2012-5484: Security feature bypass in n/a

> Man-in-the-middle attackers can spoof the join procedure in FreeIPA by exploiting improper CA certificate validation, bypassing security controls.

- **Severity:** High 7.9 (`AV:A/AC:M/Au:N/C:C/I:C/A:C`)
- **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:** 27 Jan 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-6rr4-9qrg-g6j5, RHSA-2013:0188, RHSA-2013:0189

## What is CVE-2012-5484?

CVE-2012-5484 is a high-severity vulnerability in n/a, published on 27 Jan 2013. 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

The client in FreeIPA 2.x and 3.x before 3.1.2 does not properly obtain the Certification Authority (CA) certificate from the server, which allows man-in-the-middle attackers to spoof a join procedure via a crafted certificate.

Weakness: CWE-310

## Which versions are affected by CVE-2012-5484?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ipa-client` | Red Hat:enterprise_linux:5::server | All versions | 0:2.1.3-5.el5_9.2 |
| `ipa-client-debuginfo` | Red Hat:enterprise_linux:5::server | All versions | 0:2.1.3-5.el5_9.2 |
| `ipa` | Red Hat:enterprise_linux:6::client | All versions | 0:2.2.0-17.el6_3.1 |
| `ipa-admintools` | Red Hat:enterprise_linux:6::client | All versions | 0:2.2.0-17.el6_3.1 |
| `ipa-client` | Red Hat:enterprise_linux:6::client | All versions | 0:2.2.0-17.el6_3.1 |
| `ipa-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 0:2.2.0-17.el6_3.1 |
| `ipa-python` | Red Hat:enterprise_linux:6::client | All versions | 0:2.2.0-17.el6_3.1 |
| `ipa-server` | Red Hat:enterprise_linux:6::client | All versions | 0:2.2.0-17.el6_3.1 |
| `ipa-server-selinux` | Red Hat:enterprise_linux:6::client | All versions | 0:2.2.0-17.el6_3.1 |
| `ipa` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.2.0-17.el6_3.1 |
| `ipa-admintools` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.2.0-17.el6_3.1 |
| `ipa-client` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.2.0-17.el6_3.1 |
| `ipa-debuginfo` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.2.0-17.el6_3.1 |
| `ipa-python` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.2.0-17.el6_3.1 |
| `ipa-server` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.2.0-17.el6_3.1 |
| `ipa-server-selinux` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.2.0-17.el6_3.1 |
| `ipa` | Red Hat:enterprise_linux:6::server | All versions | 0:2.2.0-17.el6_3.1 |
| `ipa-admintools` | Red Hat:enterprise_linux:6::server | All versions | 0:2.2.0-17.el6_3.1 |
| `ipa-client` | Red Hat:enterprise_linux:6::server | All versions | 0:2.2.0-17.el6_3.1 |
| `ipa-debuginfo` | Red Hat:enterprise_linux:6::server | All versions | 0:2.2.0-17.el6_3.1 |
| `ipa-python` | Red Hat:enterprise_linux:6::server | All versions | 0:2.2.0-17.el6_3.1 |
| `ipa-server` | Red Hat:enterprise_linux:6::server | All versions | 0:2.2.0-17.el6_3.1 |
| `ipa-server-selinux` | Red Hat:enterprise_linux:6::server | All versions | 0:2.2.0-17.el6_3.1 |
| `ipa` | Red Hat:enterprise_linux:6::workstation | All versions | 0:2.2.0-17.el6_3.1 |
| `ipa-admintools` | Red Hat:enterprise_linux:6::workstation | All versions | 0:2.2.0-17.el6_3.1 |
| `ipa-client` | Red Hat:enterprise_linux:6::workstation | All versions | 0:2.2.0-17.el6_3.1 |
| `ipa-debuginfo` | Red Hat:enterprise_linux:6::workstation | All versions | 0:2.2.0-17.el6_3.1 |
| `ipa-python` | Red Hat:enterprise_linux:6::workstation | All versions | 0:2.2.0-17.el6_3.1 |
| `ipa-server` | Red Hat:enterprise_linux:6::workstation | All versions | 0:2.2.0-17.el6_3.1 |
| `ipa-server-selinux` | Red Hat:enterprise_linux:6::workstation | All versions | 0:2.2.0-17.el6_3.1 |

Products: Redhat Freeipa.

## How do I fix CVE-2012-5484?

Upgrade to a fixed version.

## Is CVE-2012-5484 being exploited?

There is no known exploitation of CVE-2012-5484 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2011-3636](https://insights.sbomify.com/CVE-2011-3636/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2013-0336](https://insights.sbomify.com/CVE-2013-0336/): Denial of service in n/a (medium 5.0)
- [CVE-2013-0199](https://insights.sbomify.com/CVE-2013-0199/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-5484 and fix it if it is affected.

What it is: CVE-2012-5484 is a high-severity vulnerability in n/a, published on 27 Jan 2013. 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-2012-5484 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-5484/ (Markdown: https://insights.sbomify.com/CVE-2012-5484/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2012-5484
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2012-5484
- OSV: https://osv.dev/vulnerability/CVE-2012-5484

---
From sbomify Insights: https://insights.sbomify.com/CVE-2012-5484/
Summaries are generated and may contain mistakes; the official description above is the record.
