# CVE-2005-4147: Information disclosure in n/a

> Remote attackers can obtain source code for arbitrary TCL files in Lyris ListManager via null byte injection and potential authentication bypass.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Dec 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-p5xr-f67h-9rw9

## What is CVE-2005-4147?

CVE-2005-4147 is a medium-severity vulnerability in n/a, published on 10 Dec 2005. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The TCLHTTPd service in Lyris ListManager before 8.9b allows remote attackers to obtain source code for arbitrary .tml (TCL) files via (1) a request with a trailing null byte (%00), which might also require (2) an authentication bypass step that involves a username with a trailing "@" characters.

## Which versions are affected by CVE-2005-4147?

It affects 1 product.


Products: Lyris Technologies Inc Listmanager.

## How do I fix CVE-2005-4147?

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

## Is CVE-2005-4147 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-4142](https://insights.sbomify.com/CVE-2005-4142/): Command injection in n/a (high 7.5)
- [CVE-2005-4145](https://insights.sbomify.com/CVE-2005-4145/): Hardcoded credentials in n/a (medium 6.5)
- [CVE-2005-4146](https://insights.sbomify.com/CVE-2005-4146/): Information disclosure in n/a (medium 5.0)
- [CVE-2005-4148](https://insights.sbomify.com/CVE-2005-4148/): Information disclosure in n/a (medium 5.0)
- [CVE-2005-4149](https://insights.sbomify.com/CVE-2005-4149/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-4147 and fix it if it is affected.

What it is: CVE-2005-4147 is a medium-severity vulnerability in n/a, published on 10 Dec 2005. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-4147 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-2005-4147/ (Markdown: https://insights.sbomify.com/CVE-2005-4147/index.md)
```

## Sources

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

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