LiveActive security incident?Get immediate response
CVE Record

CVE-2021-28186: ASUS BMC's firmware: buffer overflow - ActiveX configuration-2 acquisition

The specific function in ASUS BMC’s firmware Web management page (ActiveX configuration-2 acquisition) 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

CVE-2021-28186 affects specific ASUS BMC firmware used for server management. A privileged remote user could trigger a buffer overflow in a web management function and crash the BMC web service. The main business risk is loss of management availability, not data theft or system takeover based on the provided sources.

Executive priority

Treat this as a moderate operational resilience issue. It is unlikely to justify emergency response unless affected BMC interfaces are broadly reachable or privileged access is poorly controlled. Prioritize inventory, access restriction, and vendor firmware guidance.

Technical view

The vulnerable ActiveX configuration-2 acquisition function in ASUS BMC firmware does not validate user-supplied string length, creating a CWE-120 buffer overflow. CVSS 3.1 is 4.9: network reachable, low attack complexity, high privileges required, no user interaction, availability impact high, no confidentiality or integrity impact stated.

Likely exposure

Exposure is limited to ASUS BMC firmware for Z10PR-D16 1.14.51, ASMB8-iKVM 1.14.51, and Z10PE-D16 WS 1.14.2. Risk is highest where BMC web management is reachable beyond a tightly controlled management network.

Exploitation context

The bundle does not show CISA KEV listing or evidence of active exploitation. Exploitation requires privileged access to the BMC web management interface, reducing likelihood but making insider, credential compromise, or overexposed management-plane scenarios relevant.

Researcher notes

The record names affected products and versions but does not provide a fixed version, exploit details, or active exploitation evidence. Avoid assuming broader ASUS BMC impact beyond the listed firmware unless vendor guidance confirms it.

Mitigation direction

  • Check ASUS and TWCERT guidance for fixed firmware or official mitigations.
  • Restrict BMC web access to dedicated management networks and trusted administrators.
  • Remove internet exposure for affected BMC management interfaces.
  • Review privileged BMC accounts and disable unnecessary access.
  • Monitor BMC web service crashes or repeated abnormal terminations.

Validation and detection

  • Inventory ASUS BMC models and firmware versions against the affected list.
  • Confirm whether BMC web management is reachable from untrusted networks.
  • Review BMC privileged accounts for stale, shared, or excessive access.
  • Check service logs for unexpected web management crashes.
  • Verify remediation status against current ASUS or TWCERT guidance.
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-28186 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-28186Attack 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.