CVE-2024-30417
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 · uneditedPath traversal vulnerability in the Bluetooth-based sharing module. Impact: Successful exploitation of this vulnerability may affect service confidentiality.
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 · moderate confidenceA path traversal vulnerability exists in the Bluetooth-based sharing module that allows attackers to manipulate file paths using directory traversal sequences (e.g., ../). Successful exploitation enables unauthorized access to files and directories outside the intended sharing boundary, compromising service confidentiality.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 12.0.0= 13.0.0= 2.0.0= 2.1.0= 3.0.0= 3.1.0= 4.0.0CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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.
-
Check your Huawei EMUI or HarmonyOS versionGo to Settings > About Phone > Version on your Huawei device to find the installed OS versionAffected if The version shown is exactly 12.0.0 or 13.0.0 for EMUI, or 2.0.0, 2.1.0, 3.0.0, 3.1.0, or 4.0.0 for HarmonyOS
-
Verify Bluetooth sharing module is in useCheck if Bluetooth is enabled and whether you have used or received files via Bluetooth sharing (Settings > Bluetooth > Received Files, or look for Bluetooth sharing app activity)Affected if Bluetooth is enabled and the Bluetooth sharing feature has been used recently, creating an attack surface
-
Review file access logs for suspicious path patternsCheck system logs or Bluetooth sharing history for entries containing '../' or unusual directory traversal patterns in file paths
-
Inspect Bluetooth sharing storage directoryExamine the default Bluetooth receive folder (typically /sdcard/Bluetooth/ or /storage/emulated/0/Bluetooth/) for any files with unexpected path references in their metadata or for files located outside this expected directoryAffected if Files appear in unexpected locations or the folder contains malformed filenames with '../' sequences
You are affected if your device runs EMUI 12.0.0/13.0.0 or HarmonyOS 2.0.0/2.1.0/3.0.0/3.1.0/4.0.0 and you have used Bluetooth file sharing, with path traversal indicators present in logs or unexpected files in the system.
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.
From vendor dataImplement strict input validation with canonicalization for all file path inputs in the Bluetooth sharing module, ensuring paths are normalized and validated against an allowlist of permitted directories.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-30417 — 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-30417 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