# CVE-2009-0759: Code injection in n/a

> Authenticated users can inject CRLF sequences to modify configuration files and escalate privileges in the ZNC IRC bouncer.

- **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:** Yes
- **Published:** 3 Mar 2009
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2009-0759, DSA-1735-1, GHSA-f594-w3vj-gf5c

## What is CVE-2009-0759?

CVE-2009-0759 is a medium-severity code injection vulnerability in n/a, published on 3 Mar 2009. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Multiple CRLF injection vulnerabilities in webadmin in ZNC before 0.066 allow remote authenticated users to modify the znc.conf configuration file and gain privileges via CRLF sequences in the quit message and other vectors.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2009-0759?

It affects 1 product.


Products: Znc Znc.

## How do I fix CVE-2009-0759?

Upgrade to a fixed version.

## Is CVE-2009-0759 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-12816](https://insights.sbomify.com/CVE-2019-12816/): Privilege escalation in n/a (high 8.8)
- [CVE-2010-2488](https://insights.sbomify.com/CVE-2010-2488/): Null dereference in znc (high 7.5)
- [CVE-2009-2658](https://insights.sbomify.com/CVE-2009-2658/): Path traversal in n/a (high 7.5)
- [CVE-2010-2812](https://insights.sbomify.com/CVE-2010-2812/): Denial of service in n/a (medium 5.0)
- [CVE-2010-2934](https://insights.sbomify.com/CVE-2010-2934/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-0759 and fix it if it is affected.

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

## Sources

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

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