CVE-2024-45551
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 · uneditedCryptographic issue occurs during PIN/password verification using Gatekeeper, where RPMB writes can be dropped on verification failure, potentially leading to a user throttling bypass.
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 confidenceDuring PIN/password verification via Gatekeeper, a cryptographic implementation flaw causes RPMB (Replay Protected Memory Block) writes to be dropped when verification fails. This prevents the failed authentication attempt counter from being recorded, allowing unlimited retry attempts and bypassing user throttling protections designed to lock out attackers after multiple failures.
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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 Qualcomm Fastconnect WiFi/Bluetooth componentsCheck system information or device manager for Qualcomm Fastconnect 6700, 6800, 6900, or 7800 wireless adapter firmware. On Linux, use 'lspci' or 'iw list'; on Windows, check device manager properties.Affected if A Qualcomm Fastconnect wireless adapter is present in the system
-
Identify Qualcomm mobile platform firmwareCheck system or baseband firmware information for Qualcomm Flight Rb5 5G Platform, Qam8255p, Qam8295p, or Qam8620p. On Android, check 'Settings > About Phone > Baseband' or use 'getprop' commands.Affected if Any of these Qualcomm platform firmware components are present in the device
-
Confirm all versions are affectedReview the installed firmware version against the affected product list. According to the advisory, all versions of these specific Qualcomm firmware components are affected.Affected if The device runs any version of the listed Qualcomm Fastconnect or platform firmware, since the advisory states all versions are affected
-
Verify Gatekeeper throttling behaviorTest PIN/password verification with intentional incorrect attempts. Observe whether the failure counter increments in secure storage (RPMB). This typically requires access to secure debugging interfaces or TrustZone attestations.Affected if Failed authentication attempts do not increment the throttle counter in RPMB storage, allowing unlimited retries
-
Check for vendor security advisoriesSearch for OEM-specific security updates or patches that reference CVE-2024-45551 or the Gatekeeper RPMB write failure issue.Affected if No security update addressing this CVE has been applied to the firmware
A system is affected if it contains any Qualcomm Fastconnect or Qam/Flight Rb5 platform firmware, since all versions of these components are vulnerable to the Gatekeeper throttling bypass.
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 dataFix the Gatekeeper implementation to ensure RPMB writes (authentication failure counters) are committed to secure storage regardless of verification outcome. This likely requires modifying the error handling path in the Gatekeeper daemon to always persist throttle state before returning.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.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 $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-45551 — 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-45551 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