# OSV-2020-1741: Heap-use-after-free in zend_assign_to_variable

> A heap-use-after-free vulnerability in the PHP engine's variable assignment logic could allow attackers to execute arbitrary code or cause a denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 13 Sep 2020

## What is OSV-2020-1741?

OSV-2020-1741 is an use after free vulnerability in php, published on 13 Sep 2020. 

### Official description

OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=25601

```
Crash type: Heap-use-after-free READ 1
Crash state:
zend_assign_to_variable
zend_std_write_property
ZEND_ASSIGN_OBJ_SPEC_CV_CONST_OP_DATA_VAR_HANDLER
```

## Which versions are affected by OSV-2020-1741?

1 open source package ship an affected version, including php.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `php` | OSS-Fuzz | All versions | None |

## How do I fix OSV-2020-1741?

No fix has been published for OSV-2020-1741 yet. Limit exposure of the affected software until one is available.

## Is OSV-2020-1741 being exploited?

There is no known exploitation of OSV-2020-1741 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for OSV-2020-1741 and fix it if it is affected.

What it is: OSV-2020-1741 is an use after free vulnerability in php, published on 13 Sep 2020. 
Exploitation: There is no known exploitation of OSV-2020-1741 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-1741/ (Markdown: https://insights.sbomify.com/OSV-2020-1741/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/OSV-2020-1741

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