CVE-2024-54983
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 · uneditedAn issue in Quectel BC95-CNV V100R001C00SPC051 allows attackers to bypass authentication via a crafted NAS message.
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 confidenceThe Quectel BC95-CNV NB-IoT module V100R001C00SPC051 contains an authentication bypass vulnerability where attackers can circumvent the authentication mechanism by sending specially crafted NAS (Non-Access Stratum) messages. This could allow unauthorized access to the cellular network infrastructure.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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.
-
Identify the Quectel BC95-CNV moduleCheck your device documentation, BOM (Bill of Materials), or physically inspect the module labeling to confirm the model number is BC95-CNV. If integrated into an IoT device, consult the device manufacturer's specifications for the cellular module used.Affected if The device does not use a Quectel BC95-CNV module, then this CVE does not apply.
-
Check the installed firmware versionConnect to the module via serial AT interface (typically 9600 baud) and send the command AT+CGMR or ATI to retrieve the firmware version. Compare the output against V100R001C00SPC051.Affected if The firmware version is V100R001C00SPC051, the device is directly affected by this vulnerability.
-
Determine if the device is actively registered on a cellular networkSend the command AT+CEREG? to check EPS Network Registration Status. A response of +CEREG: 0,1 or +CERREG: 0,1 indicates the device is registered and connected to a network, making it potentially exploitable.Affected if The device is registered and connected to a cellular network (CEREG shows 0,1), the NAS message handling is active and the authentication bypass could be exploited.
-
Verify network exposure and segmentationReview network architecture to determine if the cellular interface is accessible from untrusted networks or if there are network-level controls limiting exposure of the NAS layer.Affected if The device has direct cellular connectivity without network segmentation or filtering, it is exposed to potential exploitation from malicious NAS messages.
You are affected if you have a Quectel BC95-CNV module running firmware version V100R001C00SPC051 and the device is actively connected to a cellular network.
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 firmware updates from Quectel when available; in the interim, implement network-level monitoring and filtering for abnormal NAS message patterns and restrict physical/radio access to the device.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-54983 — 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-54983 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