# CVE-2024-23453: Hardcoded credentials in Android Spoon application

> A local attacker can reverse-engineer the Android Spoon app to extract hard-coded API keys, enabling unauthorized access to associated services.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **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:** 23 Jan 2024
- **Updated:** 4 Jun 2025
- **Also known as:** GHSA-288h-h8hx-vvqm

## What is CVE-2024-23453?

CVE-2024-23453 is a medium-severity vulnerability in Android Spoon application, published on 23 Jan 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Android Spoon application version 7.11.1 to 8.6.0 uses hard-coded credentials, which may allow a local attacker to retrieve the hard-coded API key when the application binary is reverse-engineered. This API key may be used for unexpected access of the associated service.

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

## Which versions are affected by CVE-2024-23453?

It affects 1 product.


Products: Spooncast Spoon.

## How do I fix CVE-2024-23453?

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

## Is CVE-2024-23453 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-23453 and fix it if it is affected.

What it is: CVE-2024-23453 is a medium-severity vulnerability in Android Spoon application, published on 23 Jan 2024. 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-2024-23453 in the wild and no public exploit code.

Affected product: Android Spoon application. 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-2024-23453/ (Markdown: https://insights.sbomify.com/CVE-2024-23453/index.md)
```

## Sources

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

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