CVE-2023-21375
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 Sysproxy, there is a possible out of bounds write due to an integer underflow. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
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 confidenceIn Sysproxy, an integer underflow allows an out-of-bounds memory write, enabling local privilege escalation without requiring user interaction or additional execution privileges.
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< 14.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
- High
CVSS:3.1/AV:L/AC:L/PR:L/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.
-
Check the Android version installed on the deviceNavigate to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shell or terminalAffected if The reported version is below 14.0 (Android 14)
-
Verify the Sysproxy component is present on the deviceCheck for the sysproxy binary or library using 'find / -name '*sysproxy*' 2>/dev/null' or locate the sysproxy service in /system/bin/ or /vendor/bin/ via ADB shellAffected if The sysproxy binary or library exists on the device
-
Confirm sysproxy is enabled and accessibleCheck if the sysproxy service is running via 'ps -A | grep sysproxy' or if the binary has execute permissions via 'ls -la <path_to_sysproxy>' in ADB shellAffected if The sysproxy binary is present and has execute permissions, indicating the component is active
The device is affected if it runs Google Android with a version lower than 14.0 and has the sysproxy component present and executable on the system.
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 · scoped14.0
Apply the vendor-supplied patch for CVE-2023-21375 which addresses the integer underflow in Sysproxy by implementing proper bounds validation before memory operations.
Android 14.0
- Check current Android version by going to Settings > About Phone > Android version
- Verify your device model is eligible for Android 14 upgrade by checking the device manufacturer's update support page
- Connect device to Wi-Fi and ensure battery is charged above 50%
- Go to Settings > System > Software Update (or Settings > About Phone > System Update)
- Tap 'Check for updates' and download any available Android 14 update
- Restart the device after the update completes to apply all security patches
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-21375 — 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-21375 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