CWE-1333: Inefficient Regular Expression Complexity

BaseDraftExploit Likelihood: High

The product uses a regular expression with a worst-case computational complexity that is inefficient and possibly exponential.

View on MITRE
Back to CWE Lookup

Technical Details

Structure
Simple
Vulnerability Mapping
ALLOWED

Applicable To

Languages
Not Language-Specific
Platforms

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-1333 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-1333, Inefficient Regular Expression Complexity, throughout the product lifecycle. Derive review questions, static or dynamic checks, and negative tests from the CWE's causal behavior; define the components and lifecycle stages each check covers; and retain findings with enough evidence to distinguish the root cause from symptoms and impacts. Track escapes and false negatives, then improve the verification plan after every confirmed occurrence.

NIST SP 800-218 Secure Software Development FrameworkNational Institute of Standards and Technology

Address Inefficient Regular Expression Complexity during Architecture and Design

MITRE associates mitigation with Architecture and Design, System Configuration, and Implementation; documented detection approaches include Automated Static Analysis; recorded impacts include DoS: Resource Consumption (CPU). Use these source-defined anchors to turn CWE-1333 into implementation, review, and verification checks for the affected component.

CWE-1333: Inefficient Regular Expression ComplexityMITRE CWE

Triage CWE-1333 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-1333, Inefficient Regular Expression Complexity, has evidence of exploitation in the wild. Confirm the CVE-to-CWE root-cause mapping independently before attaching the example, then capture the affected product, required action, and remediation deadline. A missing KEV match is not evidence that the weakness is unexploited, and a KEV entry must not be generalized to every occurrence of this CWE.

Known Exploited Vulnerabilities CatalogCybersecurity and Infrastructure Security Agency

Apply precise root-cause mapping to CWE-1333

Apply MITRE's full root-cause mapping guidance when using CWE-1333, Inefficient Regular Expression Complexity. Separate weakness language from attacker prerequisites and technical impact, check the entry's abstraction and vulnerability-mapping notes, and prefer the most specific Base or Variant supported by the evidence. Record the rejected alternatives and require an independent review before the mapping is used for remediation trends or program metrics.

CVE to CWE Root Cause Mapping GuidanceMITRE CWE

Validate CWE-1333 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-1333, Inefficient Regular Expression Complexity. Confirm the finding describes the causal weakness rather than an impact or attack pattern, compare the abstraction and mapping notes with plausible alternatives, and have a second reviewer challenge the selection. Preserve the evidence and reasoning so recurring defects can be measured against one consistent identifier.

CVE to CWE Root Cause Mapping Quick TipsMITRE CWE

Frequently Asked Questions

What is CWE-1333: Inefficient Regular Expression Complexity?+

CWE-1333: Inefficient Regular Expression Complexity is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product uses a regular expression with a worst-case computational complexity that is inefficient and possibly exponential.

What are the security consequences of Inefficient Regular Expression Complexity?+

If exploited, CWE-1333 (Inefficient Regular Expression Complexity) it can compromise Availability, leading to outcomes such as DoS: Resource Consumption (CPU).

How do you prevent or mitigate Inefficient Regular Expression Complexity?+

Recommended mitigations for CWE-1333 include: Use regular expressions that do not support backtracking, e.g. by removing nested quantifiers. Set backtracking limits in the configuration of the regular expression implementation, such as PHP's pcre.backtrack_limit. Also consider limits on execution time for the process. Do not use regular expressions with untrusted input. If regular expressions must be used, avoid using backtracking in the expression.

Which programming languages are affected by Inefficient Regular Expression Complexity?+

CWE-1333 commonly affects Not Language-Specific. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.

What are real-world examples of Inefficient Regular Expression Complexity?+

MITRE documents real CVEs mapped to CWE-1333, including CVE-2020-5243, CVE-2021-21317, CVE-2019-16215, CVE-2019-6785 and CVE-2019-12041. You can look up the full details of each CVE, including CVSS scores and remediation guidance, on our CVE Lookup tool.

What is the difference between a CWE and a CVE?+

A CWE (Common Weakness Enumeration) like CWE-1333 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.

Learn More

Advertisement