CVE-2023-48423
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 dhcp4_SetPDNAddress of dhcp4_Main.c, there is a possible out of bounds write due to a missing bounds check. This could lead to remote code execution 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 · high confidenceA buffer overflow vulnerability exists in the DHCP client function dhcp4_SetPDNAddress in dhcp4_Main.c. The function fails to validate buffer boundaries before writing PDN (Packet Data Network) address data, allowing an attacker to trigger an out-of-bounds write. Since DHCP responses are processed automatically without user interaction or elevated privileges, this enables remote code execution on the affected 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 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Confirm the device runs AndroidCheck the OS type - look for Android in system properties or /system/build.propAffected if The device is running any Android version
-
Identify the Android versionRun 'getprop ro.build.version.release' or check Settings > About Phone > Android versionAffected if Any Android version is installed (all versions are affected)
-
Verify DHCP client is in useCheck if mobile data/DHCP is active - look for dhcp service or pdp context active. On Android, cellular interfaces (rmnet0, etc.) obtain addresses via DHCP for PDN connectionsAffected if DHCP client is used for mobile data (PDP) connections - this is the vulnerable code path
-
Check for dhcp4 client processLook for dhcp4-related processes or services: 'ps -A | grep -i dhcp' or check /proc/<pid>/cmdline for dhcp4_MainAffected if The dhcp4 client daemon is running (processes DHCP responses for mobile data)
If the device runs Android and uses DHCP for mobile data connections, it is affected by this vulnerability.
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 vendor-provided patch that adds proper bounds checking before writing address data to the buffer. Until a patch is available, consider network segmentation to limit exposure to untrusted DHCP servers.
- Check the Android Security Bulletin for the month this CVE was patched to obtain the specific patch level (e.g., 2023-12-01 or later)
- Apply the latest Android security update available for your device from your device manufacturer
- For devices no longer receiving official updates, consider upgrading to a newer device that still receives monthly security patches
- If available, apply the specific patch for CVE-2023-48423 as listed in the Android Security Bulletin
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.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,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-48423 — 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-48423 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