# CVE-1999-0069: Solaris ufsrestore buffer overflow.


- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 29 Sep 1999
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-xqg2-r5rv-62x6

## What is CVE-1999-0069?

CVE-1999-0069 is a high-severity vulnerability in Sun Sunos, published on 29 Sep 1999. 

### Official description

Solaris ufsrestore buffer overflow.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Sun Sunos.

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

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

## Is CVE-1999-0069 being exploited?

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

Public exploit code:

- Solaris 7.0 - 'ufsdump' Local Buffer Overflow (1) (exploitdb)
- Solaris 7.0 - 'ufsdump' Local Buffer Overflow (2) (exploitdb)

## Other vulnerabilities in Sun Sunos

- [CVE-2010-4435](https://insights.sbomify.com/CVE-2010-4435/): Memory corruption in n/a (critical 10.0)
- [CVE-2008-4619](https://insights.sbomify.com/CVE-2008-4619/): Denial of service in n/a (critical 10.0)
- [CVE-2008-2144](https://insights.sbomify.com/CVE-2008-2144/): Other in n/a (critical 10.0)
- [CVE-2008-1369](https://insights.sbomify.com/CVE-2008-1369/): Misconfiguration in n/a (critical 10.0)
- [CVE-2001-1583](https://insights.sbomify.com/CVE-2001-1583/): Command injection in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-1999-0069 is a high-severity vulnerability in Sun Sunos, published on 29 Sep 1999. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-1999-0069 exists.

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

## Sources

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

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