# CVE-2023-22429: Hardcoded credentials in Wolt Delivery: Food and more

> A local attacker can reverse-engineer the Wolt Delivery mobile app to extract hard-coded API keys, potentially compromising external service access.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Apr 2023
- **Updated:** 11 Feb 2025
- **Also known as:** GHSA-jw33-89vh-mrpp

## What is CVE-2023-22429?

CVE-2023-22429 is a high-severity vulnerability in Wolt Delivery: Food and more, published on 11 Apr 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Android 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.

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2023-22429?

It affects 1 product.


Products: Wolt Wolt Delivery.

## How do I fix CVE-2023-22429?

No fix has been published for CVE-2023-22429 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-22429 being exploited?

There is no known exploitation of CVE-2023-22429 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-22429 and fix it if it is affected.

What it is: CVE-2023-22429 is a high-severity vulnerability in Wolt Delivery: Food and more, published on 11 Apr 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-22429 in the wild and no public exploit code.

Affected product: Wolt Delivery: Food and more. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-22429/ (Markdown: https://insights.sbomify.com/CVE-2023-22429/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-22429
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-22429
- OSV: https://osv.dev/vulnerability/CVE-2023-22429

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-22429/
Summaries are generated and may contain mistakes; the official description above is the record.