CVE-2024-36063
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 Goodwy com.goodwy.dialer (aka Right Dialer) application through 5.1.0 for Android enables any application (with no permissions) to place phone calls without user interaction by sending a crafted intent via the com.goodwy.dialer.activities.DialerActivity 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 · high confidenceThe Right Dialer Android app exposes its DialerActivity component without proper permission enforcement, allowing any installed application to trigger outgoing phone calls without user interaction by sending a crafted intent. This bypasses Android's CALL_PHONE permission model and enables unauthorized call placement.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Identify if Right Dialer app is installedCheck device or APK list for the 'Right Dialer' application package. Use 'adb shell pm list packages' or inspect installed apps through device settings.Affected if The Right Dialer app is present on the device
-
Inspect the app manifest for DialerActivityDecompile the APK (using apktool or similar) and examine AndroidManifest.xml. Look for the <activity> declaration with android:name containing 'DialerActivity'.Affected if The DialerActivity component exists in the manifest
-
Check if DialerActivity is exportedIn the manifest, locate the DialerActivity <activity> tag and examine the android:exported attribute value.Affected if android:exported is set to 'true' or the attribute is missing (defaulting to true)
-
Verify permission requirements on DialerActivityIn the manifest, check if the DialerActivity <activity> tag includes android:permission="android.permission.CALL_PHONE" or similar protective permission.Affected if No android:permission attribute is defined on the DialerActivity, or a weak permission (like INTERNET) is used instead of CALL_PHONE
A user is affected if the Right Dialer app is installed AND its DialerActivity is exported without proper CALL_PHONE permission enforcement, allowing any app to trigger calls.
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 dataThe app developer must add permission checks to the DialerActivity (e.g., require CALL_PHONE permission) or set android:exported="false" if the activity is not intended for external use, and implement user confirmation before placing any calls.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-36063 — 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-2024-36063 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