CVE-2024-23359
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 · uneditedInformation disclosure while decoding Tracking Area Update Accept or Attach Accept message received from network.
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 vulnerability exists in the decoding logic of Tracking Area Update Accept and Attach Accept messages within a mobile network protocol stack. When processing these 3GPP mobility management messages received from the network, the decoder improperly handles certain fields or structures, leading to information disclosure. This could expose sensitive mobile subscriber data or network configuration details during the decode operation.
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 versionsall versionsall versionsall 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L
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 Qualcomm firmware versionCheck the system firmware version or boot logs for the Qualcomm chip model (Qcn9024, Qcs4490, Qcs5430, Qcs6490, Qcs8550, Qep8111, Qfw7114, or Qfw7124). Use 'cat /proc/version' or check boot logs for the firmware identifier.Affected if The device runs any version of the listed Qualcomm firmware products
-
Confirm 3GPP mobility management stack is activeCheck if the mobile network protocol stack handling LTE/5G mobility management (Tracking Area Update and Attach procedures) is enabled. Inspect running processes or loaded modules related to 3GPP MM (Mobility Management) - look for processes handling 'NAS' (Non-Access Stratum) or 'EMM' (EPS Mobility Management) protocols.Affected if The 3GPP mobility management message decoder is actively processing TAU Accept or Attach Accept messages from the network
-
Review decoder logs for malformed message handlingInspect protocol stack logs for error messages or warnings related to Tracking Area Update Accept or Attach Accept message parsing. Look for indications of decoder failures, buffer issues, or unexpected field handling during 3GPP mobility management message processing.Affected if Logs show decoder errors, crashes, or anomalous behavior when processing TAU Accept or Attach Accept messages
-
Check for information disclosure indicatorsMonitor network or debug logs for unexpected data exposure during mobility management message decode operations. Look for leaked memory contents, unexpected subscriber data appearing in logs, or malformed data structures in protocol analysis outputs.Affected if Subscriber identity (IMSI), location area codes, or network configuration data appears unexpectedly in logs or debug outputs during message decoding
If the system uses any of the affected Qualcomm firmware products (Qcn9024, Qcs4490, Qcs5430, Qcs6490, Qcs8550, Qep8111, Qfw7114, Qfw7124) and processes 3GPP mobility management messages (TAU Accept or Attach Accept), the environment is potentially affected by this information disclosure 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.
From vendor dataApply the vendor-provided patch to the protocol stack library that handles 3GPP mobility management message decoding. If no patch is available, contact the affected product vendor or library maintainer for remediation guidance.
- 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-23359 — 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-23359 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