CVE-2023-20828
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 · uneditedIn gps, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS08014144; Issue ID: ALPS08014144.
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 confidenceOut of bounds write vulnerability in the GPS daemon (gps) due to a missing bounds check. This allows local privilege escalation from System execution privileges without user interaction.
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= 2.6= 2022q3= 12.0= 13.0= 19.07.0= 21.02.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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/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 your product and versionDetermine which affected product is in use (Linuxfoundation Yocto, Rdkcentral Rdk B, Google Android, or Openwrt Openwrt) and note its exact version number.Affected if The product is Yocto 2.6, Rdk B 2022q3, Android 12.0, Android 13.0, Openwrt 19.07.0, or Openwrt 21.02.0
-
Verify GPS daemon is runningCheck if the GPS daemon (gps) process is active on the system. On Android, this may appear as a system service related to location. On embedded Linux systems, check for gpsd or vendor-specific GPS processes.Affected if The GPS daemon is running and processing GPS data on an affected product version
-
Check if GPS functionality is enabledExamine system configuration to determine if GPS/location services are enabled and actively in use. This may involve checking system settings, service configurations, or running processes related to location services.Affected if GPS/location features are enabled and the GPS daemon is processing input on an affected version
-
Confirm System-level execution contextVerify that the GPS daemon runs with elevated System privileges. This is typically the case by default on Android and embedded Linux distributions.Affected if The GPS daemon executes with System privileges rather than a sandboxed or unprivileged user account
You are affected if your device runs one of the specified product versions (Yocto 2.6, Rdk B 2022q3, Android 12.0/13.0, Openwrt 19.07.0/21.02.0) and the GPS daemon with System privileges is enabled and running.
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 dataApply vendor patch ALPS08014144 which adds proper bounds validation to the GPS component; this typically comes via system/firmware updates from the device vendor.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-20828 — 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-20828 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