External-service API key disclosure via embedded credential
Published Jan 17, 2022 · Updated Aug 2, 2024
Hard-coded credentials in Jimoty App for Android before 3.7.42 allow local users to extract an external-service API key. The application embeds the key in data shipped with the app, so static analysis can recover the credential. Access to an affected application package is sufficient; the key exposed only the external integration, was deactivated, and did not directly affect app users.
Summary
What happened
Hard-coded credentials in Jimoty App for Android before 3.7.42 allow local users to extract an external-service API key. The application embeds the key in data shipped with the app, so static analysis can recover the credential. Access to an affected application package is sufficient; the key exposed only the external integration, was deactivated, and did not directly affect app users.
The record
- CVE
- CVE-2022-0131
- Published
- Jan 17, 2022
- Updated
- Aug 2, 2024
- Vendor
- Jimoty, Inc.
- Product
- Jimoty App for Android
- Classifications
- CWE-798, CAPEC-191, T1552.001
- Attack vector
- local
- 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=versions prior to 3.7.42
What conditions does exploitation require?
What is affected?
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