CVE-2022-48517
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 · uneditedUnauthorized service access vulnerability in the DSoftBus module. Successful exploitation of this vulnerability will affect availability.
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 · low confidenceThis is an unauthorized service access vulnerability in Huawei's DSoftBus module, which is a distributed bus service component. The vulnerability allows attackers to access services they are not authorized to access, resulting in availability impact. The high CVSS score indicates significant risk from network-exploitable unauthorized access.
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= 11.0.1= 12.0.0= 12.0.1= 2.0.0= 2.0.1= 2.1.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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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 the installed operating systemCheck the device system settings under 'About Phone' or use shell command 'getprop ro.build.version.emui' or 'getprop ro.build.version.harmonyos' to determine if the device runs Huawei Emui or HarmonyOSAffected if Device runs Huawei Emui or HarmonyOS
-
Check the exact Emui versionIf running Emui, verify version by going to Settings > About Phone > Version or using 'getprop ro.build.version.emui' in shellAffected if Version is 11.0.1, 12.0.0, or 12.0.1
-
Check the exact HarmonyOS versionIf running HarmonyOS, verify version by going to Settings > About Phone > Version or using 'getprop ro.build.version.harmonyos' in shellAffected if Version is 2.0.0, 2.0.1, or 2.1.0
-
Verify DSoftBus module presenceCheck if the DSoftBus service is present on the device by searching for 'dsoftbus' in system processes via shell command 'ps -A | grep dsoftbus' or checking /system/lib/modules/ for dsoftbus kernel modulesAffected if DSoftBus module is present and running on an affected OS version
Device is affected if it runs Emui 11.0.1, 12.0.0, or 12.0.1, or HarmonyOS 2.0.0, 2.0.1, or 2.1.0, with the DSoftBus module enabled and accessible.
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 dataApply vendor-provided patches for the DSoftBus module when available; implement network segmentation and access controls to limit exposure to the DSoftBus service interfaces.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-48517 — 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-2022-48517 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