# CVE-2024-3130: Insecure Data Storage leading to sensitive Information disclosure.

> Local attackers can extract hardcoded keys to decrypt stored data, exposing sensitive information in the eWeLink mobile application.

- **Severity:** Medium 5.7 (`CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Apr 2024
- **Updated:** 27 Aug 2025
- **Also known as:** GHSA-7fcw-hqq7-pqmf

## What is CVE-2024-3130?

CVE-2024-3130 is a medium-severity vulnerability in CoolKIt eWeLink APP, published on 1 Apr 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Hard-coded Credentials in CoolKit eWeLlink app are before 5.4.x on Android and IOS allows local attacker to unauthorized access to sensitive data via Decryption algorithm and key obtained after decompiling app

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

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


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

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

## Is CVE-2024-3130 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-3130 is a medium-severity vulnerability in CoolKIt eWeLink APP, published on 1 Apr 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-3130 in the wild and no public exploit code.

Affected product: CoolKIt eWeLink APP. 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-3130/ (Markdown: https://insights.sbomify.com/CVE-2024-3130/index.md)
```

## Sources

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

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