CVE-2023-30701
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 in WifiGeofenceManager prior to SMR Aug-2023 Release 1 allows local attacker to arbitrary file access.
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 · high confidenceThis is a PendingIntent hijacking vulnerability in Samsung's WifiGeofenceManager component. A local malicious application can intercept or manipulate a PendingIntent created by the WifiGeofenceManager to gain arbitrary file system access. PendingIntent hijacking occurs when the intent is not properly secured (e.g., missing FLAG_IMMUTABLE), allowing an attacker to inject or redirect the intent's action.
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= 12.0= 13.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
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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.
-
Identify device manufacturer and modelCheck if the device is a Samsung device by looking at the device info in Settings > About Phone > Manufacturer or model nameAffected if Device is not made by Samsung, the vulnerability does not apply
-
Check Android versionGo to Settings > About Phone > Android version and verify the installed version is 11.0, 12.0, or 13.0Affected if Android version is outside 11.0, 12.0, or 13.0, the vulnerability does not apply
-
Check Samsung security patch levelGo to Settings > About Phone > Software information > Security patch level and note the dateAffected if Security patch level is earlier than August 2023, the device is likely vulnerable to this PendingIntent hijacking flaw in WifiGeofenceManager
A Samsung device running Android 11, 12, or 13 with a security patch level before August 2023 is affected by this PendingIntent hijacking vulnerability in the WifiGeofenceManager component.
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 Aug-2023 Release 1 security update or later to patch the WifiGeofenceManager vulnerability. For enterprise environments, deploy the security patch via Samsung Knox or enterprise MDM solutions and verify complete device coverage.
SMR Aug-2023 Release 1 or later
- 1. Navigate to Settings on the Samsung Android device
- 2. Go to Settings > Software update
- 3. Tap on Download and install to check for available updates
- 4. Ensure the device updates to the August 2023 Samsung Security Patch (SMR Aug-2023 Release 1) or later
- 5. Verify the security patch level in Settings > About phone > Software information > Security patch level shows August 2023 or later
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-2023-30701 — 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-30701 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