CVE-2018-3650
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedInsufficient 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe Bleach module in Intel Distribution for Python prior to version 2018 Update 2 contains an insufficient input validation vulnerability that allows unprivileged users to bypass URI sanitization. This could enable injection of malicious URI schemes (such as javascript:) into sanitized HTML content through a local attack vector.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2018= 2018CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if Intel Distribution for Python is installedRun `python -c "import intel_extension_for_pytorch; print(intel_extension_for_pytorch.__version__)" 2>/dev/null || python -c "import intel_distributed; print(intel_distributed.__version__)" 2>/dev/null || which idp 2>/dev/null || echo 'Not found'`. Alternatively, check for the Intel Python launcher: `which idp-python` or check the installation directory.Affected if The product is Intel Distribution for Python and the version is before 2018 Update 2, or equals 2018 (base release without update).
-
Determine the exact Intel Distribution for Python versionRun `idp --version 2>/dev/null` or check the installation path. Look for a version string that includes Update 2 or later. If only a year (2018) is shown without an update number, it is the base release and vulnerable.Affected if The version shown is '2018' without any Update number, or shows a version number less than 2018 Update 2.
-
Confirm the Bleach module versionRun `python -c "import bleach; print(bleach.__version__)"`. Intel Distribution for Python bundles a specific version of Bleach.Affected if The Bleach version is older than the version bundled with Intel Python 2018 Update 2, which contains the patched URI sanitization.
-
Check if URI sanitization or linkify is in useSearch codebase or configuration for usages of 'bleach' with 'linkify=True' or 'filters' parameter, or for allowed schemes configuration. Grep: `grep -r 'bleach\..*linkify' .` or `grep -r 'allowedSchemes' .`Affected if The Bleach library is being used with linkify enabled or with custom URI scheme filtering, enabling the bypass to inject malicious URI schemes like javascript:.
You are affected if Intel Distribution for Python version is 2018 (base) or any version prior to 2018 Update 2, and the Bleach module is used with URI sanitization or linkify features enabled.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data2018
Update Intel Distribution for Python to version 2018 Update 2 or later to obtain the patched Bleach module with proper URI sanitization validation.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-3650 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-3650 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data