# CVE-1999-0705: Buffer overflow in INN inews program.


- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 4 Jan 2000
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-43p9-vj97-wmgv

## What is CVE-1999-0705?

CVE-1999-0705 is a high-severity vulnerability in Redhat Linux, published on 4 Jan 2000. 

### Official description

Buffer overflow in INN inews program.

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

It affects 2 products.


Products: Isc Inn, Redhat Linux.

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

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

## Is CVE-1999-0705 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-1999-0705 exists.

Public exploit code:

- ISC INN 2.2 / RedHat Linux 6.0 - inews Buffer Overflow (exploitdb)

## Other vulnerabilities in Redhat Linux

- [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-1999-0100](https://insights.sbomify.com/CVE-1999-0100/): Auth bypass 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)

## Fix prompt for AI coding agents

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

What it is: CVE-1999-0705 is a high-severity vulnerability in Redhat Linux, published on 4 Jan 2000. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-1999-0705 exists.

Affected product: Redhat Linux. 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-0705/ (Markdown: https://insights.sbomify.com/CVE-1999-0705/index.md)
```

## Sources

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

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