Security readout for executives and security teams
Plain-English summary
This flaw affects ASUS BMC web management firmware. An attacker who already has administrator access to the BMC interface can abuse a help-file function to read system files through path traversal. The main risk is sensitive information exposure from server management controllers, not direct data modification or outage.
Executive priority
Treat this as a moderate-priority infrastructure exposure issue. It is not described as unauthenticated or actively exploited, but BMC compromise can expose sensitive host-management data. Prioritize systems where BMC access is broadly reachable or admin access is weakly controlled.
Technical view
CVE-2021-28207 is CWE-22 path traversal in the ASUS BMC firmware Get Help file function. The vulnerable function does not filter a specific parameter, allowing a remote administrator-level user to access system files. CVSS 3.1 is 4.9: network reachable, low complexity, high privileges required, confidentiality high, no integrity or availability impact.
Likely exposure
Exposure is limited to organizations running the listed ASUS BMC firmware versions on affected server, workstation, and ASMB9-iKVM products. Risk increases if BMC web management is reachable beyond a tightly controlled management network or if too many users have BMC administrator privileges.
Exploitation context
The source bundle does not show active exploitation, and the CVE is not listed as KEV. Exploitation requires administrator permission on the BMC web management page and network access to that interface. No public exploit status is supported by the provided sources.
Researcher notes
The evidence identifies affected products and exact firmware versions but does not provide patched versions, CPEs, proof-of-concept details, or exploitation telemetry. Validation should focus on asset/version matching, management-plane reachability, and whether ASUS has issued product-specific firmware remediation.
Mitigation direction
- Check ASUS security advisory and support channels for firmware guidance.
- Inventory ASUS BMC assets against the affected product and version list.
- Restrict BMC web management to trusted management networks or VPN access.
- Review BMC administrator accounts and remove unnecessary privileges.
- Monitor BMC access logs for unusual help-file or file-read activity.
Validation and detection
- Confirm whether affected ASUS BMC products and firmware versions are deployed.
- Verify BMC interfaces are not exposed to untrusted networks.
- Review who has administrator access to BMC web management.
- Check vendor guidance for updated firmware or official mitigation instructions.
- Confirm monitoring covers BMC authentication and web management activity.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2021-28207 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 4.9 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N1.23.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.9MediumVector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.asus.com/content/ASUS-Product-Security-Advisory/CVE reference · x_refsource_MISC
- https://www.asus.com/tw/support/callus/CVE reference · x_refsource_MISC
- https://www.twcert.org.tw/tw/cp-132-4577-60153-1.htmlCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.