Oracle MySQL Connectors up to 8.0.30 Connector/C++ information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.2 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Oracle MySQL Connectors up to 8.0.30. This vulnerability affects unknown code of the component Connector/C++. This manipulation causes information disclosure. This vulnerability is handled as CVE-2022-2097. The attack can be initiated remotely. There is not any exploit available.
Details
A vulnerability has been found in Oracle MySQL Connectors up to 8.0.30 (Database Software) and classified as critical. Affected by this vulnerability is an unknown code of the component Connector/C++. The manipulation with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality.
The weakness was released 10/19/2022 as Oracle Critical Patch Update Advisory - October 2022. The advisory is shared at oracle.com. This vulnerability is known as CVE-2022-2097. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
The vulnerability scanner Nessus provides a plugin with the ID 211174 (Fedora 37 : openssl (2022-1c20b4dde2)), which helps to determine the existence of the flaw in a target environment.
A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the vulnerability database at Tenable (211174). 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: 5.3VulDB Meta Temp Score: 5.2
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
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: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
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 |
Nessus ID: 211174
Nessus Name: Fedora 37 : openssl (2022-1c20b4dde2)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Patch: 919925673d6c9cfed3c1085497f5dfbbed5fc431
Timeline
06/16/2022 🔍10/19/2022 🔍
10/19/2022 🔍
10/19/2022 🔍
11/17/2024 🔍
Sources
Vendor: oracle.comAdvisory: Oracle Critical Patch Update Advisory - October 2022
Status: Confirmed
CVE: CVE-2022-2097 (🔍)
GCVE (CVE): GCVE-0-2022-2097
GCVE (VulDB): GCVE-100-211621
Entry
Created: 10/19/2022 08:30Updated: 11/17/2024 02:27
Changes: 10/19/2022 08:30 (39), 11/16/2022 21:08 (4), 11/16/2022 21:16 (17), 11/16/2022 21:28 (1), 06/22/2024 20:38 (16), 11/17/2024 02:27 (2)
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.