CVE-2023-52113
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 · uneditedlaunchAnyWhere vulnerability in the ActivityManagerService 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 · moderate confidenceThe vulnerability exists in Android's ActivityManagerService, a core system service that manages activity launching and lifecycle. The 'launchAnyWhere' issue allows an attacker to potentially launch activities without proper authorization or cause a denial of service by affecting system availability.
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= 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
- 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 device firmware versionGo to Settings > About Phone > Version on the device, or run 'getprop ro.build.version.emui' or 'getprop ro.build.version.harmonyos' via ADB shellAffected if The displayed version exactly matches any of these: Emui 11.0.1, 12.0.0, 13.0.0, Harmonyos 2.0.0, 2.1.0, 3.0.0, 3.1.0, or 4.0.0
-
Confirm device is Huawei brandCheck the device manufacturer via Settings > About Phone > Manufacturer, or run 'getprop ro.product.manufacturer' via ADB shellAffected if The device is not a Huawei product running Emui or Harmonyos, the vulnerability does not apply to this CVE
-
Verify ActivityManagerService component presenceCheck system partition for ActivityManagerService by examining /system/framework/ services.jar or running 'dumpsys activity' via ADB shellAffected if The ActivityManagerService component is present and the firmware version matches affected versions, the device may be affected
The device is affected only if it is a Huawei device running exactly Emui 11.0.1, 12.0.0, or 13.0.0, or Harmonyos 2.0.0, 2.1.0, 3.0.0, 3.1.0, or 4.0.0 with the vulnerable ActivityManagerService component present.
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 available Android security patches for the ActivityManagerService component. Review and restrict activity launch intents from untrusted applications.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-52113 — 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-2023-52113 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