Source: modsecurity-crs
Version: 3.3.9-1
X-Debbugs-CC: [email protected]
Severity: important
Tags: security upstream

Hi,

The following vulnerabilities were published for modsecurity-crs.

CVE-2026-61619[0]:
| The OWASP core rule set (CRS) is a set of generic attack detection
| rules for use with compatible web application firewalls. Prior to
| versions 3.3.10, 4.25.1, and 4.28.0, regular-expression denial of
| service (ReDoS) affects a shared regex-assembly include used to
| build 12 Unix RCE detection rules in CRS v4, and the same ambiguous
| pattern was present in the manually-assembled regexes in 4 rules in
| CRS v3.3. With a single, unauthenticated, crafted request, the
| generated pattern drives PCRE2 past its backtracking limit. When
| PCRE2 exceeds that limit, the @rx operator returns an error rather
| than a match result, which results in detection bypass and CPU
| denial of service. This issue has been patched in versions 3.3.10,
| 4.25.1, and 4.28.0.


CVE-2026-62971[1]:
| The OWASP core rule set (CRS) is a set of generic attack detection
| rules for use with compatible web application firewalls. Prior to
| versions 3.3.10, 4.25.1, and 4.28.0, CRS rules in the 921 (protocol-
| attack), 930 (LFI), 931 (RFI), 932 (RCE), 933 (PHP), 934 (generic),
| 941 (XSS), 942 (SQLi), and 943 (session-fixation) families inspect
| XML request bodies via the XPath expression XML:/*. That expression
| matches only element text nodes — it does not match XML attribute
| values. As a result, an attacker who places an attack payload inside
| an XML attribute (e.g. <a
| href="javascript:alert(1)=window.name"></a> or <a value="' OR 1=1
| --"></a>) bypasses CRS detection entirely. This is verified
| empirically against a local CRS test instance and against the public
| CRS sandbox. The bypass affects approximately 159 rules across 9
| rule files and applies at every paranoia level (PL1 through PL4),
| since the variable list is more or less shared across PLs. The 944
| (Java) family is the only one that correctly includes XML://@* in
| addition to XML:/* and is therefore unaffected. This issue has been
| patched in versions 3.3.10, 4.25.1, and 4.28.0.


If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2026-61619
    https://www.cve.org/CVERecord?id=CVE-2026-61619
[1] https://security-tracker.debian.org/tracker/CVE-2026-62971
    https://www.cve.org/CVERecord?id=CVE-2026-62971

Regards,
Salvatore

Reply via email to