LiveActive security incident?Get immediate response
CVE Record

CVE-2017-1000376: libffi requests an executable stack allowing attackers to more easily trigger arbitrary code execution by o...

libffi requests an executable stack allowing attackers to more easily trigger arbitrary code execution by overwriting the stack. Please note that libffi is used by a number of other libraries. It was previously stated that this affects libffi version 3.2.1 but this appears to be incorrect. libffi prior to version 3.1 on 32 bit x86 systems was vulnerable, and upstream is believed to have fixed this issue in version 3.1.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

CVE-2017-1000376 is a libffi issue where some vulnerable builds requested an executable stack, weakening a core memory-safety protection. That can make code execution easier if an attacker can overwrite stack memory. The supplied sources limit the affected scope to libffi before 3.1 on 32-bit x86 systems. Most likely exposure is legacy 32-bit x86 systems, old distributions, appliances, containers, or applications bundling libffi before version 3.1. Modern 64-bit systems or vendor-patched packages may not be affected, but package lineage should be verified. Treat this as a focused legacy-risk cleanup item, not a broad emergency based on the supplied evidence. Prioritize environments where old 32-bit x86 software remains in production or where libffi is bundled inside critical applications. Mitigation focus: Inventory systems and applications using libffi, including bundled copies.; Prioritize legacy 32-bit x86 environments for review.; Upgrade to libffi 3.1 or vendor-patched packages where applicable..

Prepared

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-2017-1000376 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.