# CVE-2024-36063: Missing authorization in n/a

> An attacker can place phone calls without user interaction by sending a crafted intent to the dialer activity, bypassing authorization checks.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Nov 2024
- **Updated:** 8 Nov 2024
- **Also known as:** GHSA-rpqv-x6cm-mjw9

## What is CVE-2024-36063?

CVE-2024-36063 is a high-severity missing authorization vulnerability in n/a, published on 7 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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

Weakness: CWE-276 (Incorrect Default Permissions)

## Which versions are affected by CVE-2024-36063?


## How do I fix CVE-2024-36063?

No fix has been published for CVE-2024-36063 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-36063 being exploited?

There is no known exploitation of CVE-2024-36063 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-36063 and fix it if it is affected.

What it is: CVE-2024-36063 is a high-severity missing authorization vulnerability in n/a, published on 7 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-36063 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-36063/ (Markdown: https://insights.sbomify.com/CVE-2024-36063/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-36063
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-36063
- OSV: https://osv.dev/vulnerability/CVE-2024-36063

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-36063/
Summaries are generated and may contain mistakes; the official description above is the record.