CWE-1333: Inefficient Regular Expression Complexity Skip to content

Security weakness

CWE-1333 Inefficient Regular Expression Complexity

A base-level weakness that can lead to downtime and lost sales. Here is what it is, what it can cost you and how to close it.

  • Senior security engineers
  • 540+ projects delivered
  • Reply within one business day

Quick answer

What is CWE-1333?

Inefficient Regular Expression Complexity: The product uses a regular expression with a worst-case computational complexity that is inefficient and possibly exponential.

Business impact

What CWE-1333 could cost your business

MITRE documents what this weakness can do. Here is what that means for a website, store or app.

Availability

Downtime and lost sales

Crashes, slowdowns or exhausted resources can take your site, store or app offline.

  • DoS: Resource Consumption (CPU)

Free security check

Is CWE-1333 hiding in your site?

A senior engineer checks your site, store or app for this weakness and the rest of the CWE Top 25, then sends a prioritized fix plan within one business day. No obligation.

Official definition

How MITRE defines CWE-1333

Inefficient Regular Expression Complexity

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

Also known as: ReDoS, Regular Expression Denial of Service, Catastrophic backtracking

Weakness ID
CWE-1333
Type
Base
Status
Draft
Likelihood of exploit
High
Applies to
Go
Introduced during
Implementation

Prevention

How to fix CWE-1333, phase by phase

Every mitigation from the CWE entry, in the order a project runs: plan, build, test, operate.

  1. 01

    Architecture and Design

    • Use regular expressions that do not support backtracking, e.g. by removing nested quantifiers.
  2. 02

    Implementation

    • Do not use regular expressions with untrusted input. If regular expressions must be used, avoid using backtracking in the expression.
    • Limit the length of the input that the regular expression will process.
  3. 03

    System Configuration

    • 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.

Detection and evidence

How CWE-1333 is found, and where it has hit

The testing methods MITRE recommends, and real vulnerabilities this weakness has caused.

How it is detected

  • Automated Static AnalysisAutomated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then.

Real vulnerabilities it caused

  • CVE-2020-5243server allows ReDOS with crafted User-Agent strings, due to overlapping capture groups that cause excessive backtracking.
  • CVE-2021-21317npm package for user-agent parser prone to ReDoS due to overlapping capture groups
  • CVE-2019-16215Markdown parser uses inefficient regex when processing a message, allowing users to cause CPU consumption and delay preventing processing of other messages.
  • CVE-2019-6785Long string in a version control product allows DoS due to an inefficient regex.
  • CVE-2019-12041Javascript code allows ReDoS via a long string due to excessive backtracking.
  • CVE-2015-8315ReDoS when parsing time.

How we fix it

From finding to fixed: how Codefreex closes CWE-1333

  1. 01

    Scan and confirm

    We test your site, store or app for this weakness and the rest of the CWE Top 25 with automated scanning and manual review, and confirm what is actually exploitable.

  2. 02

    Fix at the source

    We change the code, configuration or dependency that causes it, not just the symptom, and plan the changes to avoid downtime.

  3. 03

    Verify the fix

    We retest every finding, check that nothing else broke and hand you a short report you can share with your team, client or auditor.

  4. 04

    Keep it fixed

    Updates, monitoring and maintenance so the weakness does not return with the next plugin, theme, app or code change.

Related weaknesses

FAQ

CWE-1333: FAQs

Short answers for owners and developers. Not sure whether your site is affected? Ask us to check.

What is CWE-1333?

CWE-1333, “Inefficient Regular Expression Complexity”, is a software weakness catalogued by MITRE in the Common Weakness Enumeration. The product uses a regular expression with a worst-case computational complexity that is inefficient and possibly exponential.

How serious is CWE-1333?

MITRE rates the likelihood of exploit as High. It can affect availability, with impacts such as dos: resource consumption (cpu). The real risk depends on where the weakness sits and what data or functions it exposes.

How do you prevent CWE-1333?

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.

Can Codefreex check my site for CWE-1333?

Yes. A senior engineer reviews your site, store or app for CWE-1333 and the rest of the CWE Top 25, confirms what is exploitable and sends a prioritized fix plan within one business day. Start with the free security check form on this page.

Which technologies does CWE-1333 affect?

MITRE lists it as applicable to Go. In practice any software that matches the weakness description can be affected, including custom code, plugins, themes and third-party libraries.

Free security check

Find out if CWE-1333 affects your site

Send your URL. A senior engineer checks for this weakness and the rest of the CWE Top 25, and replies within one business day with what to fix first.

  • A senior strategist reviews your request, not a sales bot
  • Clear scope, timeline and estimate within one business day
  • Free 30-minute discovery call, no obligation
  • NDA available on request

Weakness data from the Common Weakness Enumeration (CWE®) version 5.0, Copyright © 2006–2026, The MITRE Corporation. CWE is free to use by any organization or individual for any research, development, and/or commercial purposes under the CWE Terms of Use. CWE is a registered trademark of The MITRE Corporation. The business impact, risk profile and plain-English guidance on this page are written by Codefreex and are general information, not a security assessment of your system.