OSV-2020-263 Heap-use-after-free in dotnet_parse_tilde_2
Not scored
Published
Check this codebase for OSV-2020-263 and fix it if it is affected.
What it is: OSV-2020-263 is an use after free vulnerability in yara, published on 30 Jun 2020.
Exploitation: There is no known exploitation of OSV-2020-263 in the wild and no public exploit code.
Affected packages and fixed versions:
- yara (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-263/ (Markdown: https://insights.sbomify.com/OSV-2020-263/index.md)
A heap-use-after-free vulnerability in the dotnet parser allows attackers to cause crashes or potentially execute arbitrary code via crafted input.
- 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-263?
OSV-2020-263 is an use after free vulnerability in yara, published on 30 Jun 2020.
Official description
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=19179
Crash type: Heap-use-after-free READ 2
Crash state:
dotnet_parse_tilde_2
dotnet_parse_tilde
dotnet_parse_com
Which versions are affected by OSV-2020-263?
1 open source package ship an affected version, including yara.
| Package | Affected | Fixed in |
|---|---|---|
yara OSS-Fuzz | All versions | None |
How do I fix OSV-2020-263?
No fix has been published for OSV-2020-263 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-263 being exploited?
There is no known exploitation of OSV-2020-263 in the wild and no public exploit code.