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

> Attackers with physical access can read sensitive data from the router's NAND flash via the SPI bus due to insecure permissions.

- **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 Mar 2023
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-qc7r-x584-w555

## What is CVE-2022-45552?

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

### Official description

An Insecure Permissions vulnerability in Shenzhen Zhiboton Electronics ZBT WE1626 Router v 21.06.18 allows attackers to obtain sensitive information via SPI bus interface connected to pinout of the NAND flash memory.

Weakness: CWE-276 (Incorrect Default Permissions)

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

It affects 1 product.


Products: Zbt We1626 Firmware.

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

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

## Is CVE-2022-45552 being exploited?

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

## Other vulnerabilities in n/a

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-45552 is a high-severity vulnerability in n/a, published on 3 Mar 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-45552 in the wild and no public exploit code.

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-45552/ (Markdown: https://insights.sbomify.com/CVE-2022-45552/index.md)
```

## Sources

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

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