CVE-2024-3130
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedHard-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
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe CoolKit eWeLlink mobile application (versions prior to 5.4.x on Android and iOS) contains hard-coded credentials embedded in the application binary. A local attacker can decompile the app to extract the decryption algorithm and encryption keys, then use these to access sensitive data stored by the application.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- High
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify eWeLlink app version on AndroidOpen device Settings > Apps > eWeLlink (or Apps & notifications > See all apps > eWeLlink). Locate the version number displayed under the app name, or use ADB command: adb shell dumpsys package com.ewelink.nromAffected if Version shown is earlier than 5.4.x (for example, 5.3.x, 5.2.x, etc.)
-
Identify eWeLlink app version on iOSOpen device Settings > General > iPhone Storage > eWeLlink. The version number appears below the app icon, or connect device to computer and view app details in Finder/iTunesAffected if Version shown is earlier than 5.4.x (for example, 5.3.x, 5.2.x, etc.)
-
Confirm application is the genuine CoolKit eWeLlinkVerify the package/bundle identifier matches com.ewelink.nrom (Android) or the official CoolKit eWeLlink app from the App Store. Spoofed apps may have different identifiersAffected if The installed app claims to be eWeLlink but originates from an unofficial source or has a different package identifier
If the installed eWeLlink mobile application version is below 5.4.x on either Android or iOS, the hardcoded credentials vulnerability is present in that environment.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpdate the eWeLlink mobile application to version 5.4.x or later, which should remove the hardcoded credentials. For production systems, consider rotating any credentials or API keys that may have been exposed through this vulnerability.
5.4.x or later for Android and iOS
- 1. Open the app store on your Android device (Google Play Store) or iOS device (Apple App Store)
- 2. Search for "eWeLink" or "CoolKit eWeLlink" smart home application
- 3. If an update is available, tap the update button to install version 5.4.x or later
- 4. Alternatively, uninstall the current version and reinstall the latest version from the app store
- 5. After updating, verify the app launches successfully and functions normally
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-3130 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-3130 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data