# OSV-2018-170: Heap-use-after-free in yr_re_ast_split_at_chaining_point

> A heap-use-after-free in the YARA rule parser allows attackers to cause crashes or potentially execute code via crafted rules.

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

## What is OSV-2018-170?

OSV-2018-170 is an use after free vulnerability in yara, published on 13 Jan 2021. 

### Official description

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

```
Crash type: Heap-use-after-free READ 4
Crash state:
yr_re_ast_split_at_chaining_point
yr_parser_reduce_string_declaration
yara_yyparse
```

## Which versions are affected by OSV-2018-170?

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


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

## How do I fix OSV-2018-170?

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

## Is OSV-2018-170 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for OSV-2018-170 and fix it if it is affected.

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

## Sources

- OSV: https://osv.dev/vulnerability/OSV-2018-170

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