# CVE-2024-6780: Improper permission control in com.android.server.telecom

> Improper permission control in the Android Telecom service allows attackers to access sensitive user information.

- **Severity:** Low 3.3 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Jul 2024
- **Updated:** 30 Oct 2024
- **Also known as:** GHSA-5w6v-768m-rvhm

## What is CVE-2024-6780?

CVE-2024-6780 is a low-severity missing authorization vulnerability in TECNO com.android.server.telecom, published on 16 Jul 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Improper permission control in the mobile application (com.android.server.telecom) may lead to user information security risks.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

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


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

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

## Is CVE-2024-6780 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-6780 is a low-severity missing authorization vulnerability in TECNO com.android.server.telecom, published on 16 Jul 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-6780 in the wild and no public exploit code.

Affected product: TECNO com.android.server.telecom. 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-6780/ (Markdown: https://insights.sbomify.com/CVE-2024-6780/index.md)
```

## Sources

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

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