# CVE-2001-1387: Information disclosure in n/a

> A flaw in iptables-save causes incorrect rule recording, leading to unintended network responses and potential information leakage.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Aug 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-2wcp-prmg-9pr7

## What is CVE-2001-1387?

CVE-2001-1387 is a low-severity vulnerability in n/a, published on 31 Aug 2002. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

iptables-save in iptables before 1.2.4 records the "--reject-with icmp-host-prohibited" rule as "--reject-with tcp-reset," which causes iptables to generate different responses than specified by the administrator, possibly leading to an information leak.

Weakness: CWE-203 (Observable Discrepancy)

## Which versions are affected by CVE-2001-1387?

It affects 1 product.


Products: Netfilter Iptables.

## How do I fix CVE-2001-1387?

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

## Is CVE-2001-1387 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-2663](https://insights.sbomify.com/CVE-2012-2663/): Security feature bypass in n/a (high 7.5)
- [CVE-2001-1388](https://insights.sbomify.com/CVE-2001-1388/): Misconfiguration in n/a (medium 5.0)
- [CVE-2019-11360](https://insights.sbomify.com/CVE-2019-11360/): Memory corruption in n/a (medium 4.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2001-1387 and fix it if it is affected.

What it is: CVE-2001-1387 is a low-severity vulnerability in n/a, published on 31 Aug 2002. 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-2001-1387 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-2001-1387/ (Markdown: https://insights.sbomify.com/CVE-2001-1387/index.md)
```

## Sources

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

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