Security readout for executives and security teams
Plain-English summary
This is a low-severity issue reported in LIEF v0.14.1. A local, low-privileged attacker may obtain limited sensitive information through the name parameter in the machd_reader.c component, with user interaction required. The provided sources do not identify broad product exposure or confirmed public exploitation.
Executive priority
Handle through normal vulnerability management. This does not justify emergency response based on the supplied evidence, but teams using LIEF v0.14.1 should verify exposure and follow vendor guidance.
Technical view
The CVE maps to CWE-457 and has CVSS 3.1 score 3.9: local attack vector, low complexity, low privileges, user interaction required, unchanged scope, low confidentiality and integrity impact, and no availability impact. The source bundle names LIEF v0.14.1 and machd_reader.c but lists no CPEs.
Likely exposure
Exposure is most likely limited to environments using LIEF v0.14.1 where local users can trigger the affected component. The CVE record does not identify downstream products, CPEs, or remotely reachable attack paths.
Exploitation context
The CVE is not listed as KEV in the source bundle. The provided sources do not claim active exploitation, exploit availability, or weaponized use. Treat exploitation evidence as incomplete rather than confirmed.
Researcher notes
The evidence is sparse: affected vendor/product fields are n/a, and the CVE description is brief. The CVSS vector indicates constrained local exploitation with user interaction and limited C/I impact. Avoid expanding scope beyond LIEF v0.14.1 unless validated from vendor sources.
Mitigation direction
Check LIEF project guidance and issue 1038 for fixed versions or maintainer recommendations.
Inventory direct and bundled use of LIEF v0.14.1 in build and analysis tooling.
Restrict untrusted local users from invoking workflows that use the affected component.
Prioritize vendor-confirmed upgrades when release notes identify this CVE or issue.
Validation and detection
Confirm whether LIEF v0.14.1 is present in dependencies, containers, or packaged tools.
Review whether local users can supply input reaching the name parameter path.
Track the CVE record and GitHub issue for corrected affected-version details.
Document any compensating controls if no vendor fix is currently identified.
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.
cwe · low confidence lookup
CWE-457: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-457 · source CWE mapping
Use of Uninitialized Variable
Use of Uninitialized Variable represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.