dbcve.org
Androidx.car.appApplication · Google

CVE-2024-10382

HIGH · 7.5 CVSS v3.1 Published 2024-11-20
Fix available
A fix is available. Upgrade to after 1.4.0 or later.
See remediation →
75/100
Remediation priority · High

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
There exists a code execution vulnerability in the Car App Android Jetpack Library. CarAppService uses deserialization logic that allows construction of arbitrary java classes. This can lead to arbitrary code execution when combined with specific Java deserialization gadgets. An attacker needs to install a malicious application on victims device to be able to attack any application that uses vulnerable library. We recommend upgrading the library past version 1.7.0-beta02.

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 · high confidence

The Car App Android Jetpack Library contains a deserialization vulnerability in CarAppService that allows construction of arbitrary Java classes. When combined with malicious deserialization gadgets, this enables arbitrary code execution on affected devices.

MitigationUpgrade the Car App Android Jetpack Library to a version newer than 1.7.0-beta02.

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
Androidx.car.appApplication
Affected:<= 1.4.0= 1.7.0

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
Local
Complexity
High
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/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 checks

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

  1. Locate androidx.car.app dependency in your project
    Search your project's build configuration files (build.gradle, build.gradle.kts, libs.versions.toml, gradle.lockfile) for 'androidx.car.app' or 'car-app' dependencies
    Affected if The androidx.car.app library is declared as a dependency
  2. Identify the installed version
    Extract the version number from the dependency declaration (e.g., '1.4.0', '1.7.0', or the version referenced in a version catalog)
    Affected if The version number matches <= 1.4.0 or equals 1.7.0
  3. Verify CarAppService is in use
    Search your source code for imports or usages of 'androidx.car.app' classes, particularly any class that extends CarAppService or implements CarAppServiceHost
    Affected if Your app uses classes from the androidx.car.app library that interact with CarAppService
  4. Confirm vulnerability applicability
    Review the Car App implementation to determine if it accepts and deserializes data (such as from Intent extras, bundled data, or remote messages) that could contain malicious deserialization gadgets
    Affected if Your CarAppService implementation deserializes untrusted data from external sources

You are affected if your project includes androidx.car.app library version 1.4.0 or earlier, or exactly version 1.7.0, and your CarAppService implementation deserializes external data.

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 a release after 1.4.0
Interim mitigation

Upgrade the Car App Android Jetpack Library to a version newer than 1.7.0-beta02.

Recommended fix High confidence

1.7.0-beta02 or later (1.7.0 recommended)

  1. Open the app-level build.gradle or build.gradle.kts file
  2. Locate the dependency declaration for androidx.car.app (e.g., implementation 'androidx.car.app:app:1.4.0')
  3. Update the version to 1.7.0-beta02 or later (recommended: 1.7.0 or latest stable release)
  4. Sync the Gradle project
  5. Rebuild and test the application to ensure the car app functionality works correctly
Caveat Review release notes for API changes between your current version and the target version; test thoroughly on all supported vehicle screen sizes and configurations

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

Fix this in Androidx.car.app Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-10382 — 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-10382 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