# CVE-1999-0454: Information disclosure in n/a

> Remote attackers can identify the target operating system by analyzing IP and ICMP packet responses, facilitating targeted attacks.

- **Severity:** Critical 10.0 (`AV:N/AC:L/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:** Not needed
- **Fix available:** No
- **Published:** 4 Feb 2000
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-h9fp-2pjq-92gw

## What is CVE-1999-0454?

CVE-1999-0454 is a critical vulnerability in n/a, published on 4 Feb 2000. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A remote attacker can sometimes identify the operating system of a host based on how it reacts to some IP or ICMP packets, using a tool such as nmap or queso.

## Which versions are affected by CVE-1999-0454?


## How do I fix CVE-1999-0454?

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

## Is CVE-1999-0454 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-1999-0454 and fix it if it is affected.

What it is: CVE-1999-0454 is a critical vulnerability in n/a, published on 4 Feb 2000. 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-1999-0454 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-1999-0454/ (Markdown: https://insights.sbomify.com/CVE-1999-0454/index.md)
```

## Sources

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

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