CVE-2026-16141: CWE-798 Use of Hard-coded Credentials in OpenBMC phosphor-net-ipmid
OpenBMC's IPMI implementation, phosphor-net-ipmid, contains a logic flaw in which an unauthenticated client can force the RAKP Message 1 handler to return before it overwrites the authentication object's constructor defaults. The IPMI service then accepts a RAKP Message 3 whose HMAC is computed with the constant 20-byte 'userKey' initialized from the string '0penBmc' and an often-predictable 'bmcRandomNum'. Several downstream vendors implement phosphor-net-ipmid as their IPMI stack, such as NVIDIA and H3C.
AI Analysis
Technical Summary
OpenBMC's phosphor-net-ipmid contains a logic flaw where an unauthenticated client can cause the RAKP Message 1 handler to return prematurely before overwriting default authentication constructor values. Consequently, the IPMI service accepts RAKP Message 3 with an HMAC computed using a constant 20-byte 'userKey' derived from the hard-coded string '0penBmc' and a predictable 'bmcRandomNum'. This use of hard-coded credentials (CWE-798) and predictable randomness undermines the authentication mechanism, allowing potential unauthorized access. Multiple downstream vendors implement this IPMI stack, increasing the scope of impact.
Potential Impact
The vulnerability allows unauthenticated attackers to bypass normal authentication by exploiting hard-coded credentials and predictable random numbers in the IPMI authentication process. This can lead to full compromise of the IPMI service, affecting confidentiality, integrity, and availability of the system. The CVSS 3.1 score of 8.1 reflects high impact with network attack vector, high complexity, no privileges required, and no user interaction needed.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or patch links are provided in the available data. Until a patch is available, affected organizations should monitor vendor advisories and consider restricting network access to IPMI interfaces to trusted management networks.
CVE-2026-16141: CWE-798 Use of Hard-coded Credentials in OpenBMC phosphor-net-ipmid
Description
OpenBMC's IPMI implementation, phosphor-net-ipmid, contains a logic flaw in which an unauthenticated client can force the RAKP Message 1 handler to return before it overwrites the authentication object's constructor defaults. The IPMI service then accepts a RAKP Message 3 whose HMAC is computed with the constant 20-byte 'userKey' initialized from the string '0penBmc' and an often-predictable 'bmcRandomNum'. Several downstream vendors implement phosphor-net-ipmid as their IPMI stack, such as NVIDIA and H3C.
CVSS v3.1
Score 8.1high
Affected software
OpenBMC
phosphor-net-ipmid
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
OpenBMC's phosphor-net-ipmid contains a logic flaw where an unauthenticated client can cause the RAKP Message 1 handler to return prematurely before overwriting default authentication constructor values. Consequently, the IPMI service accepts RAKP Message 3 with an HMAC computed using a constant 20-byte 'userKey' derived from the hard-coded string '0penBmc' and a predictable 'bmcRandomNum'. This use of hard-coded credentials (CWE-798) and predictable randomness undermines the authentication mechanism, allowing potential unauthorized access. Multiple downstream vendors implement this IPMI stack, increasing the scope of impact.
Potential Impact
The vulnerability allows unauthenticated attackers to bypass normal authentication by exploiting hard-coded credentials and predictable random numbers in the IPMI authentication process. This can lead to full compromise of the IPMI service, affecting confidentiality, integrity, and availability of the system. The CVSS 3.1 score of 8.1 reflects high impact with network attack vector, high complexity, no privileges required, and no user interaction needed.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or patch links are provided in the available data. Until a patch is available, affected organizations should monitor vendor advisories and consider restricting network access to IPMI interfaces to trusted management networks.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- runZero
- Date Reserved
- 2026-07-17T17:17:25.183Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6aa956ee55bf5e2cf5f0947f
Added to database: 09/15/2026, 14:32:14 UTC
Last enriched: 09/15/2026, 14:46:28 UTC
Last updated: 09/16/2026, 03:05:08 UTC
Views: 12
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.