CVE-2019-0122
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 · uneditedDouble free in Intel(R) SGX SDK for Linux before version 2.2 and Intel(R) SGX SDK for Windows before version 2.1 may allow an authenticated user to potentially enable information disclosure 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 · high confidenceA double-free vulnerability exists in Intel SGX SDK for Linux (before v2.2) and Windows (before v2.1). The flaw allows an authenticated local user to potentially cause information disclosure or denial of service by exploiting improper memory deallocation in the SDK.
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< 2.1< 2.2CVSS 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
- None
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Locate Intel SGX SDK installation on LinuxCheck for SDK directories: /opt/intel/sgxsdk, /usr/local/sgxsdk, or search for 'sgxsdk' using 'find / -name "sgxsdk" -type d 2>/dev/null'. Also check package manager: 'dpkg -l | grep -i sgxsdk' or 'rpm -qa | grep -i sgxsdk'.Affected if The SDK directory or package exists and the version is below 2.2.
-
Locate Intel SGX SDK installation on WindowsCheck default installation paths: C:\Program Files (x86)\Intel\Intel(R) SGX SDK or C:\Program Files\Intel\Intel(R) SGX SDK. Also check Control Panel > Programs and Features for 'Intel SGX SDK' entry.Affected if The SDK is installed and the version is below 2.1.
-
Determine installed SDK version on LinuxIf SDK directory exists, check for version file: 'cat /opt/intel/sgxsdk/version' or 'cat /opt/intel/sgxsdk/version.txt'. Alternatively, check the SDK manifest or README file in the installation directory.Affected if Version displayed is less than 2.2 (e.g., 2.1, 2.0, 1.x).
-
Determine installed SDK version on WindowsOpen the installed SDK folder and locate 'version.txt' or 'Version.ini' file. Right-click on Intel SGX SDK in Programs and Features, select Properties, and view the Version field.Affected if Version displayed is less than 2.1 (e.g., 2.0, 1.9, 1.x).
-
Verify SGX is actually in useConfirm that developed applications or services actually link against and use the Intel SGX SDK by checking for linker dependencies: 'ldd your_sgx_app | grep sgx' on Linux or dependency walker on Windows.Affected if The SDK is installed at a vulnerable version AND applications built with it are actively running or deployed.
A user is affected if Intel SGX SDK is installed at a version below 2.2 on Linux or below 2.1 on Windows, and their environment uses SGX-enabled applications built with that SDK.
Generated from the published advisory. Verify against your own configuration.
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 data2.12.2
Upgrade Intel SGX SDK to version 2.2 (Linux) or 2.1 (Windows) or later to resolve the double-free vulnerability.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-0122 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-0122 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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