Oracle MySQL Enterprise Monitor up to 8.0.29 Monitoring toctou
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.8 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Oracle MySQL Enterprise Monitor up to 8.0.29. It has been rated as critical. Impacted is an unknown function of the component Monitoring. Performing a manipulation results in an unknown weakness. This vulnerability was named CVE-2022-23181. The attack needs to be approached locally. There is no available exploit. Upgrading the affected component is advised.
Details
A vulnerability, which was classified as critical, was found in Oracle MySQL Enterprise Monitor up to 8.0.29 (Database Software). This affects an unknown function of the component Monitoring. CWE is classifying the issue as CWE-367. The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check. This can cause the product to perform invalid actions when the resource is in an unexpected state. This is going to have an impact on confidentiality, integrity, and availability.
The weakness was presented 04/19/2022 as Oracle Critical Patch Update Advisory - April 2022. The advisory is shared at oracle.com. This vulnerability is uniquely identified as CVE-2022-23181. Neither technical details nor an exploit are publicly available.
The vulnerability scanner Nessus provides a plugin with the ID 211162 (Fedora 37 : tomcat (2022-30ce1cbe6e)), which helps to determine the existence of the flaw in a target environment.
Upgrading eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the databases at Tenable (211162) and EUVD (EUVD-2022-0937). 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
License
Website
- Vendor: https://www.oracle.com
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.0VulDB Meta Temp Score: 6.8
VulDB Base Score: 7.0
VulDB Temp Score: 6.7
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.0
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: ToctouCWE: CWE-367 / CWE-362
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 211162
Nessus Name: Fedora 37 : tomcat (2022-30ce1cbe6e)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Timeline
01/12/2022 🔍04/19/2022 🔍
04/19/2022 🔍
04/20/2022 🔍
03/15/2026 🔍
Sources
Vendor: oracle.comAdvisory: Oracle Critical Patch Update Advisory - April 2022
Status: Confirmed
CVE: CVE-2022-23181 (🔍)
GCVE (CVE): GCVE-0-2022-23181
GCVE (VulDB): GCVE-100-198093
EUVD: 🔍
Entry
Created: 04/20/2022 08:01Updated: 03/15/2026 17:17
Changes: 04/20/2022 08:01 (39), 04/26/2022 09:37 (2), 04/26/2022 09:42 (19), 11/17/2024 03:28 (16), 03/15/2026 17:17 (1)
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.