External-service API key disclosure via embedded credential
Published Jul 14, 2021 · Updated Aug 3, 2024
Hard-coded credentials in Retty App for Android before 4.8.13 and iOS before 4.11.14 allow attackers to obtain an external-service API key. The packaged application data embeds the static key, allowing extraction through offline analysis instead of protecting it outside the client. Access to a copy of an affected mobile app is required; JVN states that application users are not directly affected by the disclosure.
Summary
What happened
Hard-coded credentials in Retty App for Android before 4.8.13 and iOS before 4.11.14 allow attackers to obtain an external-service API key. The packaged application data embeds the static key, allowing extraction through offline analysis instead of protecting it outside the client. Access to a copy of an affected mobile app is required; JVN states that application users are not directly affected by the disclosure.
The record
- CVE
- CVE-2021-20748
- Published
- Jul 14, 2021
- Updated
- Aug 3, 2024
- Vendor
- Retty Inc.
- Product
- Retty
- Classifications
- CWE-798, T1552.001
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 14, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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=Retty App for Android versions prior to 4.8.13 and Retty App for iOS versions prior to 4.11.14
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