# CVE-2023-38292: Certain software builds for the TCL 20XE Android device contain a vulnerable, pre-installed app with a package name of com.tct.gcs.hiddenmen


- **Severity:** High 8.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 22 Apr 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-59xw-4jqj-crwp

## What is CVE-2023-38292?

CVE-2023-38292 is a high-severity vulnerability in n/a, published on 22 Apr 2024. 

### Official description

Certain software builds for the TCL 20XE Android device contain a vulnerable, pre-installed app with a package name of com.tct.gcs.hiddenmenuproxy (versionCode='2', versionName='v11.0.1.0.0201.0') that allows local third-party apps to programmatically perform a factory reset due to inadequate access control. No permissions or special privileges are necessary to exploit the vulnerability in the com.tct.gcs.hiddenmenuproxy app. No user interaction is required beyond installing and running a third-party app. The software build fingerprints for each confirmed vulnerable build are as follows: TCL/5087Z_BO/Doha_TMO:11/RP1A.200720.011/PB7I-0:user/release-keys and TCL/5087Z_BO/Doha_TMO:11/RP1A.200720.011/PB83-0:user/release-keys. This malicious app sends a broadcast intent to the exported com.tct.gcs.hiddenmenuproxy/.rtn.FactoryResetReceiver receiver component, which initiates a programmatic factory reset.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2023-38292?


## How do I fix CVE-2023-38292?

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

## Is CVE-2023-38292 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-38292 and fix it if it is affected.

What it is: CVE-2023-38292 is a high-severity vulnerability in n/a, published on 22 Apr 2024. 
Exploitation: There is no known exploitation of CVE-2023-38292 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-2023-38292/ (Markdown: https://insights.sbomify.com/CVE-2023-38292/index.md)
```

## Sources

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

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