CVE-2023-43488
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 · uneditedThe vulnerability allows a low privileged (untrusted) application to modify a critical system property that should be denied, in order to enable the ADB (Android Debug Bridge) protocol to be exposed on the network, exploiting it to gain a privileged shell on the device without requiring the physical access through USB.
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 confidenceA low-privileged Android application can modify a protected system property to enable ADB network exposure, bypassing the requirement for physical USB access and allowing the attacker to obtain a privileged shell on the device.
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 dataall versionsall versionsall versionsCVSS 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.
-
Identify device modelCheck the device model through system settings, boot logs, or physical label. Look for model numbers WR2107, WR2110, or WR2115 from Boschrexroth Ctrlx HMI Web Panel series.Affected if The device is a Boschrexroth Ctrlx HMI Web Panel WR2107, WR2110, or WR2115 model.
-
Verify ADB network service statusRun command 'getprop persist.sys.adb.network' or check if ADB is listening on TCP port 5555 (standard ADB network port) using 'netstat -an | grep 5555' or 'ss -tlnp | grep 5555'.Affected if The ADB network service is enabled or listening on TCP port 5555.
-
Inspect ADB-related system propertiesExecute 'getprop | grep adb' to list all ADB-related system properties. Check properties such as 'persist.adb.enabled', 'service.adb.tcp.port', or similar that control ADB network functionality.Affected if A system property related to ADB network exposure is set to enabled (value of 1, true, or a port number).
-
Review ADB daemon security contextCheck the ADB daemon process using 'ps -Z | grep adbd' to see its SELinux domain or security context. A vulnerable configuration would show the daemon running in a domain that permits modification by unprivileged apps.Affected if The ADB daemon is running in a security context that allows modification by low-privileged applications.
-
Check for suspicious applications with elevated privilegesReview installed applications for any that request WRITE_SECURE_SETTINGS or modify system properties. Use 'dumpsys package <pkg> | grep REQUEST' to check permissions of suspicious apps.Affected if An installed application has WRITE_SECURE_SETTINGS permission or can modify protected system properties.
A user is affected if they own a Boschrexroth Ctrlx HMI Web Panel (WR2107, WR2110, or WR2115) with ADB network exposure enabled, indicating the protected system property was modified by an untrusted application.
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-provided system updates/patches for Android; avoid installing untrusted applications.
- Consultation4.0 h
- Testing2.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 $2,336.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-43488 — 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-43488 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