CVE-2025-43977VulnerabilityPublished 21 Jul 2025Updated 22 Jul 2025

CVE-2025-43977: com.skt.prod.dialer · n/a

Affects com.skt.prod.dialerSource CVE Database V5

Not known to be exploited · CVSS 4.3 Medium.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score

4.3Medium

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

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

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

Attack Vector: Physical
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: Physical: The attack requires the attacker to physically touch or manipulate the vulnerable component. Physical interaction may be brief or persistent.
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 21 Jul 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

Affected software

Product	Affected	Fixed in
GitHubactuator/com.skt.prod.dialer`pkg:github/actuator/com.skt.prod.dialer`Other threats	Affected <=12.5.0	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 this vulnerability, European organizations should: 1) Audit and inventory Android devices to identify those running the vulnerable com.skt.prod.dialer app version 12.5.0 or earlier. 2) Coordinate with device manufacturers or software vendors to obtain and deploy patches or updated dialer applications that properly restrict intent receivers and enforce permission checks. 3) Implement mobile device management (MDM) solutions to restrict installation of untrusted or unknown applications, reducing the risk of malicious apps exploiting this vulnerability. 4) Monitor telephony usage logs for unusual call patterns, such as unexpected outgoing calls or spikes in call volume, to detect potential exploitation. 5) Educate users about the risks of installing apps from untrusted sources and encourage the use of official app stores with security vetting. 6) Consider disabling or restricting the com.skt.prod.dialer app where feasible, or replacing it with alternative dialer apps that do not exhibit this vulnerability. 7) Employ network-level controls to detect and block suspicious telephony traffic that may result from unauthorized calls.

Description

The com.skt.prod.dialer application through 12.5.0 for Android enables any installed application (with no permissions) to place phone calls without user interaction by sending a crafted intent via the com.skt.prod.dialer.activities.outgoingcall.OutgoingCallInternalBroadcaster component.

Impact

For European organizations, this vulnerability poses risks primarily in environments where Android devices with the vulnerable dialer app are used extensively, such as corporate mobile fleets or BYOD scenarios. Unauthorized calls could lead to financial fraud, especially if premium-rate or international calls are placed without user knowledge. Additionally, the silent call initiation could be leveraged to disrupt communication channels or cause denial of service by exhausting call quotas or billing limits. Privacy concerns arise as attackers could infer user behavior or location based on call patterns. Organizations in sectors like finance, telecommunications, and government, which rely heavily on secure and auditable telephony, could face reputational damage and regulatory scrutiny under GDPR if such unauthorized activities lead to data breaches or misuse of personal data. The absence of user interaction or permission requirements increases the risk of widespread exploitation if malicious apps are distributed through app stores or sideloaded.

References

Community reviews

Loading reviews…