CVE-2023-21442
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 · uneditedImproper access control vulnerability in Runestone application prior to version 2.9.09.003 in Android R(11) and 3.2.01.007 in Android S(12) allows local attackers to get device location information.
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 confidenceImproper access control vulnerability in the Runestone Android application allows a local attacker with device access to retrieve device location information. The vulnerability stems from insufficient authorization checks within the app that should restrict access to sensitive location data.
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.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.
-
Verify Runestone app is installedCheck device application list or run: pm list packages | grep runestone (via ADB shell)Affected if Runestone package is present on the device
-
Check Runestone app versionUse Settings > Apps > Runestone > Version info, or run: dumpsys package [package_name] | grep versionName (via ADB shell)Affected if Version is below 2.9.09.003 on Android 11 or below 3.2.01.007 on Android 12
-
Confirm Android OS versionCheck Settings > About Phone > Android version, or run: getprop ro.build.version.release (via ADB shell)Affected if Device runs Android 11 or Android 12
-
Check location permission statusInspect app permissions via Settings > Apps > Runestone > Permissions, or run: dumpsys package [package_name] | grep -i location (via ADB shell)Affected if Location permission is granted to Runestone app
Device is affected if Runestone app is installed with a version below 2.9.09.003 (Android 11) or below 3.2.01.007 (Android 12), the device runs Android 11 or 12, and the app has been granted location permission.
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 · scopedUpgrade Runestone application to version 2.9.09.003 (Android R/11) or 3.2.01.007 (Android S/12) or later to obtain the patched build with proper access controls.
Runestone app version 2.9.09.003 (Android R/11) or version 3.2.01.007 (Android S/12) or later
- Open the Google Play Store or Samsung Galaxy Store on the affected device
- Search for the 'Runestone' application or locate it in your installed apps
- Tap on the Runestone app and select 'Update' to install the latest version
- For Android R(11) devices, ensure the update to version 2.9.09.003 or later is applied
- For Android S(12) devices, ensure the update to version 3.2.01.007 or later is applied
- Verify the installed version by going to Settings > Apps > Runestone > App info
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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 $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-21442 — 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-21442 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