LiveActive security incident?Get immediate response
CVE Record

CVE-2020-6817: bleach.clean behavior parsing style attributes could result in a regular expression denial of service (ReDoS).

bleach.clean behavior parsing style attributes could result in a regular expression denial of service (ReDoS). Calls to bleach.clean with an allowed tag with an allowed style attribute are vulnerable to ReDoS. For example, bleach.clean(..., attributes={'a': ['style']}).

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This issue can let untrusted HTML tie up an application that uses Mozilla Bleach sanitization with style attributes enabled. The business impact is availability: affected services could slow down or become unavailable when processing crafted input. The source bundle does not identify active exploitation or a fixed version.

Executive priority

Treat as a high-priority availability risk for internet-facing services that process user-supplied HTML with Bleach. Prioritize validation first because exposure depends on a specific configuration: bleach.clean allowing style attributes.

Technical view

CVE-2020-6817 is a regular expression denial-of-service issue in bleach.clean style-attribute parsing. Calls are vulnerable when an allowed tag also permits the style attribute, such as attributes permitting style on links. CVSS 3.1 is 7.5, reflecting unauthenticated network-triggerable availability impact.

Likely exposure

Exposure is most likely in Python applications using Mozilla Bleach to sanitize user-controlled HTML while allowing style attributes on permitted tags. The bundle lists affected versions as unspecified, so teams must compare deployed Bleach versions and usage patterns against vendor guidance.

Exploitation context

The bundle marks KEV as false and provides no cited evidence of active exploitation. The CVSS vector indicates network access, low complexity, no privileges, and no user interaction, but that is risk context, not proof of exploitation in the wild.

Researcher notes

The source bundle is limited: it names the vulnerable behavior, CWE-1333, CVSS, and vulnerable configuration, but not affected version ranges, fixed releases, or exploit observations. Avoid broad product claims beyond Mozilla Bleach and the documented bleach.clean style-attribute condition.

Mitigation direction

  • Check Mozilla/GitHub advisory for affected and fixed Bleach versions.
  • Upgrade Mozilla Bleach according to vendor guidance when a fixed version is confirmed.
  • Remove style from allowed attributes where business functionality does not require it.
  • Limit untrusted HTML processing exposure behind existing abuse controls.
  • Monitor application latency and worker saturation around HTML sanitization paths.

Validation and detection

  • Inventory applications and services that depend on Mozilla Bleach.
  • Review bleach.clean usage for allowed style attributes on permitted tags.
  • Trace whether user-controlled HTML can reach those sanitization calls.
  • Compare installed Bleach versions against vendor advisory details.
  • Confirm tests cover sanitization paths that allow style attributes.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-1333: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-6817 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2020-6817Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
MozillaMozilla BleachunspecifiedListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-1333 · source CWE mapping

Inefficient Regular Expression Complexity

Inefficient Regular Expression Complexity represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.