OSV-2018-170
Heap-use-after-free in yr_re_ast_split_at_chaining_point
No scoreFix available
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
What each source reports
OSV No score
Heap-use-after-free in yr_re_ast_split_at_chaining_point
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
- Record
OSV-2018-170- Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
yaraOSS-Fuzz |
Commit ranges | Not evaluated |
Not evaluated means the source gave git commits or a range we can't read, so we can't tell which releases are affected. A fixed version beside it is the source’s own claim.
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
OSV-2018-170 is a vulnerability with no CVSS score yet in yara, published January 13, 2021. No source lists public exploit code. A source reports a fix.