# CVE-2024-32238: Information disclosure in n/a

> An attacker can retrieve the router's management password via the login interface, leading to unauthorized administrative access.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Apr 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-w4fx-77wp-mx4j

## What is CVE-2024-32238?

CVE-2024-32238 is a critical vulnerability in n/a, published on 22 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

H3C ER8300G2-X is vulnerable to Incorrect Access Control. The password for the router's management system can be accessed via the management system page login interface.

Weakness: CWE-522 (Insufficiently Protected Credentials)

## Which versions are affected by CVE-2024-32238?


## How do I fix CVE-2024-32238?

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

## Is CVE-2024-32238 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-32238 exists.

Public exploit code:

- H3C ER8300G2-X config download (github_poc): https://github.com/FuBoLuSec/CVE-2024-32238
- H3C ER8300G2-X - Password Disclosure (nuclei): http/cves/2024/CVE-2024-32238.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-32238 and fix it if it is affected.

What it is: CVE-2024-32238 is a critical vulnerability in n/a, published on 22 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-32238 exists.

Affected product: n/a. 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-2024-32238/ (Markdown: https://insights.sbomify.com/CVE-2024-32238/index.md)
```

## Sources

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

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