# CVE-2006-0353: Information disclosure in n/a

> Local users can leak seed file descriptors to obtain sensitive key information or cause denial of service by truncating the seed file.

- **Severity:** Low 3.6 (`AV:L/AC:L/Au:N/C:P/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Jan 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2006-0353, DSA-956-1, GHSA-38h3-wj4x-mm5c

## What is CVE-2006-0353?

CVE-2006-0353 is a low-severity vulnerability in n/a, published on 22 Jan 2006. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

unix_random.c in lshd for lsh 2.0.1 leaks file descriptors related to the randomness generator, which allows local users to cause a denial of service by truncating the seed file, which prevents the server from starting, or obtain sensitive seed information that could be used to crack keys.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2006-0353?

It affects 1 product.


Products: Gnu Lsh.

## How do I fix CVE-2006-0353?

Apply the vendor's patch.

## Is CVE-2006-0353 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2003-0826](https://insights.sbomify.com/CVE-2003-0826/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-0353 and fix it if it is affected.

What it is: CVE-2006-0353 is a low-severity vulnerability in n/a, published on 22 Jan 2006. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-0353 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-2006-0353/ (Markdown: https://insights.sbomify.com/CVE-2006-0353/index.md)
```

## Sources

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

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