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

> Unauthenticated attackers can download backups to reveal admin hashes, enabling account takeover via password cracking or hash replacement.

- **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:** 20 Jan 2023
- **Updated:** 3 Apr 2025
- **Also known as:** GHSA-jm5w-p8rr-g6mm

## What is CVE-2022-47732?

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

### Official description

In Yeastar N412 and N824 Configuration Panel 42.x and 45.x, an unauthenticated attacker can create backup file and download it, revealing admin hash, allowing, once cracked, to login inside the Configuration Panel, otherwise, replacing the hash in the archive and restoring it on the device which will change admin password granting access to the device.

Weakness: CWE-916 (Use of Password Hash With Insufficient Computational Effort)

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

It affects 2 products.


Products: Yeastar N412 Firmware, Yeastar N824 Firmware.

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

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

## Is CVE-2022-47732 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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