CVE-2003-0860 Memory corruption in n/a
Critical 10.0
Published
Updated
Check this codebase for CVE-2003-0860 and fix it if it is affected.
What it is: CVE-2003-0860 is a critical memory corruption vulnerability in Php Php, published on 15 Oct 2003.
Exploitation: There is no known exploitation of CVE-2003-0860 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-2003-0860/ (Markdown: https://insights.sbomify.com/CVE-2003-0860/index.md)
Buffer overflows in PHP allow attackers to potentially execute arbitrary code or cause denial of service.
- Exploited in the wild
- Not known
- Login needed
- Not stated
- Attackable
- Not stated
- Victim action needed
- Not stated
- Fix
- None listed
What is CVE-2003-0860?
CVE-2003-0860 is a critical memory corruption vulnerability in Php Php, published on 15 Oct 2003.
Official description
Buffer overflows in PHP before 4.3.3 have unknown impact and unknown attack vectors.
Which versions are affected by CVE-2003-0860?
It affects 1 product.
Products include Php Php.
How do I fix CVE-2003-0860?
No fix has been published for CVE-2003-0860 yet. Limit exposure of the affected software until one is available.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is CVE-2003-0860 being exploited?
There is no known exploitation of CVE-2003-0860 in the wild and no public exploit code.
Other vulnerabilities in Php Php
Sources
Also known as GHSA-vgf6-7fxf-q955.