# CVE-2022-47070: Information disclosure in n/a

> An attacker can retrieve the correct password by triggering a double request after entering an incorrect password, exposing sensitive credentials.

- **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:** 3 Feb 2023
- **Updated:** 26 Mar 2025
- **Also known as:** GHSA-6qc3-m7rh-m254

## What is CVE-2022-47070?

CVE-2022-47070 is a high-severity vulnerability in n/a, published on 3 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

NVS365 V01 is vulnerable to Incorrect Access Control. After entering a wrong password, the url will be sent to the server twice. In the second package, the server will return the correct password information.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2022-47070?

It affects 1 product.


Products: Nvs365 Nvs-365-V01 Firmware.

## How do I fix CVE-2022-47070?

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

## Is CVE-2022-47070 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-47071](https://insights.sbomify.com/CVE-2022-47071/): Command injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-47070 and fix it if it is affected.

What it is: CVE-2022-47070 is a high-severity vulnerability in n/a, published on 3 Feb 2023. 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-2022-47070 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-2022-47070/ (Markdown: https://insights.sbomify.com/CVE-2022-47070/index.md)
```

## Sources

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

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