# CVE-2021-28207: ASUS BMC's firmware: path traversal - Get Help file function

> Remote attackers with admin privileges can exploit a path traversal flaw in the Get Help file function to access arbitrary system files on ASUS BMC devices.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Apr 2021
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-98hm-w38p-p29q

## What is CVE-2021-28207?

CVE-2021-28207 is a medium-severity path traversal vulnerability in ASUS BMC firmware for ASMB9-iKVM, published on 6 Apr 2021. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The specific function in ASUS BMC’s firmware Web management page (Get Help 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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2021-28207?

It affects 44 products.


Products: Asus Asmb9-Ikvm Firmware, Asus E700 G4 Firmware, Asus Esc4000 Dhd G4 Firmware, Asus Esc4000 G4 Firmware, Asus Esc4000 G4x Firmware, Asus Esc8000 G4\/10g Firmware, Asus Esc8000 G4 Firmware, Asus Knpa-U16 Firmware, Asus Pro E800 G4 Firmware, Asus Rs100-E10-Pi2 Firmware, Asus Rs300-E10-Ps4 Firmware, Asus Rs300-E10-Rs4 Firmware, Asus Rs500-E9-Ps4 Firmware, Asus Rs500-E9-Rs4-U Firmware, Asus Rs500-E9-Rs4 Firmware, Asus Rs500a-E10-Ps4 Firmware, Asus Rs500a-E10-Rs4 Firmware, Asus Rs500a-E9-Ps4 Firmware, Asus Rs500a-E9-Rs4 Firmware, Asus Rs500a-E9 Rs4 U Firmware and 24 more.

## How do I fix CVE-2021-28207?

No fix has been published for CVE-2021-28207 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-28207 being exploited?

There is no known exploitation of CVE-2021-28207 in the wild and no public exploit code.

## Other vulnerabilities in ASUS BMC firmware for ASMB9-iKVM

- [CVE-2021-28190](https://insights.sbomify.com/CVE-2021-28190/): ASUS BMC's firmware: buffer overflow - Generate new certificate function (medium 4.9)
- [CVE-2021-28191](https://insights.sbomify.com/CVE-2021-28191/): ASUS BMC's firmware: buffer overflow - Firmware update function (medium 4.9)
- [CVE-2021-28192](https://insights.sbomify.com/CVE-2021-28192/): ASUS BMC's firmware: buffer overflow - Remote video storage function (medium 4.9)
- [CVE-2021-28193](https://insights.sbomify.com/CVE-2021-28193/): ASUS BMC's firmware: buffer overflow - SMTP configuration function (medium 4.9)
- [CVE-2021-28194](https://insights.sbomify.com/CVE-2021-28194/): ASUS BMC's firmware: buffer overflow - Remote image configuration setting (medium 4.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-28207 and fix it if it is affected.

What it is: CVE-2021-28207 is a medium-severity path traversal vulnerability in ASUS BMC firmware for ASMB9-iKVM, published on 6 Apr 2021. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-28207 in the wild and no public exploit code.

Affected product: ASUS BMC firmware for ASMB9-iKVM. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-28207/ (Markdown: https://insights.sbomify.com/CVE-2021-28207/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-28207
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-28207
- OSV: https://osv.dev/vulnerability/CVE-2021-28207

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-28207/
Summaries are generated and may contain mistakes; the official description above is the record.