# CVE-2024-25731: Hardcoded credentials in n/a

> Attackers can extract hardcoded AES keys from the Android camera app binary to decrypt observed network traffic, compromising data confidentiality.

- **Severity:** High 7.5 (`CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 4 Mar 2024
- **Updated:** 26 Mar 2025
- **Also known as:** GHSA-3f2h-fqxh-v4qv

## What is CVE-2024-25731?

CVE-2024-25731 is a high-severity vulnerability in n/a, published on 4 Mar 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Elink Smart eSmartCam (com.cn.dq.ipc) application 2.1.5 for Android contains hardcoded AES encryption keys that can be extracted from a binary file. Thus, encryption can be defeated by an attacker who can observe packet data (e.g., over Wi-Fi).

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

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

It affects 1 product.


Products: Elinksmart Esmartcam.

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

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

## Is CVE-2024-25731 being exploited?

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

Public exploit code:

- CVE-2024-25731 (github_poc): https://github.com/actuator/com.cn.dq.ipc

## Fix prompt for AI coding agents

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

What it is: CVE-2024-25731 is a high-severity vulnerability in n/a, published on 4 Mar 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-25731 in the wild and no public exploit code.

Affected product: n/a. 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-25731/ (Markdown: https://insights.sbomify.com/CVE-2024-25731/index.md)
```

## Sources

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

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