CVE-2024-32924
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 DeregAcceptProcINT of cn_NrmmStateDeregInit.cpp, there is a possible denial of service due to a logic error in the code. This could lead to remote denial of service 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 confidenceA logic error in the DeregAcceptProcINT function within cn_NrmmStateDeregInit.cpp causes a denial of service condition. The vulnerability allows remote attackers to trigger a DoS without requiring authentication or user interaction, likely due to improper state handling during a deregistration acceptance procedure in what appears to be a telecom/network protocol implementation.
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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Identify the Android version in useOn the Android device, go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shellAffected if Any Android version is running, as the affected products list states all versions are impacted
-
Determine if the device uses IMS (IP Multimedia Subsystem) servicesCheck for presence of IMS-related carrier services or IMS stack components on the device. This may be visible in Settings > Network & Internet > Mobile Network > Advanced > IMS settings, or by examining system logs for IMS-related processesAffected if The device supports and uses IMS functionality for VoLTE/VoWiFi, as the vulnerable code (cn_NrmmStateDeregInit.cpp) appears to be part of the NRMm state machine for network deregistration procedures in telecom protocols
-
Check for anomalous mobile network behaviorMonitor device logs (logcat) or network traffic for unexpected deregistration messages or frequent loss of cellular service, particularly involving the deregistration acceptance procedureAffected if The device experiences repeated or unexpected network deregistration events that could indicate exploitation of the logic error in DeregAcceptProcINT
-
Review carrier/ROM build for telecom component patchesIf available, examine the build fingerprint or carrier firmware version for any applied security patches related to telecom/network protocol handling. Check getprop for relevant system propertiesAffected if The build does not contain specific patches addressing the cn_NrmmStateDeregInit.cpp vulnerability in the deregistration state machine
Since all Android versions are listed as affected, the primary condition for impact is simply running any Android device that utilizes IMS-based cellular services, with the vulnerability residing in the telecom stack's deregistration acceptance state handling logic.
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 patches for this vulnerability. If no patch is available, implement network-level rate limiting and monitoring to detect and mitigate anomalous deregistration traffic patterns.
- 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-2024-32924 — 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-32924 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