CVE-2024-54984
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 BG96 BG96MAR02A08M1G allows attackers to bypass authentication via a crafted NAS message. NOTE: this is disputed by the supplier.
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 BG96MAR02A08M1G cellular modem contains a vulnerability allowing authentication bypass through specially crafted NAS (Non-Access Stratum) messages. NAS messages control connection procedures between mobile devices and the LTE network, including authentication handshake. An attacker sending malformed NAS messages could potentially bypass the authentication layer and gain unauthorized network access. The 9.8 CVSS score indicates this is remotely exploitable with low complexity and complete impact on confidentiality, integrity, and availability.
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 Quectel BG96 modem hardwareUse AT commands (AT+CGMM or ATI) to query the modem model, or inspect physical hardware labels and system device inventories for 'BG96' or 'Quectel' identifiersAffected if A Quectel BG96-series cellular modem is present in the environment
-
Check firmware versionSend AT command 'AT+CGMR' to retrieve the firmware version string and compare it to 'BG96MAR02A08M1G' or note if the version starts with 'BG96MAR02A08'Affected if The firmware version matches BG96MAR02A08M1G or falls within the affected version range
-
Verify cellular network registration is activeSend AT command 'AT+CREG?' or 'AT+CGREG?' to check network registration status - a result of 0,1, or 5 indicates the modem is registered and actively exchanging NAS messages with the networkAffected if The modem shows registered status (0,1, or 5) indicating active cellular connection and NAS layer communication
-
Review NAS message logs if availableIf the modem or network infrastructure provides NAS debugging logs (AT+CNLOG=1 or vendor-specific logging), inspect for malformed or unexpected authentication-related NAS messagesAffected if Unusual or malformed NAS authentication messages are observed in the logs, or authentication sequences complete without proper challenge-response validation
You are affected if you have a Quectel BG96 modem running firmware version BG96MAR02A08M1G that is actively connected to a cellular network where it exchanges NAS messages.
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 dataContact Quectel for firmware updates addressing the NAS authentication bypass; if unavailable, implement network segmentation to isolate affected devices and consider hardware replacement. Monitor for unauthorized cellular network access attempts.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.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 $11,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-54984 — 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-54984 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