CVE-2025-43977
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.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.
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 · moderate confidenceThe com.skt.prod.dialer Android application through version 12.5.0 contains an improper access control vulnerability in the OutgoingCallInternalBroadcaster component. This component accepts intents from any installed application without requiring the CALL_PHONE permission or user confirmation, allowing malicious apps to trigger outgoing phone calls silently.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 12.5.0CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/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 installed version of com.skt.prod.dialerUse 'adb shell dumpsys package com.skt.prod.dialer' or check via Settings > Apps > com.skt.prod.dialer to find the installed version numberAffected if The installed version is exactly 12.5.0 (note: earlier versions may also be affected but only 12.5.0 is explicitly listed as affected)
-
Verify OutgoingCallInternalBroadcaster component is exportedDecompile the APK and inspect AndroidManifest.xml for the OutgoingCallInternalBroadcaster receiver declaration; check if android:exported="true" is set without proper permission requirementsAffected if The component has android:exported="true" and does not require android:permission="android.permission.CALL_PHONE"
-
Confirm CALL_PHONE permission is not enforced on the componentReview the component's intent filter and permission attributes in the manifest - verify there is no android:permission="android.permission.CALL_PHONE" or similar restriction on the OutgoingCallInternalBroadcasterAffected if The component accepts intents without requiring the CALL_PHONE runtime permission
-
Test component accepts intents from arbitrary appsCreate a minimal test app that sends an Intent to OutgoingCallInternalBroadcaster without any permission and observe if the call is initiatedAffected if The component processes the intent and initiates an outgoing call without prompting for permission or user confirmation
If com.skt.prod.dialer version 12.5.0 is installed AND the OutgoingCallInternalBroadcaster component is exported without CALL_PHONE permission enforcement, the device is vulnerable to silent outgoing call initiation by any installed 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 dataSK Telecom should implement proper permission validation on the OutgoingCallInternalBroadcaster component, requiring the CALL_PHONE runtime permission and/or user confirmation before placing any calls. Users should update to the patched version once released.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-43977 — 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-2025-43977 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