dbcve.org
Software Guard Extensions SdkPlugin / extension · Intel

CVE-2019-14566

HIGH · 7.8 CVSS v3.1 Published 2019-11-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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
Insufficient input validation in Intel(R) SGX SDK multiple Linux and Windows versions may allow an authenticated user to enable information disclosure, escalation of privilege or denial of service via local access.

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 · moderate confidence

Insufficient input validation in Intel(R) SGX SDK on Linux and Windows allows a local, authenticated user to potentially achieve information disclosure, privilege escalation, or cause denial of service through improper handling of input data within the SGX enclave development environment.

MitigationApply the Intel SGX SDK security update from Intel's security advisories; identify and rebuild any applications using the affected SDK versions to ensure enclave functionality remains intact.

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
Software Guard Extensions SdkPlugin / extension
Affected:= 2.3.100.49777= 2.3.101.50222= 2.4.100.51291= 2.2.100.45311= 2.3.100.46354= 2.4.100.48163= 2.5.100.49891= 2.6.100.51363

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
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/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. Locate Intel SGX SDK installation directory
    On Linux: check /opt/intel/sgxsdk or /usr/local/sgxsdk; on Windows: check C:\Program Files (x86)\Intel\Intel(R) SGX SDK or C:\Program Files\Intel\Intel(R) SGX SDK. Use 'find /opt -name "sgxsdk" 2>/dev/null' on Linux or check registry keys under HKEY_LOCAL_MACHINE\SOFTWARE\Intel\SGX in Windows.
    Affected if The SGX SDK is not found in any standard installation path, meaning the product is likely not installed.
  2. Identify installed SGX SDK version
    Look for a version file or manifest within the SDK directory. Common files include version.txt, sdkVersion, or VERSION in the SDK root. On Linux: 'cat /opt/intel/sgxsdk/version.xml' or similar. On Windows: check the installer log or the file properties of the SDK binary files.
    Affected if The installed version matches any of the following exact versions: 2.3.100.49777, 2.3.101.50222, 2.4.100.51291, 2.2.100.45311, 2.3.100.46354, 2.4.100.48163, 2.5.100.49891, or 2.6.100.51363.
  3. Verify SGX enclave development is in use
    Check for projects or applications that import or link against the SGX SDK libraries. Look for presence of sgx.h headers, link to libsgx_*.so or sgx_*.lib libraries, or check for enclave configuration files (.edl, .config.xml) in development directories. Use 'grep -r "sgx" /path/to/project' or examine build configuration files.
    Affected if Applications are being built or deployed that utilize the SGX SDK enclave development environment, which relies on the vulnerable input validation in the SDK.
  4. Check for running enclave applications
    List running processes and examine any that are associated with SGX enclaves. On Linux: 'ps aux | grep -i sgx' or check /proc/*/maps for sgxsdk libraries. On Windows: check Task Manager or use 'wmic process get name,commandline' to find processes loading sgxsdk.dll.
    Affected if Enclave applications are actively running, indicating the vulnerable SDK code path may be exercised through enclave initialization or communication.

A user is affected if the Intel SGX SDK is installed with any of the specific versions listed (exact matches only) AND the SGX enclave development environment or running enclave applications are present in their environment.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Intel SGX SDK security update from Intel's security advisories; identify and rebuild any applications using the affected SDK versions to ensure enclave functionality remains intact.

Fix this in Software Guard Extensions Sdk Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-14566 — 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-2019-14566 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