# CVE-2024-41999: Security feature bypass in Smart-tab Android app

> An attacker with physical access can exploit active debug code to escalate privileges, modify settings, or spoof devices in the Smart-tab Android app.

- **Severity:** Medium 6.8 (`CVSS:3.0/AV:P/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Sep 2024
- **Updated:** 30 Sep 2024
- **Also known as:** GHSA-m27q-cmfx-vgvc

## What is CVE-2024-41999?

CVE-2024-41999 is a medium-severity vulnerability in TECHNO SUPPORT COMPANY Smart-tab Android app, published on 30 Sep 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Smart-tab Android app installed April 2023 or earlier contains an active debug code vulnerability. If this vulnerability is exploited, an attacker with physical access to the device may exploit the debug function to gain access to the OS functions, escalate the privilege, change the device's settings, or spoof devices in other rooms.

Weakness: CWE-489 (Active Debug Code)

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


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

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

## Is CVE-2024-41999 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-41999 is a medium-severity vulnerability in TECHNO SUPPORT COMPANY Smart-tab Android app, published on 30 Sep 2024. 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-41999 in the wild and no public exploit code.

Affected product: TECHNO SUPPORT COMPANY Smart-tab Android app. 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-41999/ (Markdown: https://insights.sbomify.com/CVE-2024-41999/index.md)
```

## Sources

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

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