# CVE-2019-6166: Cross-site request forgery in Service Bridge

> Cross-site request forgery in Lenovo Service Bridge allows attackers to perform unauthorized actions on behalf of the user.

- **Severity:** Medium 5.4 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L`)
- **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:** 26 Jun 2019
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-fxv3-4v9h-4x8v

## What is CVE-2019-6166?

CVE-2019-6166 is a medium-severity vulnerability in Lenovo Service Bridge, published on 26 Jun 2019. 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 reported in Lenovo Service Bridge before version 4.1.0.1 could allow cross-site request forgery.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2019-6166?

It affects 1 product.


Products: Lenovo Service Bridge.

## How do I fix CVE-2019-6166?

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

## Is CVE-2019-6166 being exploited?

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

## Other vulnerabilities in Lenovo Service Bridge

- [CVE-2019-6167](https://insights.sbomify.com/CVE-2019-6167/): Code injection in Service Bridge (high 8.8)
- [CVE-2019-6168](https://insights.sbomify.com/CVE-2019-6168/): Code injection in Service Bridge (high 8.8)
- [CVE-2019-6169](https://insights.sbomify.com/CVE-2019-6169/): Information disclosure in Service Bridge (medium 6.5)
- [CVE-2026-1636](https://insights.sbomify.com/CVE-2026-1636/): Privilege escalation in Service Bridge (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-6166 and fix it if it is affected.

What it is: CVE-2019-6166 is a medium-severity vulnerability in Lenovo Service Bridge, published on 26 Jun 2019. 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-2019-6166 in the wild and no public exploit code.

Affected product: Lenovo Service Bridge. 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-2019-6166/ (Markdown: https://insights.sbomify.com/CVE-2019-6166/index.md)
```

## Sources

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

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