Oracle MySQL Enterprise Monitor up to 8.0.30 Monitoring: General expression language injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.6 | $5k-$25k | 0.00 |
Summary
A vulnerability identified as very critical has been detected in Oracle MySQL Enterprise Monitor up to 8.0.30. This affects an unknown part of the component Monitoring: General. The manipulation leads to an unknown weakness. This vulnerability is uniquely identified as CVE-2021-31805. The attack is possible to be carried out remotely. No exploit exists. You should upgrade the affected component.
Details
A vulnerability, which was classified as very critical, has been found in Oracle MySQL Enterprise Monitor up to 8.0.30 (Database Software). This issue affects some unknown functionality of the component Monitoring: General. Using CWE to declare the problem leads to CWE-917. The product constructs all or part of an expression language (EL) statement in a framework such as a Java Server Page (JSP) using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended EL statement before it is executed. Impacted is confidentiality, integrity, and availability.
The weakness was disclosed 07/19/2022 as Oracle Critical Patch Update Advisory - July 2022. The advisory is shared at oracle.com. The identification of this vulnerability is CVE-2021-31805. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 08/14/2022).
We expect the 0-day to have been worth approximately $25k-$100k.
Upgrading eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
- 8.0.0
- 8.0.1
- 8.0.2
- 8.0.3
- 8.0.4
- 8.0.5
- 8.0.6
- 8.0.7
- 8.0.8
- 8.0.9
- 8.0.10
- 8.0.11
- 8.0.12
- 8.0.13
- 8.0.14
- 8.0.15
- 8.0.16
- 8.0.17
- 8.0.18
- 8.0.19
- 8.0.20
- 8.0.21
- 8.0.22
- 8.0.23
- 8.0.24
- 8.0.25
- 8.0.26
- 8.0.27
- 8.0.28
- 8.0.29
- 8.0.30
License
Website
- Vendor: https://www.oracle.com
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 9.8VulDB Meta Temp Score: 9.6
VulDB Base Score: 9.8
VulDB Temp Score: 9.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
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: Expression language injectionCWE: CWE-917 / CWE-20
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: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Timeline
04/26/2021 🔍07/19/2022 🔍
07/19/2022 🔍
07/20/2022 🔍
08/14/2022 🔍
Sources
Vendor: oracle.comAdvisory: Oracle Critical Patch Update Advisory - July 2022
Status: Confirmed
CVE: CVE-2021-31805 (🔍)
GCVE (CVE): GCVE-0-2021-31805
GCVE (VulDB): GCVE-100-204437
Entry
Created: 07/20/2022 08:17Updated: 08/14/2022 03:35
Changes: 07/20/2022 08:17 (39), 08/14/2022 03:27 (2), 08/14/2022 03:35 (18)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.