OWASP ModSecurity Core Rule Set up to 3.1.0 REQUEST-933-APPLICATION-ATTACK-PHP.conf incorrect regex ⚔ [Disputed]
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in OWASP ModSecurity Core Rule Set up to 3.1.0. It has been rated as problematic. The affected element is an unknown function of the file /rules/REQUEST-933-APPLICATION-ATTACK-PHP.conf. The manipulation leads to incorrect regex. This vulnerability is documented as CVE-2019-11390. The attack can be initiated remotely. There is not any exploit available. It is still unclear if this vulnerability genuinely exists.
Details
A vulnerability, which was classified as problematic, has been found in OWASP ModSecurity Core Rule Set up to 3.1.0. This issue affects an unknown function of the file /rules/REQUEST-933-APPLICATION-ATTACK-PHP.conf. The manipulation with an unknown input leads to a incorrect regex vulnerability. Using CWE to declare the problem leads to CWE-185. The product specifies a regular expression in a way that causes data to be improperly matched or compared. Impacted is availability. The summary by CVE is:
An issue was discovered in OWASP ModSecurity Core Rule Set (CRS) through 3.1.0. /rules/REQUEST-933-APPLICATION-ATTACK-PHP.conf allows remote attackers to cause a denial of service (ReDOS) by entering a specially crafted string with set_error_handler# at the beginning and nested repetition operators.
The bug was discovered 04/15/2019. The weakness was released 04/21/2019. The identification of this vulnerability is CVE-2019-11390 since 04/20/2019. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details of the vulnerability are known, but there is no available exploit.
The vulnerability was handled as a non-public zero-day exploit for at least 6 days. During that time the estimated underground price was around $0-$5k. The real existence of this vulnerability is still doubted at the moment.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Entries connected to this vulnerability are available at VDB-133932, VDB-133930, VDB-133929 and VDB-133928. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.3
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Incorrect regexCWE: CWE-185 / CWE-697
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
04/15/2019 🔍04/20/2019 🔍
04/21/2019 🔍
04/23/2019 🔍
08/05/2024 🔍
Sources
Advisory: 1358Status: Not defined
Disputed: 🔍
CVE: CVE-2019-11390 (🔍)
GCVE (CVE): GCVE-0-2019-11390
GCVE (VulDB): GCVE-100-133931
scip Labs: https://www.scip.ch/en/?labs.20130913
See also: 🔍
Entry
Created: 04/23/2019 08:46Updated: 08/05/2024 02:02
Changes: 04/23/2019 08:46 (54), 06/01/2020 09:48 (1), 09/06/2023 10:55 (4), 08/05/2024 02:02 (17)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.