Physical data disclosure via external debug logs
Published Mar 27, 2023 · Updated Feb 19, 2025
Information exposure in Juiker app 4.6.0607.1 for Android allows physically proximate attackers to read partial user data from debug logs. Juiker writes debug logs containing sensitive information, including personal contacts, to mobile external storage such as an SD card. Physical access to the device is required; the documented consequence is limited to disclosure of partial user information.
Summary
What happened
Information exposure in Juiker app 4.6.0607.1 for Android allows physically proximate attackers to read partial user data from debug logs. Juiker writes debug logs containing sensitive information, including personal contacts, to mobile external storage such as an SD card. Physical access to the device is required; the documented consequence is limited to disclosure of partial user information.
The record
- CVE
- CVE-2022-39043
- Published
- Mar 27, 2023
- Updated
- Feb 19, 2025
- Vendor
- LoFTechnology, Inc.
- Product
- Juiker
- Classifications
- CWE-532, CWE-200, CWE-922, T1409
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 27, 2023CVE publishedPublication date reported by the CVE source.
- Feb 19, 2025Record 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.6.0607.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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