CVE-2018-19975

Exp

In YARA 3.8.1, bytecode in a specially crafted compiled rule can read data from any arbitrary address in memory, in libyara/exec.c. Specifically, OP_COUNT can read a DWORD.

Published: 2018-12-17 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2018-19975 is rated High Exploit Risk (61.9/100): CVSS Medium severity, with medium exploitation likelihood (EPSS 1.36%). 3 public exploit reference(s) are indexed (Exploit-DB). EPSS rose +1.10% over the last day, indicating growing attacker interest. Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2018-19975

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗
— nvd_ref exploit_tag Exploit-DB ↗
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2018-19975

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.26% 1.36% +1.10%
2 2026-01-15 0.23% 0.26% +0.03%
3 2025-11-21 — 0.23% —

Full EPSS history (9 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2018-19975

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.5 3.0 MEDIUM
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 1.8 3.6 [email protected]
7.1 2.0 HIGH
AV:N/AC:M/Au:N/C:C/I:N/A:N Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:C)
Complete confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:N)
No availability impact.
 8.6 6.9 [email protected]

Weakness enumeration for CVE-2018-19975

OS Trackers for CVE-2018-19975

vendor priority summary link
debian not yet assigned CVE-2018-19975 not yet assigned priority: Debian including 1 source packages (yara), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2018-19975
ubuntu medium CVE-2018-19975 medium priority: Ubuntu including 1 source packages (yara), 19 status rows across 19 suites (bionic, cosmic, disco, eoan, focal, groovy, hirsute, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): ignored 9, not-affected 6, released 3, DNE 1. https://ubuntu.com/security/CVE-2018-19975

Affected software / configurations for CVE-2018-19975

Vendor Product Version Raw CPE
virustotal yara 3.8.1 cpe:2.3:a:virustotal:yara:3.8.1:*:*:*:*:*:*:*

References for CVE-2018-19975

cvelogic Threat Intelligence