# CVE-2011-2500: Auth bypass in n/a

> Remote attackers can bypass NFS export access controls by spoofing DNS records, allowing unauthorized mounting and access to shared filesystems.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Feb 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2011-2500, GHSA-crxh-9828-m763

## What is CVE-2011-2500?

CVE-2011-2500 is a high-severity authentication bypass vulnerability in n/a, published on 15 Feb 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The host_reliable_addrinfo function in support/export/hostname.c in nfs-utils before 1.2.4 does not properly use DNS to verify access to NFS exports, which allows remote attackers to mount filesystems by establishing crafted DNS A and PTR records.

Weakness: CWE-264

## Which versions are affected by CVE-2011-2500?

It affects 1 product.


Products: Linux-Nfs Nfs-Utils.

## How do I fix CVE-2011-2500?

Upgrade to a fixed version.

## Is CVE-2011-2500 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2003-0252](https://insights.sbomify.com/CVE-2003-0252/): Memory corruption in n/a (critical 9.8)
- [CVE-2025-12801](https://insights.sbomify.com/CVE-2025-12801/): Nfs-utils: rpc.mountd in the nfs-utils privilege escalation (medium 6.5)
- [CVE-2019-3689](https://insights.sbomify.com/CVE-2019-3689/): nfs-utils: root-owned files stored in insecure /var/lib/nfs directory (medium 5.1)
- [CVE-2011-1749](https://insights.sbomify.com/CVE-2011-1749/): Denial of service in n/a (low 3.3)
- [CVE-2013-1923](https://insights.sbomify.com/CVE-2013-1923/): Information disclosure in n/a (low 3.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-2500 and fix it if it is affected.

What it is: CVE-2011-2500 is a high-severity authentication bypass vulnerability in n/a, published on 15 Feb 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2011-2500 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-2011-2500/ (Markdown: https://insights.sbomify.com/CVE-2011-2500/index.md)
```

## Sources

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

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