CVE-2023-22429
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAndroid App 'Wolt Delivery: Food and more' version 4.27.2 and earlier uses hard-coded credentials (API key for an external service), which may allow a local attacker to obtain the hard-coded API key via reverse-engineering the application binary.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Wolt Delivery Android app versions 4.27.2 and earlier contains a hard-coded API key embedded in the application binary. A local attacker can extract this API key through reverse-engineering of the APK, potentially gaining unauthorized access to the external service.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 4.28.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if Wolt Delivery app is installedOn the Android device, go to Settings > Apps > Wolt Delivery, or use the command 'adb shell pm list packages | grep wolt' to list installed packagesAffected if The Wolt Delivery app package is present on the device
-
Determine the installed app versionOn the device, go to Settings > Apps > Wolt Delivery > App info to view the version number, or use 'adb shell dumpsys package com.wolt.delivery | grep versionName'Affected if The version displayed is 4.27.2 or earlier, or any version below 4.28.0
-
Extract and inspect the APK for embedded secretsPull the APK from the device using 'adb shell pm path com.wolt.delivery' then 'adb pull <path>', then use a reverse engineering tool such as apktool, jadx, or strings command to decompile and search the binary for API keys, authentication tokens, or hardcoded credential stringsAffected if The APK binary contains hardcoded API keys, authentication tokens, or other secrets embedded in the code or resources
If the Wolt Delivery app version is below 4.28.0 and contains a hardcoded API key in the APK binary, the environment is affected by this vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped4.28.0
Remove the hardcoded API key from the application code and implement proper credential management, such as storing secrets on a secure backend server and using authenticated API calls, or implementing OAuth/token-based authentication. The compromised API key should be rotated immediately.
4.28.0 or later
- 1. Open the Google Play Store app on the Android device
- 2. Search for 'Wolt Delivery: Food and more'
- 3. Tap 'Update' to install version 4.28.0 or later
- 4. Alternatively, enable automatic app updates in Play Store settings to ensure future security updates are applied automatically
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-22429 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-22429 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data