CVE-2021-28204
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 · uneditedThe specific function in ASUS BMC’s firmware Web management page (Modify user’s information function) does not filter the specific parameter. As obtaining the administrator permission, remote attackers can launch command injection to execute command arbitrary.
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 confidenceASUS BMC firmware contains a command injection vulnerability in the web management page's 'Modify user's information function'. The parameter handling in this function does not properly filter user input, allowing authenticated administrators (or attackers who have obtained admin credentials) to inject and execute arbitrary operating system commands on the underlying BMC firmware.
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= 1.14.51= 1.14.51= 1.14.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
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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.
-
Identify BMC firmware versionAccess the ASUS BMC web interface and navigate to the 'System Information' or 'Firmware Version' page. Alternatively, use IPMI command: 'ipmitool -I lanplus -H <BMC_IP> -U <admin_user> -P <admin_pass> raw' or check via BMC's REST API endpoint if available.Affected if The installed firmware version matches exactly 1.14.51 (for Z10pr D16 or Asmb8 Ikvm models) or 1.14.2 (for Z10pe D16 Ws model).
-
Confirm the product modelCheck the product model name in the BMC web interface under 'System Information' or via IPMI: 'ipmitool -I lanplus -H <BMC_IP> -U <admin_user> -P <admin_pass> fru print'.Affected if The model is one of: Asus Z10pr D16, Asus Asmb8 Ikvm, or Asus Z10pe D16 Ws.
-
Verify web management interface accessibilityAttempt to reach the BMC web interface via HTTPS/HTTP on the BMC IP address (typically port 443 or 80). Confirm the interface responds with ASUS BMC login page.Affected if The web management interface is exposed and accessible from network locations outside of trusted administrative segments.
-
Check for user management function exposureLog into the BMC web interface and navigate to the 'User Management' or 'Modify User' section where user information can be edited.Affected if The 'Modify user's information function' is accessible and available in the web interface.
You are affected if your ASUS BMC firmware version exactly matches 1.14.51 or 1.14.2 on one of the affected product models (Z10pr D16, Asmb8 Ikvm, or Z10pe D16 Ws) AND the web management interface with user modification features is accessible.
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 the vendor-supplied ASUS BMC firmware patch when available. Until patched, restrict administrative access to the BMC web interface to trusted personnel only and monitor for unauthorized access attempts.
- Consultation4.0 h
- Implementation2.0 h
- Testing3.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,864.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-28204 — 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-2021-28204 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