# CVE-2010-1862: Information disclosure in n/a

> Attackers can obtain sensitive memory contents via a context-dependent interruption of internal functions in PHP.

- **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 stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 7 May 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-553r-9qxm-9m7h

## What is CVE-2010-1862?

CVE-2010-1862 is a medium-severity vulnerability in Php Php, published on 7 May 2010. 

### Official description

The chunk_split function in PHP 5.2 through 5.2.13 and 5.3 through 5.3.2 allows context-dependent attackers to obtain sensitive information (memory contents) by causing a userspace interruption of an internal function, related to the call time pass by reference feature.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2010-1862?

It affects 1 product.


Products: Php Php.

## How do I fix CVE-2010-1862?

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

## Is CVE-2010-1862 being exploited?

There is no known exploitation of CVE-2010-1862 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-2010-1862 and fix it if it is affected.

What it is: CVE-2010-1862 is a medium-severity vulnerability in Php Php, published on 7 May 2010. 
Exploitation: There is no known exploitation of CVE-2010-1862 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-2010-1862/ (Markdown: https://insights.sbomify.com/CVE-2010-1862/index.md)
```

## Sources

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

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