CVE-2024-34673
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 Input Validation in IpcProtocol in Modem prior to SMR Nov-2024 Release 1 allows local attackers to cause Denial-of-Service.
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 confidenceThis is an improper input validation vulnerability in the IpcProtocol component of a modem. Local attackers can send specially crafted IPC messages to trigger a denial-of-service condition, likely causing the modem service to crash or become unresponsive.
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= 12.0= 13.0= 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 Android OS versionGo to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADBAffected if Version is exactly 12.0, 13.0, or 14.0 (not newer versions)
-
Confirm Samsung device with modemVerify the device is a Samsung product with cellular modem capability. Check via 'getprop ro.product.brand' and confirm modem hardware existsAffected if Device is a Samsung Android phone/tablet with an active modem component
-
Verify IpcProtocol modem component is presentCheck for the IpcProtocol service or modem IPC daemon. Run 'ps -A | grep -i ipc' or check modem-related processes via 'dumpsys'Affected if The IpcProtocol component is running or loaded on the device
-
Assess local access exposureReview if local untrusted processes or apps can send IPC messages to the modem service. Check for exposed IPC sockets or services in /dev/socket or via 'dumpsys' for IPC-related servicesAffected if Local processes have direct access to modem IPC interfaces without proper authentication
The environment is affected if it is a Samsung Android device running version 12.0, 13.0, or 14.0 with the IpcProtocol modem component present and locally accessible to untrusted processes.
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 SMR Nov-2024 Release 1 or later vendor firmware update to the affected modem. As a secondary measure, restrict local access to the device to limit attack surface.
SMR Nov-2024 Release 1
- Check your Samsung device model and carrier for SMR Nov-2024 Release 1 availability
- Navigate to Settings > Security and privacy > Security update on your Samsung Android device
- Ensure the security patch level shows November 2024 or later
- If update is not yet available, periodically check for updates until SMR Nov-2024 Release 1 is delivered
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.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 $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-34673 — 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-2024-34673 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