# CVE-2019-3665: Code Injection vulnerability


- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 3 Dec 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-mq78-57jv-92wc

## What is CVE-2019-3665?

CVE-2019-3665 is a medium-severity vulnerability in McAfee, LLC McAfee Web Advisor (WA), published on 3 Dec 2019. 

### Official description

Code Injection vulnerability in the web interface in McAfee Web Advisor (WA) prior to 4.1.1.48 allows remote unauthenticated attacker to allow the browser to render a website which Web Advisor would normally have blocked via a carefully crafted web site.

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

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

It affects 1 product.


Products: Mcafee Webadvisor.

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

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

## Is CVE-2019-3665 being exploited?

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

## Other vulnerabilities in McAfee, LLC McAfee Web Advisor (WA)

- [CVE-2022-0815](https://insights.sbomify.com/CVE-2022-0815/): McAfee WebAdvisor - Extension Fingerprinting vulnerability (medium 6.5)
- [CVE-2019-3666](https://insights.sbomify.com/CVE-2019-3666/): API Abuse Vulnerability (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-3665 is a medium-severity vulnerability in McAfee, LLC McAfee Web Advisor (WA), published on 3 Dec 2019. 
Exploitation: There is no known exploitation of CVE-2019-3665 in the wild and no public exploit code.

Affected product: McAfee, LLC McAfee Web Advisor (WA). 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-3665/ (Markdown: https://insights.sbomify.com/CVE-2019-3665/index.md)
```

## Sources

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

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