Oracle MySQL Server 8.0.34 and prior/8.1.0 Packaging double free
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.7 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Oracle MySQL Server 8.0.34 and prior/8.1.0. This affects an unknown part of the component Packaging. Performing a manipulation results in an unknown weakness. This vulnerability was named CVE-2023-39975. The attack may be initiated remotely. There is no available exploit.
Details
A vulnerability classified as critical has been found in Oracle MySQL Server 8.0.34 and prior/8.1.0 (Database Software). This affects some unknown functionality of the component Packaging. CWE is classifying the issue as CWE-415. The product calls free() twice on the same memory address, potentially leading to modification of unexpected memory locations. This is going to have an impact on confidentiality, integrity, and availability.
The weakness was presented 01/16/2024 as Oracle Critical Patch Update Advisory - January 2024. The advisory is shared at oracle.com. This vulnerability is uniquely identified as CVE-2023-39975. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 02/26/2026).
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
License
Website
- Vendor: https://www.oracle.com
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.8VulDB Meta Temp Score: 8.7
VulDB Base Score: 8.8
VulDB Temp Score: 8.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.8
NVD Vector: 🔍
ADP CISA Base Score: 8.8
ADP CISA 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: 🔍
Exploiting
Class: Double freeCWE: CWE-415 / CWE-119
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: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Patch: github.com
Timeline
08/07/2023 🔍01/16/2024 🔍
01/16/2024 🔍
01/17/2024 🔍
02/26/2026 🔍
Sources
Vendor: oracle.comAdvisory: Oracle Critical Patch Update Advisory - January 2024
Status: Confirmed
CVE: CVE-2023-39975 (🔍)
GCVE (CVE): GCVE-0-2023-39975
GCVE (VulDB): GCVE-100-251253
Entry
Created: 01/17/2024 09:10Updated: 02/26/2026 08:40
Changes: 01/17/2024 09:10 (38), 02/09/2024 20:22 (3), 02/09/2024 20:30 (1), 02/26/2026 08:40 (35)
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.