CVE-2019-19648
No exploitation reported by the sources we read.
- Published2019-12-09
- WeaknessCWE-125
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
In the macho_parse_file functionality in macho/macho.c of YARA 3.11.0, command_size may be inconsistent with the real size. A specially crafted MachO file can cause an out-of-bounds memory access, resulting in Denial of Service (application crash) or potential code execution.
Timeline
dates in UTC- 2019-12-0901:15CVE publishedNVD
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 33.x | = 33 | no fix published | NVD |
| 34.x | = 34 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 3.11 | = 3.11.0 | no fix published | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Distribution builds and vendor advisories
Packages from OSV.dev and products from the vendors' CSAF advisories.
version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.
Packages
- yaraUbuntu:Pro:20.04:LTSall versions · fixed in 3.9.0-1ubuntu0.1~esm1
- yaraDebian:14all versions · no fixed version listed
- yaraDebian:13all versions · no fixed version listed
- yaraDebian:12all versions · no fixed version listed
Vendor advisories
- CVE-2019-19648 Red Hat Product Security
yara: out-of-bounds memory access in macho_parse_file in macho/macho.c
Fix
No fix published by the sources we read yet. NVD record
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof of concept
- PoC-in-GitHubno public repository identifiedread 2026-11-08
- Metasploit modules
- none listed Metasploit Framework
Sources
- NVDCVSS 3.17.8read 2026-10-23
- NVDCVSS 2.06.8read 2026-10-23
- NVDweakness (CWE)CWE-125read 2026-10-23
- FIRST EPSSEPSS score1.5 %2026-11-08
- OSVaffected packages—
- GitHub Advisoriesadvisory—
Identifiers
- EUVD-2019-9258same flawENISA EUVD · LicenseRef-ENISA-legal-notice
- GHSA-7fcj-v5v7-gm5gsame flawGitHub Advisory Database · CC-BY-4.0
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
- Published
- 2019-12-09
- Last Modified
- 2026-06-17
- NVD status
- Modified
- GitHub Advisory
- GHSA-7fcj-v5v7-gm5g
Frequently asked questions
What is CVE-2019-19648?
Is CVE-2019-19648 actively exploited?
What is the CVSS score for CVE-2019-19648?
Running yara? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.
Sources for this record
- CVE Program · CVE Program Terms of Use
- ENISA EU Vulnerability Database · ENISA legal notice §1.2 (reproduction authorised, provided the source is acknowledged)
- FIRST EPSS · EPSS terms of use (free use, attribution requested)
- GitHub Advisory Database · CC-BY-4.0 · GHSA-7fcj-v5v7-gm5g
- NVD · Public domain (17 U.S.C. § 105) for NVD-authored data; third-party content under its own terms
- OSV.dev · Per record, as its publisher states it: each row carries the label in sourceLicense when one is served
- Red Hat Product Security (CSAF and VEX) · CC-BY-4.0