ASUS BMC's firmware: buffer overflow - Service configuration-1 function
Noroxi assessment
Priority: Monitor (action score 20/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.8% (FIRST EPSS); higher than 78.3% of all records.
- Anyone who can reach it over the internet can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
The Service configuration-1 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.
- Published
- Apr 6, 2021
- Updated
- Jun 16, 2026
- EPSS
- 1.8% · 78th percentile
- CWE
- CWE-120
Report tools
Action score
20
Monitor
Low priority for now.
- CVSS
- 19 / 40 · 4.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 1.8%
CNA vs NVD score
- NVD
- 4.9
- CNA · twcert
- 4.9
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| asus | asmb9-ikvm firmware | cpe:2.3:o:asus:asmb9-ikvm_firmware |
| asus | asmb9-ikvm | cpe:2.3:h:asus:asmb9-ikvm |
| asus | rs720a-e9-rs24-e firmware | cpe:2.3:o:asus:rs720a-e9-rs24-e_firmware |
| asus | rs720a-e9-rs24-e | cpe:2.3:h:asus:rs720a-e9-rs24-e |
| asus | rs700a-e9-rs4 firmware | cpe:2.3:o:asus:rs700a-e9-rs4_firmware |
| asus | rs700a-e9-rs4 | cpe:2.3:h:asus:rs700a-e9-rs4 |
| asus | rs700-e9-rs4 firmware | cpe:2.3:o:asus:rs700-e9-rs4_firmware |
| asus | rs700-e9-rs4 | cpe:2.3:h:asus:rs700-e9-rs4 |
| asus | esc4000 g4x firmware | cpe:2.3:o:asus:esc4000_g4x_firmware |
| asus | esc4000 g4x | cpe:2.3:h:asus:esc4000_g4x |
| asus | rs700-e9-rs12 firmware | cpe:2.3:o:asus:rs700-e9-rs12_firmware |
| asus | rs700-e9-rs12 | cpe:2.3:h:asus:rs700-e9-rs12 |
and 76 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- asus asmb9-ikvm firmware1.11.12
- asus e700 g4 firmware1.14.1
- asus esc4000 dhd g4 firmware1.13.7
- asus esc4000 g4 firmware1.15.2
- asus esc4000 g4x firmware1.11.6
- asus esc8000 g4 firmware1.15.4
- asus esc8000 g4/10g firmware1.15.4
- asus knpa-u16 firmware1.13.4
- asus pro e800 g4 firmware1.14.2
- asus rs100-e10-pi2 firmware1.13.6
- asus rs300-e10-ps4 firmware1.13.6
- asus rs300-e10-rs4 firmware1.13.6
- asus rs500-e9-ps4 firmware1.15.4
- asus rs500-e9-rs4 firmware1.15.4
- asus rs500-e9-rs4-u firmware1.15.4
- asus rs500a-e10-ps4 firmware1.15.2
- asus rs500a-e10-rs4 firmware1.15.2
- asus rs500a-e9 rs4 u firmware1.14.1
- asus rs500a-e9-ps4 firmware1.14.1
- asus rs500a-e9-rs4 firmware1.14.1
Versions reported by the vendor
Affected version ranges reported by the assigning authority (twcert). Independent of NVD's CPE analysis and usually ahead of it.
ASUS BMC firmware for ASMB9-iKVM
- 1.11.12affected
ASUS BMC firmware for E700 G4
- 1.14.1affected
ASUS BMC firmware for ESC4000 DHD G4
- 1.13.7affected
ASUS BMC firmware for ESC4000 G4
- 1.15.2affected
ASUS BMC firmware for ESC4000 G4X
- 1.11.6affected
ASUS BMC firmware for ESC8000 G4
- 1.15.4affected
ASUS BMC firmware for ESC8000 G4/10G
- 1.15.4affected
ASUS BMC firmware for KNPA-U16
- 1.13.4affected
ASUS BMC firmware for Pro E800 G4
- 1.14.2affected
ASUS BMC firmware for RS100-E10-PI2
- 1.13.6affected
ASUS BMC firmware for RS300-E10-PS4
- 1.13.6affected
ASUS BMC firmware for RS300-E10-RS4
- 1.13.6affected
Same product
asus: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-28209ASUS BMC's firmware: path traversal - Delete video file function20Monitor
- CVE-2021-28208ASUS BMC's firmware: path traversal - Get video file function20Monitor
- CVE-2021-28207ASUS BMC's firmware: path traversal - Get Help file function20Monitor
Published before and after this one in the same product
- ← EarlierCVE-2021-28199Apr 6, 2021 · ASUS BMC's firmware: buffer overflow - Modify user’s information function20Monitor
- ← EarlierCVE-2021-28200Apr 6, 2021 · ASUS BMC's firmware: buffer overflow - CD media configuration function20Monitor
- Later →CVE-2021-28202Apr 6, 2021 · ASUS BMC's firmware: buffer overflow - Service configuration-2 function20Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-21-0295 · Apr 7, 2021(ASUS Cihazlarda Güvenlik Zafiyeti)
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- Administrator privileges are required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-120 · Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Root cause
When data is copied, the source length is not compared with the size of the destination buffer. Excess data overwrites adjacent memory.
The bug in code
The whole CWE-120 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
char buf[256];memcpy(buf, pkt->data, pkt->len);Fixed
char buf[256];if (pkt->len > sizeof(buf)) { return -EINVAL;}memcpy(buf, pkt->data, pkt->len);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Overflow BuffersCAPEC-100likelihood: High · Very High
- Client-side Injection-induced Buffer OverflowCAPEC-14likelihood: Medium · High
- Filter Failure through Buffer OverflowCAPEC-24likelihood: High · High
- MIME ConversionCAPEC-42likelihood: High · High
- Overflow Binary Resource FileCAPEC-44likelihood: High · Very High
- Buffer Overflow via Symbolic LinksCAPEC-45likelihood: High · High
- Overflow Variables and TagsCAPEC-46likelihood: High · High
ATT&CK techniques
—
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.