# CVE-2013-0199: Information disclosure in n/a

> Remote attackers can obtain Cross-Realm Kerberos Trust keys due to insufficient LDAP access controls in FreeIPA.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 May 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-3gwj-28p7-3v2r

## What is CVE-2013-0199?

CVE-2013-0199 is a medium-severity vulnerability in n/a, published on 29 May 2014. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The default LDAP ACIs in FreeIPA 3.0 before 3.1.2 do not restrict access to the (1) ipaNTTrustAuthIncoming and (2) ipaNTTrustAuthOutgoing attributes, which allow remote attackers to obtain the Cross-Realm Kerberos Trust key via unspecified vectors.

Weakness: CWE-264

## Which versions are affected by CVE-2013-0199?

It affects 1 product.


Products: Redhat Freeipa.

## How do I fix CVE-2013-0199?

No fix has been published for CVE-2013-0199 yet. Limit exposure of the affected software until one is available.

## Is CVE-2013-0199 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-5484](https://insights.sbomify.com/CVE-2012-5484/): Security feature bypass in n/a (high 7.9)
- [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)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-0199 and fix it if it is affected.

What it is: CVE-2013-0199 is a medium-severity vulnerability in n/a, published on 29 May 2014. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-0199 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-2013-0199/ (Markdown: https://insights.sbomify.com/CVE-2013-0199/index.md)
```

## Sources

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

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