Oracle MySQL Server up to 8.0.31 InnoDB

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.4$0-$5k0.00

Summaryinfo

A vulnerability has been found in Oracle MySQL Server up to 8.0.31 and classified as critical. This affects an unknown part of the component InnoDB. Performing a manipulation results in an unknown weakness. This vulnerability is identified as CVE-2023-21869. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability classified as critical has been found in Oracle MySQL Server up to 8.0.31 (Database Software). This affects an unknown part of the component InnoDB. This is going to have an impact on integrity, and availability.

The weakness was released 01/17/2023 as Oracle Critical Patch Update Advisory - January 2023. The advisory is shared at oracle.com. This vulnerability is uniquely identified as CVE-2023-21869. Neither technical details nor an exploit are publicly available.

The vulnerability scanner Nessus provides a plugin with the ID 236677 (Alibaba Cloud Linux 3 : 0081: mysql:8.0 (ALINUX3-SA-2023:0081)), 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 (236677). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.5
VulDB Meta Temp Score: 5.4

VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍

CNA Base Score: 5.5
CNA Vector (Oracle): 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Unknown
CWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 236677
Nessus Name: Alibaba Cloud Linux 3 : 0081: mysql:8.0 (ALINUX3-SA-2023:0081)

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Timelineinfo

12/17/2022 🔍
01/17/2023 +31 days 🔍
01/17/2023 +0 days 🔍
01/18/2023 +1 days 🔍
05/18/2025 +851 days 🔍

Sourcesinfo

Vendor: oracle.com

Advisory: Oracle Critical Patch Update Advisory - January 2023
Status: Confirmed

CVE: CVE-2023-21869 (🔍)
GCVE (CVE): GCVE-0-2023-21869
GCVE (VulDB): GCVE-100-218781

Entryinfo

Created: 01/18/2023 07:28
Updated: 05/18/2025 12:05
Changes: 01/18/2023 07:28 (38), 02/14/2023 02:51 (2), 02/14/2023 03:00 (11), 02/14/2023 03:07 (1), 05/18/2025 12:05 (22)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you need the next level of professionalism?

Upgrade your account now!