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

> Any installed Android app can trigger phone calls without user interaction via a crafted intent, bypassing authorization checks in the TextNow application.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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:** 3 Feb 2025
- **Updated:** 5 Feb 2025
- **Also known as:** GHSA-q8p5-49qg-m9wx

## What is CVE-2024-36437?

CVE-2024-36437 is a medium-severity missing authorization vulnerability in n/a, published on 3 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The com.enflick.android.TextNow (aka TextNow: Call + Text Unlimited) application 24.17.0.2 for Android enables any installed application (with no permissions) to place phone calls without user interaction by sending a crafted intent via the com.enflick.android.TextNow.activities.DialerActivity component.

Weakness: CWE-926 (Improper Export of Android Application Components)

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


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

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

## Is CVE-2024-36437 being exploited?

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

Public exploit code:

- CVE-2024-36437 (github_poc): https://github.com/actuator/com.enflick.android.TextNow

## Fix prompt for AI coding agents

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

What it is: CVE-2024-36437 is a medium-severity missing authorization vulnerability in n/a, published on 3 Feb 2025. 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-36437 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-36437/ (Markdown: https://insights.sbomify.com/CVE-2024-36437/index.md)
```

## Sources

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

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