Oracle MySQL Server up to 5.1.66/5.1.28 Replication sql injection

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.6$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as problematic, has been found in Oracle MySQL Server up to 5.1.66/5.1.28. The impacted element is an unknown function of the component Replication. The manipulation leads to sql injection. This vulnerability is documented as CVE-2013-0375. The attack can be initiated remotely. There is not any exploit available. Applying a patch is the recommended action to fix this issue.

Detailsinfo

A vulnerability was found in Oracle MySQL Server up to 5.1.66/5.1.28 (Database Software) and classified as problematic. This issue affects an unknown functionality of the component Replication. The manipulation with an unknown input leads to a sql injection vulnerability. Using CWE to declare the problem leads to CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Impacted is confidentiality, and integrity. The summary by CVE is:

Unspecified vulnerability in the Server component in Oracle MySQL 5.1.66 and earlier, and 5.1.28 and earlier, allows remote authenticated users to affect confidentiality and integrity via unknown vectors related to Server Replication.

The weakness was released 01/15/2013 with Oracle as cpujan2013-1515902 as not defined advisory (Website). The advisory is shared at oracle.com. The public release was coordinated with Oracle. The identification of this vulnerability is CVE-2013-0375 since 12/07/2012. The exploitation is known to be easy. The attack may be initiated remotely. The successful exploitation needs a simple authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1505 for this issue.

The vulnerability scanner Nessus provides a plugin with the ID 64386 (CentOS 6 : mysql (CESA-2013:0219)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family CentOS Local Security Checks. The commercial vulnerability scanner Qualys is able to test this issue with plugin 19831 (Oracle MySQL January 2013 Critical Patch Update).

Applying a patch is able to eliminate this problem. A possible mitigation has been published immediately after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Tenable (64386), SecurityFocus (BID 57299†), Secunia (SA53372†) and Vulnerability Center (SBV-38084†). isc.sans.edu is providing further details. Entries connected to this vulnerability are available at VDB-5221, VDB-5212, VDB-5226 and VDB-5229. 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.9
VulDB Meta Temp Score: 5.8

VulDB Base Score: 5.4
VulDB Temp Score: 5.2
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 6.4
NVD Vector: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Sql injection
CWE: CWE-89 / CWE-74 / CWE-707
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: 64386
Nessus Name: CentOS 6 : mysql (CESA-2013:0219)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍

OpenVAS ID: 881586
OpenVAS Name: CentOS Update for mysql CESA-2013:0219 centos6
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Patch
Status: 🔍

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

Timelineinfo

12/07/2012 🔍
01/12/2013 +36 days 🔍
01/15/2013 +3 days 🔍
01/15/2013 +0 days 🔍
01/15/2013 +0 days 🔍
01/16/2013 +1 days 🔍
01/16/2013 +0 days 🔍
01/18/2013 +2 days 🔍
08/30/2013 +224 days 🔍
04/22/2021 +2792 days 🔍

Sourcesinfo

Vendor: oracle.com

Advisory: cpujan2013-1515902
Organization: Oracle
Status: Not defined
Confirmation: 🔍
Coordinated: 🔍

CVE: CVE-2013-0375 (🔍)
GCVE (CVE): GCVE-0-2013-0375
GCVE (VulDB): GCVE-100-7421

OVAL: 🔍

SecurityFocus: 57299 - Oracle January 2013 Critical Patch Update Multiple Vulnerabilities
Secunia: 53372 - Gentoo update for mysql, Moderately Critical
Vulnerability Center: 38084 - [cpujan2013-1515902] Oracle MySQL <=5.1.66 and <=5.5.28 Remote Unauthorized Data Insert \\ Update \\ Delete -CVE-2013-0375, Medium

Misc.: 🔍
See also: 🔍

Entryinfo

Created: 01/18/2013 09:45
Updated: 04/22/2021 11:14
Changes: 01/18/2013 09:45 (87), 04/23/2017 19:28 (5), 04/22/2021 11:14 (3)
Complete: 🔍
Cache ID: 216:DD9: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.

Do you want to use VulDB in your project?

Use the official API to access entries easily!