CVE-2024-53932
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 · uneditedThe com.remi.colorphone.callscreen.calltheme.callerscreen (aka Color Phone: Call Screen Theme) application through 21.1.9 for Android enables any application (with no permissions) to place phone calls without user interaction by sending a crafted intent via the com.remi.colorphone.callscreen.calltheme.callerscreen.dialer.DialerActivity 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 · high confidenceThe Color Phone Android application (versions through 21.1.9) exposes the DialerActivity component without proper permission checks. Any installed application can send a crafted intent to this exported component to trigger outgoing phone calls without user interaction or requiring any permissions, effectively bypassing Android's call authorization controls.
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
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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.
-
Check if Color Phone app is installedRun 'pm list packages | grep -i color' or check package list in Settings > Apps for a package named 'Color Phone' or similar (such as 'com.colorphone.dialer' or 'com.colorphone.flash')Affected if The Color Phone application is present on the device
-
Identify the exact package nameUse 'adb shell pm list packages -3 | grep -i color' to list third-party packages containing 'color' in the name, or look at the app's package name in Settings > Apps > App InfoAffected if A package matching Color Phone is found
-
Retrieve the installed versionRun 'adb shell dumpsys package <package_name>' and look for 'versionName' and 'versionCode', or view in Settings > Apps > App Info > VersionAffected if The version is 21.1.9 or any earlier version through the entire 21.x.x lineage
-
Verify the vulnerable component existsUse 'aapt dump badging <apk_path>' or 'adb shell pm dump <package_name> | grep -A 20 Activity' to inspect if DialerActivity is declared in the manifest and exportedAffected if The DialerActivity component is present and shows 'android:exported=true' in the manifest without android:permission attribute
If the Color Phone app is installed with version 21.1.9 or earlier and the DialerActivity component is exported without permission checks, the device is vulnerable to unauthorized outgoing calls initiated by any other app.
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 dataImplement proper permission enforcement on the DialerActivity by requiring the CALL_PHONE permission and ensuring the activity is not unnecessarily exported, or add explicit permission checks within the activity's intent handling logic.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2024-53932 — 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-53932 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