CVE-2022-28697
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 · uneditedImproper access control in firmware for Intel(R) AMT and Intel(R) Standard Manageability may allow an unauthenticated user to potentially enable escalation of privilege via physical 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 confidenceImproper access control in Intel(R) AMT and Intel(R) Standard Manageability firmware allows an unauthenticated user with physical access to potentially escalate privileges by exploiting insufficient access restrictions in the firmware layer.
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
- Physical
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:P/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check if Intel AMT is present and enabled in the systemOpen Windows Device Manager and look for 'Intel(R) Active Management Technology' under System devices, or check the Intel Management Engine Interface driver status. Alternatively, access the Intel AMT configuration via BIOS/UEFI (press Ctrl+P during boot on supported systems) or use the Intel Management and Security Status application.Affected if Intel AMT hardware and driver are present and enabled in the system
-
Verify Intel Standard Manageability statusCheck for 'Intel Standard Manageability' entries in Windows Device Manager under System devices, or verify through the Intel Management and Security Status tool if available on the system.Affected if Intel Standard Manageability is present and listed as active
-
Confirm firmware version through Intel toolsUse Intel's MEInfo, Intel Management and Security Status, or access the AMT/SM web interface (typically at https://localhost:16992) to retrieve the firmware version information.Affected if A firmware version is reported - note that all versions are affected per the CVE scope
-
Check BIOS/UEFI configuration for AMT settingsEnter the system BIOS or UEFI setup during boot (commonly F2, F12, or Del key) and look for Intel AMT, Intel Standard Manageability, or AMT Configuration settings under advanced or security menus.Affected if Intel AMT or Standard Manageability options are available and configurable in the firmware settings
If Intel AMT or Intel Standard Manageability is present and enabled on the system, the environment is affected by this vulnerability since all versions of these firmware implementations are vulnerable to improper access control.
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 dataUpdate Intel AMT and Standard Manageability firmware to the latest patched version provided by Intel to remediate the improper access control vulnerability.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28697 — 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-28697 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