# CVE-2023-6540: Code injection in Lenovo Browser HD

> Attackers can inject code into Lenovo Android browsers to disclose sensitive user information.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 3 Jan 2024
- **Updated:** 17 Jun 2025
- **Also known as:** GHSA-8v3x-2g6f-gc4c

## What is CVE-2023-6540?

CVE-2023-6540 is a medium-severity code injection vulnerability in Lenovo Browser HD, published on 3 Jan 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A vulnerability was reported in the Lenovo Browser Mobile and Lenovo Browser HD Apps for Android that could allow an attacker to craft a payload that could result in the disclosure of sensitive information.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 2 products.


Products: Lenovo Browser Hd, Lenovo Browser Mobile.

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

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

## Is CVE-2023-6540 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-6540 is a medium-severity code injection vulnerability in Lenovo Browser HD, published on 3 Jan 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-6540 in the wild and no public exploit code.

Affected product: Lenovo Browser HD. 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-6540/ (Markdown: https://insights.sbomify.com/CVE-2023-6540/index.md)
```

## Sources

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

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