# CVE-2025-64304: Hardcoded credentials in "FOD" App for Android

> A local unauthenticated attacker can retrieve hard-coded cryptographic keys from the FOD mobile application, potentially compromising data security.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Nov 2025
- **Updated:** 25 Nov 2025
- **Also known as:** GHSA-rx74-p2rx-rwpq

## What is CVE-2025-64304?

CVE-2025-64304 is a medium-severity vulnerability in Fuji Television Network, Inc. "FOD" App for Android, published on 25 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

"FOD" App uses hard-coded cryptographic keys, which may allow a local unauthenticated attacker to retrieve the cryptographic keys.

Weakness: CWE-321 (Use of Hard-coded Cryptographic Key)

## Which versions are affected by CVE-2025-64304?


## How do I fix CVE-2025-64304?

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

## Is CVE-2025-64304 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-64304 and fix it if it is affected.

What it is: CVE-2025-64304 is a medium-severity vulnerability in Fuji Television Network, Inc. "FOD" App for Android, published on 25 Nov 2025. 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-2025-64304 in the wild and no public exploit code.

Affected product: Fuji Television Network, Inc. "FOD" App for Android. 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-2025-64304/ (Markdown: https://insights.sbomify.com/CVE-2025-64304/index.md)
```

## Sources

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

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