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

> An attacker can place phone calls without user interaction by sending a crafted intent to the DialerActivity component in the Color Call Theme app.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Jan 2025
- **Updated:** 8 Jan 2025
- **Also known as:** GHSA-5hp7-929x-xgf8

## What is CVE-2024-53933?

CVE-2024-53933 is a medium-severity missing authorization vulnerability in n/a, published on 6 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The com.callerscreen.colorphone.themes.callflash (aka Color Call Theme & Call Screen) application through 1.0.7 for Android enables any application (with no permissions) to place phone calls without user interaction by sending a crafted intent via the com.android.call.color.app.activities.DialerActivity component.

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


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

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

## Is CVE-2024-53933 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-53933 is a medium-severity missing authorization vulnerability in n/a, published on 6 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-53933 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-53933/ (Markdown: https://insights.sbomify.com/CVE-2024-53933/index.md)
```

## Sources

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

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