CVE-2022-23427
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 · uneditedPendingIntent hijacking vulnerability in KnoxPrivacyNoticeReceiver prior to SMR Feb-2022 Release 1 allows local attackers to access media files without permission via implicit Intent.
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 a PendingIntent hijacking vulnerability in Samsung's KnoxPrivacyNoticeReceiver component. A local attacker can exploit an implicit Intent to hijack a PendingIntent, allowing unauthorized access to media files without the required permissions. The vulnerability exists in Samsung mobile devices running Knox versions prior to the February 2022 security maintenance release.
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= 10.0= 11.0= 12.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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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.
-
Identify device manufacturer and modelCheck if the device is a Samsung mobile device (look for Samsung in system settings or use 'getprop ro.product.brand' command)Affected if Device is not a Samsung device - this vulnerability only affects Samsung devices with Knox
-
Confirm Android versionCheck Android version in Settings > About Phone > Android version, or use 'getprop ro.build.version.release'Affected if Version is 10.0, 11.0, or 12.0 - these are the affected versions per the CVE
-
Check Samsung security patch levelCheck Settings > About Phone > Software information > Security patch level, or use 'getprop ro.build.version.security_patch'Affected if Security patch level is earlier than February 2022 (the vulnerability was fixed in the Feb-2022 SMR release)
-
Verify KnoxPrivacyNoticeReceiver component existsCheck if the KnoxPrivacyNoticeReceiver component is present on the device - this can be done by examining installed Knox-related packages via package manager or checking for the component in app manifests if accessibleAffected if The KnoxPrivacyNoticeReceiver component is present and active - this is the vulnerable component
A Samsung device running Android 10, 11, or 12 with a security patch level before February 2022 and with the KnoxPrivacyNoticeReceiver component present is likely affected by this PendingIntent hijacking vulnerability.
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 · scopedApply the Samsung SMR Feb-2022 Release 1 or later security patch, which contains the fix for this PendingIntent hijacking vulnerability in KnoxPrivacyNoticeReceiver.
SMR Feb-2022 Release 1 or later
- 1. Navigate to Settings on the Samsung Android device
- 2. Go to 'Software update' or 'System updates'
- 3. Check for and download the February 2022 Samsung Security Maintenance Release (SMR Feb-2022 Release 1) or later
- 4. Install the security update and restart the device
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-23427 — 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-23427 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