# CVE-2007-0909: Code injection in n/a

> Attackers can execute arbitrary code via format string vulnerabilities in PHP print functions and odbc_result_all, particularly on 64-bit systems.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 13 Feb 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-57q9-cw6p-2qrg

## What is CVE-2007-0909?

CVE-2007-0909 is a high-severity code injection vulnerability in Php Php, published on 13 Feb 2007. It can be exploited over the network.

### Official description

Multiple format string vulnerabilities in PHP before 5.2.1 might allow attackers to execute arbitrary code via format string specifiers to (1) all of the *print functions on 64-bit systems, and (2) the odbc_result_all function.

## Which versions are affected by CVE-2007-0909?

It affects 2 products.


Products: Php Php, Trustix Secure Linux.

## How do I fix CVE-2007-0909?

Upgrade to a fixed version.

## Is CVE-2007-0909 being exploited?

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

## Other vulnerabilities in Php Php

- [CVE-2012-2688](https://insights.sbomify.com/CVE-2012-2688/): Integer overflow in n/a (critical 10.0)
- [CVE-2012-2376](https://insights.sbomify.com/CVE-2012-2376/): Memory corruption in n/a (critical 10.0)
- [CVE-2011-3268](https://insights.sbomify.com/CVE-2011-3268/): Memory corruption in n/a (critical 10.0)
- [CVE-2009-4143](https://insights.sbomify.com/CVE-2009-4143/): Other in n/a (critical 10.0)
- [CVE-2008-5557](https://insights.sbomify.com/CVE-2008-5557/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-0909 and fix it if it is affected.

What it is: CVE-2007-0909 is a high-severity code injection vulnerability in Php Php, published on 13 Feb 2007. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2007-0909 in the wild and no public exploit code.

Affected product: Php Php. 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-2007-0909/ (Markdown: https://insights.sbomify.com/CVE-2007-0909/index.md)
```

## Sources

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

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