Password disclosure via unencrypted device storage
Published Jan 17, 2022 · Updated Aug 2, 2024
Missing encryption in KING JIM MIRUPASS PW10 and PW20 firmware all versions allows physically proximate attackers to obtain stored passwords. The firmware retains password records in device storage without applying encryption, leaving their contents recoverable from the device. Physical possession is required, and the documented consequence is password disclosure rather than data alteration or service interruption.
Summary
What happened
Missing encryption in KING JIM MIRUPASS PW10 and PW20 firmware all versions allows physically proximate attackers to obtain stored passwords. The firmware retains password records in device storage without applying encryption, leaving their contents recoverable from the device. Physical possession is required, and the documented consequence is password disclosure rather than data alteration or service interruption.
The record
- CVE
- CVE-2022-0183
- Published
- Jan 17, 2022
- Updated
- Aug 2, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-311, T1555.005
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 17, 2022CVE publishedPublication date reported by the CVE source.
- Aug 2, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo