VulnerabilityPublished 30 Oct 2024Updated 31 Oct 2024

CVE-2024-37573: com.talkatone.android

Affects com.talkatone.androidSource CVE Database V5

Not known to be exploited · CVSS 8.4 High.

Data as of 26 Oct 2026, 12:54 UTC

CVSS 3.1 base score

8.4High

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

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

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

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

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

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
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: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 30 Oct 2024
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.talkatone.android`pkg:github/actuator/com.talkatone.android`Other threats	Affected =8.4.6	Fixed in–

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

AI-suggested

Until an official patch is released, users and organizations should take proactive steps to mitigate this vulnerability. First, restrict installation of untrusted or unknown applications to reduce the risk of malicious apps exploiting this flaw. Employ mobile device management (MDM) solutions to enforce app whitelisting or blacklisting policies. Monitor device behavior for unusual outgoing call patterns that could indicate exploitation. Disable or uninstall the Talkatone app if it is not essential or replace it with a more secure alternative communication app. Developers and security teams should review and audit intent handling in their own apps to prevent similar issues. Once a patch is available, prioritize immediate update deployment. Additionally, consider implementing runtime application self-protection (RASP) or endpoint detection and response (EDR) tools capable of detecting unauthorized call attempts. Educate users about the risks of installing apps from unverified sources and the importance of scrutinizing app permissions and behaviors.

Description

The Talkatone com.talkatone.android application 8.4.6 for Android enables any installed application (with no permissions) to place phone calls without user interaction by sending a crafted intent via the com.talkatone.vedroid.ui.launcher.OutgoingCallInterceptor component.

Impact

The vulnerability allows any app installed on an Android device with Talkatone 8.4.6 to place phone calls without user knowledge or permission. This can lead to unauthorized premium-rate calls causing financial losses to users or organizations. Confidentiality is compromised as attackers can infer user activity or location through call patterns. Integrity is affected because attackers can manipulate call behavior, potentially interfering with legitimate communications. Availability is impacted as malicious apps could flood the phone system with calls, causing denial of service or battery drain. For organizations, this could result in unexpected telephony costs, reputational damage, and potential regulatory compliance issues related to user privacy. The lack of required permissions and user interaction lowers the barrier for exploitation, increasing the risk of widespread abuse if malicious apps are distributed via app stores or sideloaded. Although no exploits are currently known, the vulnerability's characteristics make it a significant threat to both individual users and enterprises relying on Talkatone for voice communications.

References

github.com/actuator/com.talkatone.android/blob/main/CVE-2024-37573 (opens in a new tab)

Community reviews

Loading reviews…