CVE-2022-30944
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 · uneditedInsufficiently protected credentials for Intel(R) AMT and Intel(R) Standard Manageability may allow a privileged user to potentially enable information disclosure 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 confidenceThis vulnerability in Intel(R) AMT and Intel(R) Standard Manageability involves insufficiently protected credentials that could allow a privileged user with local access to potentially disclose sensitive information. The issue stems from inadequate protection mechanisms for stored credentials within the AMT firmware, enabling an authenticated local attacker to access credentials they should not have visibility into.
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 dataall versionsall versionsCVSS 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
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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.
-
Check if Intel AMT is enabled in BIOS/UEFIAccess the system BIOS/UEFI settings during boot and look for Intel AMT (Active Management Technology) or Intel vPro settings under security or advanced options. Alternatively, use the 'netsh lan show interfaces' command or check Device Manager for 'Intel(R) Active Management Technology' devices.Affected if Intel AMT is present and enabled in BIOS/UEFI settings
-
Identify Intel AMT firmware version via OSOpen Command Prompt and run: 'netsh lan show interfaces' or check Intel Management Engine Interface (MEI) driver in Device Manager. The firmware version is displayed in the AMT web interface or via Intel SCS (Setup and Configuration Software).Affected if Any Intel AMT firmware version is reported (all versions are affected)
-
Check if Intel Standard Manageability is installedOpen Windows Control Panel > Programs and Features, or check for 'Intel Standard Manageability' in the list of installed software. Also check Device Manager for Intel Standard Manageability components.Affected if Intel Standard Manageability is listed as installed (all versions are affected)
-
Verify local access privileges to AMT interfaceCheck which local user accounts have access to the AMT SOL/IDER/KVM features or web interface. Review user rights on the local system and verify AMT admin accounts configured in Intel AMT.Affected if Any local privileged user account exists on the system with AMT access enabled
If Intel AMT or Intel Standard Manageability is present and enabled on the system, the environment is affected by this vulnerability since all versions contain the insufficient credential protection flaw.
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 dataApply Intel firmware updates for AMT and Standard Manageability when released. Ensure proper access controls and least-privilege principles for systems with AMT enabled, and consider disabling AMT if not required.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-30944 — 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-2022-30944 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