dbcve.org
AndroidOperating system · Google

CVE-2024-44100

HIGH · 7.5 CVSS v3.1 Published 2024-10-25
Fix available
A fix is available. Upgrade to 2024-10-05 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Android before 2024-10-05 on Google Pixel devices allows information disclosure in the modem component, A-299774545.

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 confidence

An information disclosure vulnerability exists in the modem component of Google Pixel devices running Android versions before the 2024-10-05 patch. The flaw allows unauthorized disclosure of potentially sensitive information through the modem without requiring user interaction or elevated privileges.

MitigationApply the October 2024 Android security update (or later) to affected Google Pixel devices to remediate this vulnerability in the modem component.

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 data
AndroidOperating system
Affected:< 2024-10-05

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
None
Availability
None

CVSS:3.1/AV:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm device is a Google Pixel
    Check the device model in Settings > About Phone > Model Number. This vulnerability only affects Google Pixel devices.
    Affected if Device is NOT a Google Pixel (other Android devices are not listed as affected for this CVE)
  2. Check Android version
    Go to Settings > About Phone > Android version. Note the full version number displayed.
    Affected if Android version is any version released before the 2024-10-05 patch (the specific version number varies by carrier/model)
  3. Verify security patch level
    Go to Settings > About Phone > Security patch level. This shows the date of the installed security updates.
    Affected if Security patch level is earlier than October 5, 2024 (the patch date must be before 2024-10-05)
  4. Identify modem component status
    This vulnerability resides in the modem component. There is no direct user-facing setting to check modem vulnerability status - the detection relies entirely on verifying the patch level in step 3.
    Affected if Security patch level shows a date before October 2024, indicating the modem has not received the fix

A Google Pixel device is affected if its security patch level predates October 5, 2024, regardless of Android version number, because the fix is delivered via the monthly security update.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 2024-10-05 or later
Fixed in 2024-10-05
Interim mitigation

Apply the October 2024 Android security update (or later) to affected Google Pixel devices to remediate this vulnerability in the modem component.

Recommended fix Moderate confidence

Android Security Patch Level 2024-10-05 or later on Google Pixel devices

  1. Check your current Android Security Patch Level by going to Settings > About Phone > Android version > Security Patch Level
  2. Ensure your Google Pixel device is running Android Security Patch Level dated 2024-10-05 or later
  3. Go to Settings > System > System Update to check for and install the latest security updates
  4. If no update is available, verify your carrier or Google provides an OTA update for your specific Pixel model
  5. For enterprise or managed devices, contact your IT administrator to ensure the October 2024 Android Security Bulletin updates are deployed
Caveat Standard Android security update - minimal risk; always backup data before major updates

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Android Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-44100 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-44100 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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