Sun MySQL 4.1/5.0 sql_parse.cpp security check

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

A vulnerability classified as critical has been found in Sun MySQL 4.1/5.0 (Database Software). This affects an unknown code block of the file sql_parse.cpp. The manipulation with an unknown input leads to a security check vulnerability. CWE is classifying the issue as CWE-358. The product does not implement or incorrectly implements one or more security-relevant checks as specified by the design of a standardized algorithm, protocol, or technique. This is going to have an impact on confidentiality, and integrity. The summary by CVE is:

The check_scramble_323 function in MySQL 4.1.x before 4.1.3, and 5.0, allows remote attackers to bypass authentication via a zero-length scrambled string.

The bug was discovered 07/05/2004. The weakness was disclosed 07/05/2004 by Chris Anley with NGSSoftware Insight Security Research as not defined posting (Bugtraq). It is possible to read the advisory at securityfocus.com. This vulnerability is uniquely identified as CVE-2004-0627 since 07/06/2004. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details and a public exploit are known. The attack technique deployed by this issue is T1211 according to MITRE ATT&CK.

After 5 days, there has been an exploit disclosed. The exploit is shared for download at securiteam.com. It is declared as proof-of-concept. We expect the 0-day to have been worth approximately $5k-$25k. The vulnerability scanner Nessus provides a plugin with the ID 17691 (MySQL 4.1 < 4.1.3 Multiple Vulnerabilities), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Databases and running in the context r.

Upgrading to version 4.1.3 eliminates this vulnerability. Applying a patch is able to eliminate this problem. The bugfix is ready for download at mysql.com. The best possible mitigation is suggested to be upgrading to the latest version. A possible mitigation has been published even before and not after the disclosure of the vulnerability. Attack attempts may be identified with Snort ID 3665. Furthermore it is possible to detect and prevent this kind of attack with TippingPoint and the filter 2902.

The vulnerability is also documented in the databases at X-Force (16604), Tenable (17691) and Exploit-DB (311). Further details are available at ngssoftware.com. The entry 22548 is pretty similar.

Productinfo

Type

Vendor

Name

Version

License

Support

  • end of life

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB CVSS-B Score: 🔍
VulDB CVSS-BT Score: 🔍
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.5
VulDB Meta Temp Score: 5.9

VulDB Base Score: 6.5
VulDB Temp Score: 5.9
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
unlockunlockunlockunlockunlockunlock
unlockunlockunlockunlockunlockunlock
unlockunlockunlockunlockunlockunlock

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

NVD Base Score: 🔍

Exploitinginfo

Class: Security check
CWE: CWE-358
CAPEC: 🔍
ATT&CK: 🔍

Local: No
Remote: Yes

Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-Dayunlockunlockunlockunlock
Todayunlockunlockunlockunlock

Nessus ID: 17691
Nessus Name: MySQL 4.1 < 4.1.3 Multiple Vulnerabilities
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 52406
OpenVAS Name: FreeBSD Ports: mysql-server
OpenVAS File: 🔍
OpenVAS Family: 🔍

Exploit-DB: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍
Exploit Delay Time: 🔍

Upgrade: MySQL 4.1.3
Patch: mysql.com

Snort ID: 3665
TippingPoint: 🔍
SourceFire IPS: 🔍
ISS Proventia IPS: 🔍
PaloAlto IPS: 🔍
Fortigate IPS: 🔍

Timelineinfo

06/28/2004 🔍
07/05/2004 +7 days 🔍
07/05/2004 +0 days 🔍
07/05/2004 +0 days 🔍
07/05/2004 +0 days 🔍
07/06/2004 +1 days 🔍
07/06/2004 +0 days 🔍
07/06/2004 +0 days 🔍
07/10/2004 +3 days 🔍
07/26/2004 +16 days 🔍
12/06/2004 +133 days 🔍
01/07/2011 +2223 days 🔍
06/28/2019 +3094 days 🔍

Sourcesinfo

Vendor: oracle.com

Advisory: securityfocus.com⛔
Researcher: Chris Anley
Organization: NGSSoftware Insight Security Research
Status: Not defined

CVE: CVE-2004-0627 (🔍)
X-Force: 16604
Vulnerability Center: 4864 - Authentication Bypass in MySQL 4.1.x before 4.1.3 and 5.0, Medium
SecuriTeam: securiteam.com
SecurityFocus: 10654 - MySQL Authentication Bypass Vulnerability
Secunia: 12020 - MySQL Authentication Vulnerabilities, Moderately Critical
OSVDB: 7475 - MySQL Zero-length Scrambled String Crafted Packet Authentication Bypass

scip Labs: https://www.scip.ch/en/?labs.20161013
Misc.: 🔍
See also: 🔍

Entryinfo

Created: 07/06/2004 16:26
Updated: 06/28/2019 20:51
Changes: 07/06/2004 16:26 (106), 06/28/2019 20:51 (2)
Complete: 🔍

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!