# CVE-2019-16371: Cross-site request forgery in n/a

> Attackers can steal LastPass credentials via clickjacking on crafted websites, requiring users to update the browser extension.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/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:** 16 Sep 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-36f7-g2v6-4rj3

## What is CVE-2019-16371?

CVE-2019-16371 is a high-severity vulnerability in n/a, published on 16 Sep 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

LogMeIn LastPass before 4.33.0 allows attackers to construct a crafted web site that captures the credentials for a victim's account on a previously visited web site, because do_popupregister can be bypassed via clickjacking.

Weakness: CWE-1021 (Improper Restriction of Rendered UI Layers or Frames)

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

It affects 1 product.


Products: Logmein Lastpass.

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

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

## Is CVE-2019-16371 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-10193](https://insights.sbomify.com/CVE-2018-10193/): Denial of service in n/a (high 7.5)
- [CVE-2013-5113](https://insights.sbomify.com/CVE-2013-5113/): Weak cryptography in n/a (medium 6.8)
- [CVE-2013-5114](https://insights.sbomify.com/CVE-2013-5114/): Security feature bypass in n/a (medium 6.1)
- [CVE-2020-35207](https://insights.sbomify.com/CVE-2020-35207/): Auth bypass in n/a (medium 5.7)
- [CVE-2020-35208](https://insights.sbomify.com/CVE-2020-35208/): Auth bypass in n/a (medium 5.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-16371 is a high-severity vulnerability in n/a, published on 16 Sep 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-16371 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-2019-16371/ (Markdown: https://insights.sbomify.com/CVE-2019-16371/index.md)
```

## Sources

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

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