API key disclosure via hard-coded credential
Published Apr 11, 2023 · Updated Feb 11, 2025
Hard-coded credentials in Wolt Delivery 4.27.2 and earlier allow local users to obtain an external-service API key from the Android app. The application binary embeds the key as a static credential, allowing reverse-engineering to recover it without interacting with the external service. Access to a copy of the Android application binary is required, and JVN reports that application users are not directly affected by the key disclosure.
Summary
What happened
Hard-coded credentials in Wolt Delivery 4.27.2 and earlier allow local users to obtain an external-service API key from the Android app. The application binary embeds the key as a static credential, allowing reverse-engineering to recover it without interacting with the external service. Access to a copy of the Android application binary is required, and JVN reports that application users are not directly affected by the key disclosure.
The record
- CVE
- CVE-2023-22429
- Published
- Apr 11, 2023
- Updated
- Feb 11, 2025
- Vendor
- Wolt
- Product
- Wolt Delivery
- Classifications
- CWE-798, T1552.001
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 11, 2023CVE publishedPublication date reported by the CVE source.
- Feb 11, 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=version 4.27.2 and earlier
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