# CVE-2009-0180: Security feature bypass in n/a

> Remote attackers can bypass intended access restrictions on NFS services due to missing TCP Wrapper support in Fedora build scripts.

- **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:** No
- **Published:** 20 Jan 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-5j3f-hrhw-w856

## What is CVE-2009-0180?

CVE-2009-0180 is a high-severity vulnerability in n/a, published on 20 Jan 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Certain Fedora build scripts for nfs-utils before 1.1.2-9.fc9 on Fedora 9, and before 1.1.4-6.fc10 on Fedora 10, omit TCP Wrapper support, which might allow remote attackers to bypass intended access restrictions, possibly a related issue to CVE-2008-1376.

Weakness: CWE-264

## Which versions are affected by CVE-2009-0180?

It affects 1 product.


Products: Nfs Nfs-Utils.

## How do I fix CVE-2009-0180?

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

## Is CVE-2009-0180 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2004-0946](https://insights.sbomify.com/CVE-2004-0946/): Memory corruption in n/a (critical 10.0)
- [CVE-2008-4552](https://insights.sbomify.com/CVE-2008-4552/): Auth bypass in n/a (high 7.5)
- [CVE-2004-0154](https://insights.sbomify.com/CVE-2004-0154/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-0180 and fix it if it is affected.

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

## Sources

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

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