LiveActive security incident?Get immediate response
CVE Record

CVE-2021-4305: Woorank robots-txt-guard patterns.js makePathPattern redos

A vulnerability was found in Woorank robots-txt-guard. It has been rated as problematic. Affected by this issue is the function makePathPattern of the file lib/patterns.js. The manipulation of the argument pattern leads to inefficient regular expression complexity. The exploit has been disclosed to the public and may be used. The name of the patch is c03827cd2f9933619c23894ce7c98401ea824020. It is recommended to apply a patch to fix this issue. The identifier of this vulnerability is VDB-217448.

LowCVSS 3.5Not KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

CVE-2021-4305 is a denial-of-service weakness in Woorank robots-txt-guard. A crafted pattern can make its regular expression processing inefficient, consuming CPU and reducing availability. The published severity is low because impact is limited to availability and requires adjacent access plus low privileges.

Executive priority

Treat this as a low-priority availability risk unless the library is exposed to untrusted pattern input in a sensitive service. Patch during normal maintenance, but prioritize faster if robots parsing sits on a public or business-critical request path.

Technical view

The issue affects makePathPattern in lib/patterns.js and is classified as CWE-1333, inefficient regular expression complexity. Manipulating the pattern argument can trigger ReDoS behavior. CVSS v3.1 is 3.5 with no confidentiality or integrity impact and low availability impact. A patch commit is identified as c03827cd2f9933619c23894ce7c98401ea824020.

Likely exposure

Exposure is likely limited to applications using Woorank robots-txt-guard where a low-privileged or adjacent actor can influence pattern input. The source bundle does not identify exact affected versions, package ranges, or downstream products.

Exploitation context

The vulnerability entry says exploit details were publicly disclosed and may be used. There is no KEV listing and no provided source confirms active exploitation in the wild.

Researcher notes

Key gaps are version range and real-world package adoption. Focus analysis on how pattern reaches makePathPattern, whether input is attacker-controlled, and whether resource limits contain ReDoS effects. Do not assume active exploitation beyond public disclosure evidence.

Mitigation direction

  • Inventory applications using Woorank robots-txt-guard.
  • Apply the vendor patch commit or a vendor-confirmed fixed release.
  • Avoid passing untrusted pattern values into robots-txt-guard until patched.
  • Add timeouts or resource controls around pattern processing where feasible.
  • Monitor vendor and repository guidance for affected version details.

Validation and detection

  • Check dependency manifests and lockfiles for robots-txt-guard usage.
  • Confirm deployed source includes commit c03827cd2f9933619c23894ce7c98401ea824020 or later vendor fix.
  • Review call sites for user-controlled pattern input.
  • Run regression tests for malformed long patterns without exposing production services.
  • Monitor logs and CPU metrics for unusual availability degradation.
Prepared
Confidence
medium
Sources
6

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-2021-4305 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
Low
CVSS
3.5 (3.1)
Known Exploited
No
Published

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

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
5Source 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
3.5CVSS 3.1LowCVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L2.11.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

3.5Low
CVSS 3.1 vector shape for CVE-2021-4305Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Woorankrobots-txt-guardn/aListed
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.