LiveActive security incident?Get immediate response
CVE Record

CVE-2019-19648: In the macho_parse_file functionality in macho/macho.c of YARA 3.11.0, command_size may be inconsistent wit...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

YARA 3.11.0 can crash when inspecting a maliciously malformed Mach-O file. Because YARA is commonly used in security scanning pipelines, the business risk is interruption of analysis services and, per the CVE text, possible code execution. The bundle does not provide a CVSS score or confirmed exploitation.

Executive priority

Treat this as a targeted security tooling reliability risk. It is not KEV-listed and has incomplete scoring data, but vulnerable scanners handling untrusted files could crash and disrupt detection workflows. Prioritize remediation in internet-facing or high-volume analysis pipelines.

Technical view

In macho_parse_file in YARA 3.11.0's macho/macho.c, command_size can be inconsistent with the real size. A crafted Mach-O file can trigger out-of-bounds memory access, causing denial of service or potential code execution. The bundle does not provide CVSS, CWE, CPEs, or exact fixed versions.

Likely exposure

Exposure is most likely where YARA 3.11.0 processes untrusted Mach-O files, such as malware analysis, file-upload scanning, CI security checks, or endpoint/security tooling. The bundle only names YARA 3.11.0, so do not assume other versions without vendor confirmation.

Exploitation context

The CVE is not marked as CISA KEV, and the supplied sources do not claim active exploitation. Exploitation would require a crafted Mach-O file to be parsed by the vulnerable YARA functionality. The public bundle does not include exploit maturity, prerequisites, or proof-of-concept status.

Researcher notes

Key gaps are missing CVSS, CWE, CPE data, and exact fixed-version details in the supplied bundle. The strongest technical signal is the YARA Mach-O parser description. Validate exposure by version and file-processing path rather than broad product assumptions.

Mitigation direction

  • Inventory YARA deployments and identify any running version 3.11.0.
  • Review upstream YARA and Fedora advisories for fixed package guidance.
  • Prioritize updates where YARA parses untrusted Mach-O files.
  • Limit untrusted Mach-O processing until vendor guidance is applied.
  • Monitor vendor channels for exact fixed-version confirmation.

Validation and detection

  • Confirm installed YARA versions across scanning hosts and containers.
  • Identify workflows that parse Mach-O files from external sources.
  • Check package manager history against Fedora or upstream YARA advisories.
  • Verify scanning services remain stable after applying vendor updates.
  • Document any remaining YARA 3.11.0 exceptions and compensating controls.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2019-19648 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.