# CVE-1999-0425: talkback in Netscape 4.5 allows a local user to kill an arbitrary process of another user whose Netscape crashes.


- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:N/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 29 Sep 1999
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-7gf5-w5c8-cpr2

## What is CVE-1999-0425?

CVE-1999-0425 is a medium-severity vulnerability in n/a, published on 29 Sep 1999. 

### Official description

talkback in Netscape 4.5 allows a local user to kill an arbitrary process of another user whose Netscape crashes.

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

It affects 1 product.


Products: Netscape Communicator.

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

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

## Is CVE-1999-0425 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2002-2248](https://insights.sbomify.com/CVE-2002-2248/): Buffer overflow in the sun.awt.windows.WDefaultFontCharset Java class implementation in Netscape 4.0 allows remote attackers to execute arbi (critical 10.0)
- [CVE-1999-1189](https://insights.sbomify.com/CVE-1999-1189/): Memory corruption in n/a (high 7.5)
- [CVE-2001-0596](https://insights.sbomify.com/CVE-2001-0596/): Cross-site scripting in n/a (high 7.5)
- [CVE-1999-1357](https://insights.sbomify.com/CVE-1999-1357/): Cross-site scripting in n/a (high 7.5)
- [CVE-2000-1187](https://insights.sbomify.com/CVE-2000-1187/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-1999-0425 is a medium-severity vulnerability in n/a, published on 29 Sep 1999. 
Exploitation: There is no known exploitation of CVE-1999-0425 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-0425/ (Markdown: https://insights.sbomify.com/CVE-1999-0425/index.md)
```

## Sources

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

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