# CVE-2007-1375: Integer overflow in n/a

> An integer overflow in PHP's substr_compare function allows attackers to read sensitive memory via a large length argument.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Mar 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-cqfv-6frg-v5c7

## What is CVE-2007-1375?

CVE-2007-1375 is a medium-severity vulnerability in Php Php, published on 10 Mar 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Integer overflow in the substr_compare function in PHP 5.2.1 and earlier allows context-dependent attackers to read sensitive memory via a large value in the length argument, a different vulnerability than CVE-2006-1991.

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

It affects 1 product.


Products: Php Php.

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

Upgrade to a fixed version.

## Is CVE-2007-1375 being exploited?

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

Public exploit code:

- PHP 5.2.1 - 'substr_compare()' Information Leak (exploitdb)

## 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-1375 and fix it if it is affected.

What it is: CVE-2007-1375 is a medium-severity vulnerability in Php Php, published on 10 Mar 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-1375 exists.

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

## Sources

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

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