LiveActive security incident?Get immediate response
CVE Record

CVE-2021-28175: ASUS BMC's firmware: buffer overflow - Radius configuration function

The Radius configuration function in ASUS BMC’s firmware Web management page does not verify the string length entered by users, resulting in a Buffer overflow vulnerability. As obtaining the privileged permission, remote attackers use the leakage to abnormally terminate the Web service.

MediumCVSS 4.9Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

ASUS BMC web management firmware has a Radius configuration flaw where overly long user input can overflow a buffer. The cited impact is service disruption, not data theft. Exploitation requires privileged BMC access, so business urgency is highest where management interfaces are reachable beyond tightly controlled admin networks.

Executive priority

Treat this as a moderate operational risk. Prioritize remediation for BMCs exposed outside restricted admin networks or managed by many privileged users, because disruption of BMC web management can affect server administration during incidents.

Technical view

CVE-2021-28175 is a CWE-120 buffer overflow in the Radius configuration function of ASUS BMC firmware web management. CVSS 3.1 is 4.9, AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H. Affected versions listed are Z10PR-D16 1.14.51, ASMB8-iKVM 1.14.51, and Z10PE-D16 WS 1.14.2.

Likely exposure

Exposure is likely limited to environments running the listed ASUS BMC firmware versions, especially where privileged BMC users can access the web management interface over a network.

Exploitation context

The source bundle does not show CISA KEV listing or other evidence of active exploitation. The CVSS vector requires high privileges and no user interaction. Reported impact is abnormal termination of the web service, affecting availability.

Researcher notes

Evidence supports a privileged, network-reachable buffer overflow with availability impact only. The provided sources do not name fixed versions, exploit maturity, or detailed technical root cause beyond missing string-length verification in Radius configuration input handling.

Mitigation direction

  • Inventory ASUS BMC firmware and identify the listed affected products and versions.
  • Check ASUS and TWCERT advisories for supported fixed firmware or vendor-directed remediation.
  • Restrict BMC web management access to dedicated administrative networks.
  • Review and minimize privileged BMC accounts with Radius configuration access.
  • Monitor BMC web service crashes and unexpected management-plane restarts.

Validation and detection

  • Confirm whether any BMCs run Z10PR-D16 1.14.51, ASMB8-iKVM 1.14.51, or Z10PE-D16 WS 1.14.2.
  • Verify BMC web interfaces are not internet-exposed or broadly reachable.
  • Review BMC account permissions for users able to modify Radius settings.
  • Check operational logs for abnormal web service termination events.
  • Document current ASUS guidance and planned firmware remediation status.
Prepared
Confidence
medium
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 · low confidence lookup

CWE-120: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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
cve · low confidence lookup

CVE-2021-28175 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:N/I:N/A:H

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:N/I:N/A:H1.23.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

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

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 Z10PR-D161.14.51Listed
ASUSBMC firmware for ASMB8-iKVM1.14.51Listed
ASUSBMC firmware for Z10PE-D16 WS1.14.2Listed
Weakness

CWE details

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

CWE-120 · source CWE mapping

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.