CVE-2023-30728
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 · uneditedIntent redirection vulnerability in PackageInstallerCHN prior to version 13.1.03.00 allows local attacker to access arbitrary file. This vulnerability requires user interaction.
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 confidenceIntent redirection vulnerability in the PackageInstallerCHN app allows a local attacker to access arbitrary files on the device. The flaw enables a malicious app to intercept or redirect intents from the package installer to access files outside its normal permissions, requiring user interaction to trigger.
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< 13.1.03.00CVSS 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
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 if PackageInstallerCHN app is installedUse ADB command: `adb shell pm list packages | grep packageinstallerchn` or check in Settings > Apps for PackageInstallerCHNAffected if The app is present on the device (system app on Samsung devices)
-
Retrieve installed version of PackageInstallerCHNUse ADB command: `adb shell dumpsys package com.sec.android.app.packageinstallerchn | grep versionName` or check app info in Settings > Apps > PackageInstallerCHN > VersionAffected if A version number is returned that is lower than 13.1.03.00
-
Compare version against affected rangeIf version is obtained, verify it is less than 13.1.03.00 (e.g., 13.1.02.50, 13.1.01.00, etc.)Affected if Installed version is below 13.1.03.00
-
Verify device can install apps from unknown sourcesCheck Settings > Security > Install unknown apps or Settings > Apps > Special access > Install unknown apps - see which apps have permission to install packagesAffected if Any app has permission to install packages and the PackageInstallerCHN version is vulnerable
Device is affected if PackageInstallerCHN is installed with a version lower than 13.1.03.00 and the device allows app installations that could trigger the intent redirection.
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 · scoped13.1.03.00
Update device firmware to version 13.1.03.00 or later to obtain the patched PackageInstallerCHN. Users should apply system updates promptly and avoid installing apps from untrusted sources.
13.1.03.00 or later
- Check current PackageInstallerCHN version in device settings or via adb shell dumpsys package com.sec.android.app.launcher (or relevant package name)
- Apply Samsung security update containing version 13.1.03.00 or later - typically via Settings > Software Update > Download and Install
- Verify the installed version is 13.1.03.00 or higher after update completion
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-30728 — 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-30728 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