VulnerabilityPublished 6 Jan 2025Updated 8 Jan 2025

CVE-2024-53933: com.callerscreen.colorphone.themes.callflash

Affects com.callerscreen.colorphone.themes.callflashSource CVE Database V5

Not known to be exploited · CVSS 6.3 Medium.

Data as of 26 Oct 2026, 11:42 UTC

CVSS 3.1 base score

6.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Attack Vector: Adjacent
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Adjacent: The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 6 Jan 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
GitHubactuator/com.callerscreen.colorphone.themes.callflash`pkg:github/actuator/com.callerscreen.colorphone.themes.callflash`Other threats	Affected <=1.0.7	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-53933, organizations and users should first identify and remove the vulnerable Color Call Theme & Call Screen app from their Android devices. If removal is not immediately possible, restrict the app’s ability to receive external intents by disabling or limiting the exposed DialerActivity component via Android’s package manager or using Mobile Device Management (MDM) policies. Implement application whitelisting to prevent installation of untrusted apps that could exploit this vulnerability. Monitor telephony logs for unusual call patterns or spikes in call volume that may indicate exploitation. Educate users about the risks of installing apps from untrusted sources and the importance of reviewing app permissions and behaviors. Vendors should be urged to release patches that enforce proper intent validation and restrict unauthorized access to sensitive components. Network-level controls such as call rate limiting and fraud detection systems can help reduce financial impact. Regularly update Android OS and security policies to minimize attack surface.

Description

The com.callerscreen.colorphone.themes.callflash (aka Color Call Theme & Call Screen) application through 1.0.7 for Android enables any application (with no permissions) to place phone calls without user interaction by sending a crafted intent via the com.android.call.color.app.activities.DialerActivity component.

Impact

The primary impact of CVE-2024-53933 is unauthorized phone call initiation by any application without permissions or user consent. This can lead to financial losses through toll fraud if calls are made to premium-rate numbers. It also poses privacy risks as calls could be made to contacts or external numbers without the user's knowledge, potentially exposing sensitive information or enabling social engineering attacks. The integrity of telephony functions is compromised as the app can be manipulated to perform actions it was not intended to. Availability impact is limited but possible if excessive unauthorized calls disrupt legitimate phone usage. For organizations, this vulnerability could be exploited to bypass telephony restrictions, cause reputational damage, and increase operational costs. The risk is elevated in environments where the vulnerable app is widely deployed on employee devices, especially in sectors like finance, government, and telecommunications. Although exploitation requires proximity (adjacent network) or local device access, the lack of required permissions lowers the barrier for attackers to abuse this vulnerability.

References

Community reviews

Loading reviews…