| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $0-$5k | 0.00 |
Summary
A vulnerability was found in MySQL MaxDB up to 7.5.00.16. It has been rated as problematic. The impacted element is the function IsAscii7. This manipulation causes denial of service.
This vulnerability is registered as CVE-2004-0931. Furthermore, an exploit is available.
Upgrading the affected component is advised.
Details
A vulnerability classified as problematic was found in MySQL MaxDB up to 7.5.00.16 (Database Software). Affected by this vulnerability is the function IsAscii7. The manipulation with an unknown input leads to a denial of service vulnerability. The CWE definition for the vulnerability is CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. As an impact it is known to affect availability. The summary by CVE is:
MySQL MaxDB before 7.5.00.18 allows remote attackers to cause a denial of service (crash) via an HTTP request to webdbm with high ASCII values in the Server field, which triggers an assert error in the IsAscii7 function.
The bug was discovered 08/16/2004. The weakness was published 10/07/2004 by Patrik Karlsson (Website). The advisory is shared at idefense.com. This vulnerability is known as CVE-2004-0931 since 10/04/2004. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details and also a exploit are known.
After before and not just, there has been an exploit disclosed. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 52 days. During that time the estimated underground price was around $0-$5k.
Upgrading to version bis 7.5.00.17 eliminates this vulnerability.
The vulnerability is also documented in the databases at X-Force (17633), SecurityFocus (BID 11346†), OSVDB (10532†) and Secunia (SA12756†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 4.8
VulDB Base Score: 5.3
VulDB Temp Score: 4.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Denial of serviceCWE: CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Proof-of-Concept
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: MaxDB bis 7.5.00.17
Timeline
08/16/2004 🔍10/04/2004 🔍
10/06/2004 🔍
10/07/2004 🔍
10/07/2004 🔍
10/07/2004 🔍
10/07/2004 🔍
12/31/2004 🔍
04/14/2015 🔍
06/22/2018 🔍
Sources
Advisory: idefense.com⛔Researcher: Patrik Karlsson
Status: Not defined
CVE: CVE-2004-0931 (🔍)
GCVE (CVE): GCVE-0-2004-0931
GCVE (VulDB): GCVE-100-22645
X-Force: 17633 - MaxDB IsAscii7 denial of service
SecurityFocus: 11346 - MySQL MaxDB WebDBM Server Name Denial of Service Vulnerability
Secunia: 12756 - MaxDB Two Vulnerabilities, Moderately Critical
OSVDB: 10532 - MySQL MaxDB webdbm Server Field DoS
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 04/14/2015 13:27Updated: 06/22/2018 07:51
Changes: 04/14/2015 13:27 (61), 06/22/2018 07:51 (7)
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.