CVE-2023-39386
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 · uneditedVulnerability of input parameters being not strictly verified in the PMS module. Successful exploitation of this vulnerability may cause newly installed apps to fail to restart.
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 confidenceThis is an input validation vulnerability in a PMS (Package Management System) module where input parameters are not strictly verified. Successful exploitation allows an attacker to cause newly installed applications to fail to restart, likely by providing malformed or unexpected input during the installation process that corrupts the app's startup configuration.
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= 3.0.0= 3.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 OS versionCheck the device settings or system information to determine if the OS is Huawei Emui or Harmonyos, and note the exact version numberAffected if The OS is Emui 12.0.0, Emui 13.0.0, Harmonyos 3.0.0, or Harmonyos 3.1.0
-
Compare your version to affected rangesVerify the exact version matches one of the affected versions: Emui = 12.0.0 or = 13.0.0; Harmonyos = 3.0.0 or = 3.1.0Affected if The installed version exactly matches one of the four listed versions (not a range, but the specific versions)
-
Identify PMS module usageCheck if the Package Management System module is actively used for app installations - this is typically a core system component on these OS versionsAffected if The PMS module processes installation requests (this is default behavior on affected versions)
-
Monitor for app restart failuresAfter installing a new application, observe whether it fails to restart or shows errors in startup configuration - check system logs for installation-related errorsAffected if Newly installed applications fail to restart or show corrupted startup configuration after installation
You are affected if your device runs Emui 12.0.0, Emui 13.0.0, Harmonyos 3.0.0, or Harmonyos 3.1.0 and you observe newly installed apps failing to restart due to corrupted startup configuration.
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 and sanitization for all parameters processed by the PMS module during app installation and restart operations.
- 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-2023-39386 — 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-39386 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