# CVE-2009-4769: Other in n/a

> Remote attackers can execute arbitrary code via format string vulnerabilities in httpdx's logging function, requiring logging to be enabled.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Apr 2010
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-72h8-x8gh-6pw7

## What is CVE-2009-4769?

CVE-2009-4769 is a critical vulnerability in n/a, published on 20 Apr 2010. It can be exploited over the network, with no action from the victim.

### Official description

Multiple format string vulnerabilities in the tolog function in httpdx 1.4, 1.4.5, 1.4.6, 1.4.6b, and 1.5 allow (1) remote attackers to execute arbitrary code via format string specifiers in a GET request to the HTTP server component when logging is enabled, and allow (2) remote authenticated users to execute arbitrary code via format string specifiers in a PWD command to the FTP server component.

Weakness: CWE-134 (Use of Externally-Controlled Format String)

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

It affects 1 product.


Products: Jasper Httpdx.

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

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

## Is CVE-2009-4769 being exploited?

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

Public exploit code:

- HTTPDX tolog() Function Format String Vulnerability (metasploit)
- HTTPDX tolog() Function Format String Vulnerability (metasploit)
- httpdx - 'tolog()' Format String (Metasploit) (1) (exploitdb)
- httpdx - 'tolog()' Format String (Metasploit) (2) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2009-3711](https://insights.sbomify.com/CVE-2009-3711/): Memory corruption in n/a (critical 10.0)
- [CVE-2009-3663](https://insights.sbomify.com/CVE-2009-3663/): Other in n/a (critical 10.0)
- [CVE-2009-4770](https://insights.sbomify.com/CVE-2009-4770/): Hardcoded credentials in n/a (high 7.5)
- [CVE-2009-4531](https://insights.sbomify.com/CVE-2009-4531/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-4769 is a critical vulnerability in n/a, published on 20 Apr 2010. It can be exploited over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-4769 exists.

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-4769/ (Markdown: https://insights.sbomify.com/CVE-2009-4769/index.md)
```

## Sources

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

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