OSV-2020-1779 Heap-use-after-free in zend_gc_addref
Not scored
Published
Check this codebase for OSV-2020-1779 and fix it if it is affected.
What it is: OSV-2020-1779 is an use after free vulnerability in php, published on 17 Sep 2020.
Exploitation: There is no known exploitation of OSV-2020-1779 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-2020-1779/ (Markdown: https://insights.sbomify.com/OSV-2020-1779/index.md)
A heap-use-after-free in the PHP engine's garbage collection can lead to crashes or potential code execution.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Not stated
- Victim action needed
- Not needed
- Fix
- None listed
What is OSV-2020-1779?
OSV-2020-1779 is an use after free vulnerability in php, published on 17 Sep 2020.
Official description
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=25697
Crash type: Heap-use-after-free READ 4
Crash state:
zend_gc_addref
zend_generator_update_current
zend_generator_dtor_storage
Which versions are affected by OSV-2020-1779?
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-2020-1779?
No fix has been published for OSV-2020-1779 yet. Limit exposure of the affected software until one is available.
Upgrade to the fixed version. These bugs are found with fuzzing and sanitisers and avoided by memory-safe languages. More about Use after free.
Is OSV-2020-1779 being exploited?
There is no known exploitation of OSV-2020-1779 in the wild and no public exploit code.