OSV-2022-238 Segv on unknown address in i_zval_ptr_dtor
Not scored
Published
Check this codebase for OSV-2022-238 and fix it if it is affected.
What it is: OSV-2022-238 is a memory corruption vulnerability in php, published on 12 Mar 2022.
Exploitation: There is no known exploitation of OSV-2022-238 in the wild and no public exploit code.
Affected packages and fixed versions:
- php (OSS-Fuzz): affected all versions; no fix listed
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/OSV-2022-238/ (Markdown: https://insights.sbomify.com/OSV-2022-238/index.md)
A segmentation fault in the PHP engine's internal destructor can cause a denial of service when processing specific inputs.
- Exploited in the wild
- Not known
- Login needed
- Not stated
- Attackable
- Not stated
- Victim action needed
- Not stated
- Fix
- None listed
What is OSV-2022-238?
OSV-2022-238 is a memory corruption vulnerability in php, published on 12 Mar 2022.
Official description
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45429
Crash type: Segv on unknown address
Crash state:
i_zval_ptr_dtor
zend_leave_helper_SPEC
zend_dispatch_try_catch_finally_helper_SPEC
Which versions are affected by OSV-2022-238?
1 open source package ship an affected version, including php.
| Package | Affected | Fixed in |
|---|---|---|
php OSS-Fuzz | All versions | None |
How do I fix OSV-2022-238?
No fix has been published for OSV-2022-238 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 OSV-2022-238 being exploited?
There is no known exploitation of OSV-2022-238 in the wild and no public exploit code.