CVE-2024-53936VulnerabilityPublished 6 Jan 2025Updated 8 Jan 2025

CVE-2024-53936: n/a

Source CVE Database V5

Not known to be exploited · CVSS 6.3 Medium.

Data as of 26 Oct 2026, 07:57 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 2026-10-26.

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

AI-suggested

To mitigate CVE-2024-53936, organizations and users should: 1) Identify and uninstall the 'Color Phone Call Screen' app if it is not essential, especially in enterprise environments. 2) If the app is required, monitor for updates or patches from the vendor and apply them promptly once available. 3) Use mobile device management (MDM) solutions to restrict installation of untrusted or unnecessary apps that could exploit this vulnerability. 4) Employ runtime application self-protection (RASP) or endpoint detection and response (EDR) tools to detect suspicious call initiation patterns. 5) Restrict or audit intent communications on Android devices using security frameworks or custom policies to prevent unauthorized intents targeting vulnerable components. 6) Educate users about risks of installing apps from untrusted sources and the importance of monitoring call logs for unexpected activity. 7) Network-level controls can be used to detect and block unusual call traffic patterns. These steps go beyond generic advice by focusing on controlling the vulnerable component's exposure and monitoring for exploitation attempts.

Description

The com.asianmobile.callcolor (aka Color Phone Call Screen App) application through 24 for Android enables any application (with no permissions) to place phone calls without user interaction by sending a crafted intent via the com.asianmobile.callcolor.ui.component.call.CallActivity component.

Impact

The primary impact of CVE-2024-53936 is unauthorized phone call initiation by malicious apps without requiring any permissions or user interaction. This can lead to several adverse effects: financial loss due to premium or international calls, privacy violations through call metadata exposure, potential harassment or denial of service by call spamming, and erosion of user trust in affected devices. While the confidentiality, integrity, and availability impacts are rated low individually, the combined effect can be significant for users and organizations relying on the affected app. Enterprises with Android devices using this app may face increased risk of fraud or operational disruption. The lack of required permissions and user interaction lowers the barrier for exploitation, increasing the threat surface. However, the attack vector is adjacent network, meaning the attacker must have some level of access to the device or network environment. Since no known exploits are reported, the immediate risk is moderate but could escalate if weaponized.

References

Community reviews

Loading reviews…