dbcve.org
Incorrect Permission AssignmentWeakness · CWE-732

CVE-2024-10018

CRITICAL · 9.8 CVSS v3.1 Published 2024-10-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
Improper permission control in the mobile application (com.transsion.aivoiceassistant) can lead to the launch of any unexported component.

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

The Transsion AI Voice Assistant Android app (com.transsion.aivoiceassistant) contains an improper permission control vulnerability allowing any external application to launch unexported (private) components within the app. This bypasses Android's component access controls, potentially enabling attackers to trigger sensitive activities, services, or broadcast receivers that were intended to be internal-only.

MitigationRestrict access to unexported components by implementing proper permission checks within the app's components or by applying the android:permission attribute to exported components. Audit all components to ensure only intentionally accessible ones are exported.

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 checks

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

  1. Verify Transsion AI Voice Assistant is installed
    Check if the app with package name 'com.transsion.aivoiceassistant' is installed on the device. Use 'adb shell pm list packages | grep transsion' or check in Settings > Apps.
    Affected if The package com.transsion.aivoiceassistant is present on the device.
  2. Extract and inspect the app manifest
    Obtain the APK from the device (via adb pull or other means) and extract AndroidManifest.xml using aapt (aapt dump badging <apkfile>) or a decompiler. Look for the 'exported' attribute on <activity>, <service>, and <receiver> tags.
    Affected if Any component declares 'android:exported="true"' without proper permission protection, or any unexported component can be invoked by any external app.
  3. Identify exported activities
    In the manifest, locate all <activity> elements. Check if android:exported is set to true or missing (defaults to true for intents with implicit filters). Note any activity elements that lack android:permission attributes.
    Affected if Activities intended to be internal are exported or accessible without permission checks.
  4. Identify exported services and receivers
    In the manifest, locate all <service> and <receiver> elements. Check their android:exported settings and whether android:permission is defined. A missing android:permission on an exported component indicates it accepts calls from any app.
    Affected if Services or broadcast receivers are exported without android:permission protection.
  5. Check for intent-filter components
    Any component with an <intent-filter> is automatically exported=true unless explicitly set to false. Review all intent-filter containing components in the manifest.
    Affected if Components with intent-filters are unintentionally exposed to external apps.

You are affected if the Transsion AI Voice Assistant app is installed AND any of its components (activities, services, receivers) are exported without android:permission protection, allowing arbitrary external apps to invoke internal-only components.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict access to unexported components by implementing proper permission checks within the app's components or by applying the android:permission attribute to exported components. Audit all components to ensure only intentionally accessible ones are exported.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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