# CVE-2024-3701: Improper Authentication in com.transsion.kolun.aiservice

> Attackers can exploit missing authentication in the TECNO AI service app to perform malicious actions and affect system services.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Apr 2024
- **Updated:** 21 Aug 2024
- **Also known as:** GHSA-27r2-x487-q675

## What is CVE-2024-3701?

CVE-2024-3701 is a critical missing authorization vulnerability in TECNO com.transsion.kolun.aiservice, published on 15 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The system application (com.transsion.kolun.aiservice) component does not perform an authentication check, which allows attackers to perform malicious exploitations and affect system services.

Weakness: CWE-287 (Improper Authentication), CWE-306 (Missing Authentication for Critical Functionality)

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

It affects 1 product.


Products: Tecno Hios.

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

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

## Is CVE-2024-3701 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-3701 is a critical missing authorization vulnerability in TECNO com.transsion.kolun.aiservice, published on 15 Apr 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-3701 in the wild and no public exploit code.

Affected product: TECNO com.transsion.kolun.aiservice. 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-3701/ (Markdown: https://insights.sbomify.com/CVE-2024-3701/index.md)
```

## Sources

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

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