# CVE-2022-0183: Information disclosure in MIRUPASS

> An attacker with physical access can extract stored passwords from MIRUPASS devices due to missing encryption of sensitive data.

- **Severity:** Medium 4.6 (`CVSS:3.1/AV:P/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jan 2022
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-rpwp-rm9j-p52v

## What is CVE-2022-0183?

CVE-2022-0183 is a medium-severity vulnerability in KING JIM CO.,LTD. MIRUPASS, published on 17 Jan 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Missing encryption of sensitive data vulnerability in 'MIRUPASS' PW10 firmware all versions and 'MIRUPASS' PW20 firmware all versions allows an attacker who can physically access the device to obtain the stored passwords.

Weakness: CWE-311 (Missing Encryption of Sensitive Data)

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

It affects 2 products.


Products: Kingjim Mirupass Pw10 Firmware, Kingjim Mirupass Pw20 Firmware.

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

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

## Is CVE-2022-0183 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-0183 is a medium-severity vulnerability in KING JIM CO.,LTD. MIRUPASS, published on 17 Jan 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-0183 in the wild and no public exploit code.

Affected product: KING JIM CO.,LTD. MIRUPASS. 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-0183/ (Markdown: https://insights.sbomify.com/CVE-2022-0183/index.md)
```

## Sources

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

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