CVE-2022-26872
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 · uneditedAMI Megarac Password reset interception via API
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 is an authentication bypass vulnerability in AMI MegaRAC Baseboard Management Controller (BMC) firmware that allows attackers to intercept or manipulate password reset operations via the API. The vulnerability enables unauthorized password resets leading to full administrative access to the BMC, which manages server hardware remotely.
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= 12= 13CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Identify if the system uses AMI MegaRAC BMCCheck the BMC web interface login page for 'MegaRAC' branding, or use IPMI command 'ipmitool -I lanplus -H <BMC_IP> -U admin raw' to query BMC information, or examine system documentation for BMC firmware vendor detailsAffected if The system uses AMI MegaRAC firmware for baseboard management controller
-
Check MegaRAC firmware versionAccess BMC web interface and navigate to Settings > Firmware Information, or use IPMI command 'ipmitool -I lanplus -H <BMC_IP> -U admin -P <password> raw 06 01' to retrieve firmware versionAffected if The installed firmware version is 12.x or 13.x
-
Verify remote management interface is network-accessibleCheck if BMC management ports (HTTP 80, HTTPS 443, IPMI 623) are listening and accessible from network segments, using 'nmap -p 80,443,623 <BMC_IP>' or checking firewall rulesAffected if BMC remote management ports are exposed to untrusted networks
-
Confirm password reset API endpoint is accessibleTest access to BMC API endpoints for password reset functionality, typically at /api/session or /api/user endpoints, by sending HTTP requests to the BMC IPAffected if Password reset API endpoints respond without authentication
A system is affected if it runs AMI MegaRAC BMC firmware versions 12 or 13 and has remote management interfaces network-accessible, allowing unauthorized password reset attacks via the API.
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 vendor-supplied firmware patches for MegaRAC BMC, restrict network access to management interfaces using firewall rules or out-of-band networks, and disable unused remote management protocols.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-26872 — 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-26872 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