LiveActive security incident?Get immediate response
CVE Record

CVE-2021-28209: ASUS BMC's firmware: path traversal - Delete video file function

The specific function in ASUS BMC’s firmware Web management page (Delete video file function) does not filter the specific parameter. As obtaining the administrator permission, remote attackers can use the means of path traversal to access system files.

MediumCVSS 4.9Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This vulnerability affects specific ASUS BMC firmware web management pages. An authenticated administrator could abuse a file deletion feature to traverse paths and read system files. The business risk is mainly sensitive information exposure from management controllers, not unauthenticated takeover or service outage based on the supplied sources.

Executive priority

Treat as a controlled but important infrastructure risk. Prioritize systems where BMC interfaces are reachable from broad networks or where administrator credentials may be shared, stale, or exposed. The issue is not documented here as actively exploited, but BMCs can expose sensitive host-management data.

Technical view

CVE-2021-28209 is CWE-22 path traversal in the ASUS BMC firmware Delete video file function. The vulnerable parameter is not filtered. CVSS 3.1 is 4.9: network reachable, low complexity, high privileges required, no user interaction, high confidentiality impact, no integrity or availability impact.

Likely exposure

Exposure is limited to organizations running the listed ASUS BMC firmware versions, including ASMB9-iKVM 1.11.12 and multiple RS, ESC, E700, WS, Z11PA, and KNPA models. Risk increases if BMC web management is reachable beyond a tightly controlled administration network.

Exploitation context

The source bundle does not show CISA KEV listing, public active exploitation, or exploit availability. The CVSS vector requires administrator privileges, so this is most relevant after credential compromise, insider misuse, or excessive administrative access to BMC management pages.

Researcher notes

Evidence is limited to the CVE description, CVSS vector, affected firmware list, and references. Do not assume unauthenticated exploitation or integrity impact. Validation should focus on affected firmware presence, BMC reachability, administrator access paths, and vendor-published firmware or mitigation status.

Mitigation direction

  • Check ASUS security advisory and support channels for firmware updates or vendor mitigations.
  • Restrict BMC web management access to trusted administration networks only.
  • Review and reduce BMC administrator accounts to the minimum required set.
  • Rotate or reset BMC administrator credentials if compromise is suspected.
  • Monitor BMC administrative activity for unusual file access or video-delete actions.

Validation and detection

  • Inventory ASUS systems and match BMC firmware versions against the affected list.
  • Confirm whether BMC web management is externally reachable or broadly reachable internally.
  • Verify which users have administrator permission on affected BMC interfaces.
  • Check ASUS guidance for patched firmware applicability to each affected model.
  • Review available BMC logs for unexpected administrative file-management activity.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · medium confidence lookup

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 lookup
description · low confidence lookup

File 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 lookup
cve · low confidence lookup

CVE-2021-28209 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
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

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
4.9CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N1.23.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.9Medium
CVSS 3.1 vector shape for CVE-2021-28209Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
ASUSBMC firmware for ASMB9-iKVM1.11.12Listed
ASUSBMC firmware for RS720A-E9-RS24-E1.10.3Listed
ASUSBMC firmware for RS700A-E9-RS41.10.0Listed
ASUSBMC firmware for RS700-E9-RS41.09Listed
ASUSBMC firmware for ESC4000 G4X1.11.6Listed
ASUSBMC firmware for RS700-E9-RS121.11.5Listed
ASUSBMC firmware for RS100-E10-PI21.13.6Listed
ASUSBMC firmware for RS300-E10-PS41.13.6Listed
ASUSBMC firmware for RS300-E10-RS41.13.6Listed
ASUSBMC firmware for RS500A-E9-PS41.14.1Listed
ASUSBMC firmware for RS500A-E9-RS41.14.1Listed
ASUSBMC firmware for RS500A-E9 RS41.14.1Listed
ASUSBMC firmware for E700 G41.14.1Listed
ASUSBMC firmware for WS C422 PRO/SE1.14.1Listed
ASUSBMC firmware for WS X299 PRO/SE1.14.1Listed
ASUSBMC firmware for Z11PA-U121.15.1Listed
ASUSBMC firmware for Z11PA-U12/10G-2S1.15.1Listed
ASUSBMC firmware for KNPA-U161.13.4Listed
ASUSBMC firmware for ESC4000 DHD G41.13.7Listed
ASUSBMC firmware for ESC4000 G41.15.2Listed
ASUSBMC firmware for RS720Q-E9-RS24-S1.15.0Listed
ASUSBMC firmware for RS720Q-E9-RS81.15.0Listed
ASUSBMC firmware for RS720Q-E9-RS8-S1.15.0Listed
ASUSBMC firmware for Z11PA-D81.14.1Listed
ASUSBMC firmware for Z11PA-D8C1.14.1Listed
ASUSBMC firmware for RS720-E9-RS24-U1.14.3Listed
ASUSBMC firmware for RS720-E9-RS8-G1.15.2Listed
ASUSBMC firmware for RS500-E9-PS41.15.4Listed
ASUSBMC firmware for Pro E800 G41.14.2Listed
ASUSBMC firmware for RS500-E9-RS41.15.4Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-22 · source CWE mapping

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.