LiveActive security incident?Get immediate response
CVE Record

CVE-2021-33391: An issue in HTACG HTML Tidy v5.7.28 allows attacker to execute arbitrary code via the -g option of the Clea...

An issue in HTACG HTML Tidy v5.7.28 allows attacker to execute arbitrary code via the -g option of the CleanNode() function in gdoc.c.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2021-33391 is reported as a critical flaw in HTACG HTML Tidy v5.7.28. If an affected deployment processes attacker-controlled content through the vulnerable -g path, the reported impact is arbitrary code execution. The public bundle does not identify a fixed version or complete affected-product metadata.

Executive priority

Treat as high-priority where HTML Tidy v5.7.28 is used in automated or externally reachable content processing. If the product is not present, business urgency is low. The main gap is incomplete public fix and affected-product metadata.

Technical view

The CVE describes a CWE-416 use-after-free in HTML Tidy v5.7.28 involving the -g option and CleanNode() in gdoc.c. CVSS 3.1 is 9.8 with network attack vector, low complexity, no privileges, and no user interaction. Public evidence is limited to CVE records and a GitHub issue.

Likely exposure

Most likely exposure is systems that include HTACG HTML Tidy v5.7.28 and invoke the -g option on untrusted or externally supplied HTML. The CVE record lacks CPEs and normalized affected-product data, so software inventory may require binary, package, and dependency searches.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Risk remains high because the CVSS vector indicates unauthenticated, low-complexity remote exploitation with full confidentiality, integrity, and availability impact if reachable.

Researcher notes

Key uncertainties are affected package naming, fixed versions, and practical reachability. The CVE asserts arbitrary code execution and CWE-416, but the provided sources do not include detailed root-cause analysis, proof of exploitation in the wild, or remediation confirmation.

Mitigation direction

  • Identify any HTACG HTML Tidy v5.7.28 deployments or embedded copies.
  • Avoid processing untrusted input with the -g option until vendor guidance is confirmed.
  • Check the upstream GitHub issue and CVE record for fixed-version guidance.
  • Restrict and sandbox services that run HTML Tidy against external content.
  • Monitor exposed content-processing services for crashes or unusual child-process behavior.

Validation and detection

  • Search asset and dependency inventories for HTML Tidy v5.7.28.
  • Review application code and jobs for use of the -g option.
  • Confirm whether untrusted HTML can reach affected processing paths.
  • Check CVE and upstream issue history for patch or workaround updates.
  • Document compensating controls if no vendor fix is available.
Prepared
Confidence
medium
Sources
3

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-416: 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
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-33391 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
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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
2Source 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
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2021-33391Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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
n/an/an/aListed
Weakness

CWE details

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

CWE-416 · source CWE mapping

Use After Free

Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.