dbcve.org
Enterprise Virtualization ServerApplication · Redhat

CVE-2017-1000376

HIGH · 7.0 CVSS v3.1 Published 2017-06-19
Fix available
A fix is available. Upgrade to 3.2 or later.
See remediation →
72/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

libffi prior to version 3.1 on 32-bit x86 systems requests an executable stack, allowing attackers to more easily achieve arbitrary code execution by overwriting stack memory. This is a memory protection bypass that lowers the bar for exploitation of stack-based vulnerabilities.

MitigationUpgrade libffi to version 3.1 or later on affected 32-bit x86 systems. Verify and rebuild any dependent libraries or applications that statically link against libffi.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Enterprise Virtualization ServerApplication
Affected:all versions
OpenshiftApplication
Affected:= 2.0
Enterprise LinuxOperating system
Affected:= 6.0= 7.0
Debian LinuxOperating system
Affected:= 8.0= 9.0
LibffiApplication
Affected:< 3.2
PeopletoolsApplication
Affected:= 8.56= 8.57

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify system is 32-bit x86 architecture
    Run 'uname -m' or 'arch' command. On 64-bit systems (x86_64), this vulnerability does not apply even if libffi is older.
    Affected if System architecture is i386, i686, or other 32-bit x86 variants.
  2. Check if libffi library is installed
    Run 'ldconfig -p | grep ffi' or 'dpkg -l | grep libffi' (Debian) or 'rpm -qa | grep libffi' (RHEL). Also check for libffi.so files in /usr/lib or /usr/lib32.
    Affected if libffi library is present on a 32-bit x86 system.
  3. Determine installed libffi version
    Run 'pkg-config --modversion libffi' or check the library file directly with 'ls -la /usr/lib*/libffi*'. Compare the version to the affected range (all versions prior to 3.1 on 32-bit x86, or specifically < 3.2 for libffi project).
    Affected if Installed version is less than 3.1 (or less than 3.2 for libffi project).
  4. Check if dependent applications statically link libffi
    Review application dependencies using 'ldd <application>' or check build manifests for static linking of libffi. This matters because dynamically linked libffi can be patched system-wide.
    Affected if Applications or libraries statically link a vulnerable libffi version.

A system is affected if it is a 32-bit x86 architecture running libffi version 3.0.x or earlier, or any version prior to 3.2 from the Libffi Project, that is either dynamically linked or statically embedded in dependent applications.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 3.2 or later
Fixed in 3.2
Interim mitigation

Upgrade libffi to version 3.1 or later on affected 32-bit x86 systems. Verify and rebuild any dependent libraries or applications that statically link against libffi.

Fix this in Enterprise Virtualization Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-1000376 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-1000376 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data