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

Summaryinfo

A vulnerability classified as problematic has been found in MySQL. This impacts an unknown function. This manipulation causes format string. This vulnerability is tracked as CVE-2008-3963. Moreover, an exploit is present. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability has been found in MySQL (Database Software) and classified as problematic. Affected by this vulnerability is some unknown processing. The manipulation with an unknown input leads to a format string vulnerability. The CWE definition for the vulnerability is CWE-134. The product uses a function that accepts a format string as an argument, but the format string originates from an external source. As an impact it is known to affect availability. The summary by CVE is:

MySQL 5.0 before 5.0.66, 5.1 before 5.1.26, and 6.0 before 6.0.6 does not properly handle a b (b single-quote single-quote) token, aka an empty bit-string literal, which allows remote attackers to cause a denial of service (daemon crash) by using this token in a SQL statement.

The bug was discovered 09/08/2008. The weakness was disclosed 09/10/2008 by Sergei Golubchik (Website). It is possible to read the advisory at debian.org. This vulnerability is known as CVE-2008-3963 since 09/09/2008. The exploitation appears to be easy. The attack can be launched remotely. Required for exploitation is a single authentication. Technical details are unknown but a public exploit is available.

It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 2 days. During that time the estimated underground price was around $5k-$25k. The vulnerability scanner Nessus provides a plugin with the ID 34765 (SuSE 10 Security Update : MySQL (ZYPP Patch Number 5618)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family SuSE Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 165638 (SUSE Enterprise Linux Security Update (SUSE-SR:2009:001)).

Upgrading to version 5.0.0.0 eliminates this vulnerability. A possible mitigation has been published 2 weeks after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at X-Force (45042), Exploit-DB (32348), Tenable (34765), SecurityFocus (BID 29106†) and OSVDB (48021†). The entries VDB-4033, VDB-45619, VDB-45239 and VDB-45178 are pretty similar. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.3
VulDB Meta Temp Score: 3.9

VulDB Base Score: 4.3
VulDB Temp Score: 3.9
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Format string
CWE: CWE-134 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
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: 34765
Nessus Name: SuSE 10 Security Update : MySQL (ZYPP Patch Number 5618)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
Nessus Port: 🔍

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

Qualys ID: 🔍
Qualys Name: 🔍

Exploit-DB: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

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

Upgrade: MySQL 5.0.0.0

Timelineinfo

03/28/2008 🔍
05/08/2008 +41 days 🔍
09/08/2008 +123 days 🔍
09/09/2008 +1 days 🔍
09/10/2008 +1 days 🔍
09/10/2008 +0 days 🔍
09/11/2008 +1 days 🔍
09/12/2008 +1 days 🔍
09/19/2008 +7 days 🔍
11/13/2008 +55 days 🔍
03/17/2015 +2315 days 🔍
12/22/2024 +3568 days 🔍

Sourcesinfo

Advisory: debian.org
Researcher: Sergei Golubchik
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2008-3963 (🔍)
GCVE (CVE): GCVE-0-2008-3963
GCVE (VulDB): GCVE-100-43987

OVAL: 🔍

X-Force: 45042
SecurityFocus: 29106 - MySQL MyISAM Table Privileges Secuity Bypass Vulnerability
Secunia: 31769
OSVDB: 48021 - CVE-2008-3963 - MySQL - Denial-Of-Service Issue
SecurityTracker: 1020858
Vulnerability Center: 19434 - MySQL Remote Denial of Service via an Empty Bit-String Literal in a SQL Statement, High
Vupen: ADV-2008-2554

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

Entryinfo

Created: 03/17/2015 16:11
Updated: 12/22/2024 23:48
Changes: 03/17/2015 16:11 (76), 08/16/2019 17:48 (12), 12/22/2024 23:48 (21)
Complete: 🔍
Cache ID: 216:0B6:103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!