CVE-2017-8929 json
The sized_string_cmp function in libyara/sizedstr.c in YARA 3.5.0 allows remote attackers to cause a denial of service (use-after-free and…
published 2017-05-14 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-17869
- cvss
- 7.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.8%
- EPSS 1.8% chance of exploitation in 30 days, percentile 78%
- public exploits
- 0
- none known
Summary
The sized_string_cmp function in libyara/sizedstr.c in YARA 3.5.0 allows remote attackers to cause a denial of service (use-after-free and application crash) via a crafted rule.
Patch / fix
- yara Debian 14, Debian 13, Debian 12 3.6.0+dfsg-1
debian advisories DEBIAN-CVE-2017-8929
- yara Ubuntu Pro 16.04 LTS 3.4.0+dfsg-2ubuntu0.1~esm1
ubuntu advisories UBUNTU-CVE-2017-8929
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2017-8929 updated cvss 3.3
yara: Use-after-free in sized_string_cmp function
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
1.81% chance of exploitation in the next 30 days, higher than 78% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:N/A:P |
Classification
- Weakness
-
- CWE-416 Use After Free
References
-
github.com
/VirusTotal/yara/commit/053e67e3ec81cc9268ce30eaf0d6663d8639ed1e
patch
-
github.com
/VirusTotal/yara/issues/658
issue-tracking, patch
Sources
- CVE List CVE-2017-8929
- NVD CVE-2017-8929
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.