# CVE-2018-3650: Cross-site scripting in Intel Distribution for Python

> An attacker can bypass URI sanitization in the Bleach module of Intel Distribution for Python, potentially enabling cross-site scripting attacks.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Aug 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-v5j7-m2vx-ghr9

## What is CVE-2018-3650?

CVE-2018-3650 is a high-severity cross-site scripting vulnerability in Intel Distribution for Python, published on 1 Aug 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Insufficient Input Validation in Bleach module in INTEL Distribution for Python versions prior to IDP 2018 Update 2 allows unprivileged user to bypass URI sanitization via local vector.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2018-3650?

It affects 1 product.


Products: Intel Distribution for Python.

## How do I fix CVE-2018-3650?

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

## Is CVE-2018-3650 being exploited?

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

## Other vulnerabilities in Intel Distribution for Python

- [CVE-2022-28696](https://insights.sbomify.com/CVE-2022-28696/): Privilege escalation in Intel(R) Distribution for Python (high 7.8)
- [CVE-2018-12175](https://insights.sbomify.com/CVE-2018-12175/): Privilege escalation in Intel(R) Distribution for Python 2018 (high 7.8)
- [CVE-2022-26032](https://insights.sbomify.com/CVE-2022-26032/): Privilege escalation in Intel(R) Distribution for Python programming language for Intel(R) oneAPI Toolkits (medium 6.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-3650 and fix it if it is affected.

What it is: CVE-2018-3650 is a high-severity cross-site scripting vulnerability in Intel Distribution for Python, published on 1 Aug 2018. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-3650 in the wild and no public exploit code.

Affected product: Intel Distribution for Python. 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-2018-3650/ (Markdown: https://insights.sbomify.com/CVE-2018-3650/index.md)
```

## Sources

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

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