ModSecurity up to 2.9.4/3.0.5 JSON Object denial of service
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in ModSecurity up to 2.9.4/3.0.5. Impacted is an unknown function of the component JSON Object Handler. Performing a manipulation results in denial of service. This vulnerability is known as CVE-2021-42717. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability was found in ModSecurity up to 2.9.4/3.0.5. It has been classified as problematic. This affects some unknown functionality of the component JSON Object Handler. The manipulation with an unknown input leads to a denial of service vulnerability. CWE is classifying the issue as CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. This is going to have an impact on availability.
The weakness was published 12/08/2021. The advisory is shared at trustwave.com. This vulnerability is uniquely identified as CVE-2021-42717 since 10/19/2021. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1499 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
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: Denial of serviceCWE: CWE-404
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
10/19/2021 🔍12/08/2021 🔍
12/08/2021 🔍
07/04/2025 🔍
Sources
Advisory: trustwave.comStatus: Not defined
CVE: CVE-2021-42717 (🔍)
GCVE (CVE): GCVE-0-2021-42717
GCVE (VulDB): GCVE-100-187665
scip Labs: https://www.scip.ch/en/?labs.20130913
Entry
Created: 12/08/2021 01:56Updated: 07/04/2025 01:12
Changes: 12/08/2021 01:56 (36), 12/10/2021 14:35 (1), 07/04/2025 01:12 (33)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.