# CVE-1999-0100: Auth bypass in n/a

> Remote attackers can gain unauthorized access to the AIX innd server via control messages, potentially leading to privilege escalation or code execution.

- **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 stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Sep 1999
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-hhfc-jw69-5ww9

## What is CVE-1999-0100?

CVE-1999-0100 is a critical authentication bypass vulnerability in n/a, published on 29 Sep 1999. It can be exploited over the network, with no action from the victim.

### Official description

Remote access in AIX innd 1.5.1, using control messages.

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

It affects 1 product.


Products: Isc Inn.

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

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

## Is CVE-1999-0100 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2002-0525](https://insights.sbomify.com/CVE-2002-0525/): Memory corruption in n/a (critical 10.0)
- [CVE-1999-0754](https://insights.sbomify.com/CVE-1999-0754/): Privilege escalation in n/a (critical 10.0)
- [CVE-2004-0045](https://insights.sbomify.com/CVE-2004-0045/): Memory corruption in n/a (high 7.5)
- [CVE-1999-0247](https://insights.sbomify.com/CVE-1999-0247/): Memory corruption in n/a (high 7.5)
- [CVE-1999-0705](https://insights.sbomify.com/CVE-1999-0705/): Buffer overflow in INN inews program. (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-1999-0100 is a critical authentication bypass vulnerability in n/a, published on 29 Sep 1999. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-1999-0100 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-0100/ (Markdown: https://insights.sbomify.com/CVE-1999-0100/index.md)
```

## Sources

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

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