Skip to content

GHSA-mj6m-246h-9w56 CVE-2022-25769

Improper regex in htaccess file

Critical Packagist
Severity
9.1 / 10
Critical · CVSS 3.1
Exploit chance (EPSS)
0.51%
Chance of exploitation in the next 30 days. Higher than 43.30% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-1284 Improper Validation of Specified Quantity in Input
Fix
3.3.5
Upgrade mautic/core to this version or later

Description

Impact

the default .htaccess file has some restrictions in the access to PHP files to only allow specific PHP files to be executed in the root of the application.

This logic isn't correct, as the regex in the second FilesMatch only checks the filename, not the full path.

Patches

Please upgrade to 3.3.5 or 4.2.0

Workarounds

No

References

For more information

If you have any questions or comments about this advisory:

Affected versions

Packagist

PackageVulnerableFixed in
mautic/core
< 3.3.5
3.3.5
mautic/core
>= 4.0.0, < 4.2.0
4.2.0

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

mautic/core Packagist → 3.3.5

composer
composer require mautic/core:^3.3.5

Severity breakdown

CVSS 3.1 9.1

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

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

Weakness

CWE-1284: Improper Validation of Specified Quantity in Input

The product receives input that is expected to specify a quantity (such as size or length), but it does not validate or incorrectly validates that the quantity has the required properties.

How to prevent it
  • Implementation: Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue." Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-5hvg-w58j-545m
Mautic has Stored Cross-Site Scripting (XSS) in Project Option Selector
Medium Also affects mautic/core
GHSA-7h65-whp7-rgqf
Mautic has Stored Cross-Site Scripting (XSS) in Projects Component
High Also affects mautic/core
GHSA-2jrw-c95w-h43g
Mautic has an Authorization Bypass in API v2 Endpoints
High Also affects mautic/core
GHSA-6r9h-4h75-7q4x
Mautic vulnerable to Path Traversal via Campaign Import
Critical Also affects mautic/core
GHSA-9fx4-7cmj-47vg
Mautic has Server-Side Template Injection (SSTI) in Theme Templates
Critical Also affects mautic/core
GHSA-jmv8-8j9j-rcpc
Mautic Focus component Vulnerable to SSRF
Medium Also affects mautic/core
GHSA-fcmw-wx57-9p75
Mautic has SQL Injection in API Contact Filtering
High Also affects mautic/core
GHSA-r5j5-q42h-fc93
Mautic is Vulnerable to SQL Injection through Contact Activity API Sorting
High Also affects mautic/core
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor