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

> A remote attacker can obtain sensitive information via the password parameter on the admin password change page of Netis routers.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Jan 2025
- **Updated:** 7 Jan 2025
- **Also known as:** GHSA-2wgj-4jrq-2g66

## What is CVE-2024-48456?

CVE-2024-48456 is a high-severity vulnerability in n/a, published on 6 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue in Netis Wifi6 Router NX10 2.0.1.3643 and 2.0.1.3582 and Netis Wifi 11AC Router NC65 3.0.0.3749 and Netis Wifi 11AC Router NC63 3.0.0.3327 and 3.0.0.3503 and Netis Wifi 11AC Router NC21 3.0.0.3800, 3.0.0.3500 and 3.0.0.3329 and Netis Wifi Router MW5360 1.0.1.3442 and 1.0.1.3031 allows a remote attacker to obtain sensitive information via the parameter password at the change admin password page at the router web interface.

Weakness: CWE-125 (Out-of-bounds Read)

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


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

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

## Is CVE-2024-48456 being exploited?

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

Public exploit code:

- Netis Router Exploit Chain Reactor (CVE-2024-48455, CVE-2024-48456 and CVE-2024-48457). (metasploit)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-48456 is a high-severity vulnerability in n/a, published on 6 Jan 2025. 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-48456 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-48456/ (Markdown: https://insights.sbomify.com/CVE-2024-48456/index.md)
```

## Sources

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

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