Related Weaknesses
CWE-ID |
Weakness Name |
Source |
CWE-399 |
Category : Resource Management Errors Weaknesses in this category are related to improper management of system resources. |
|
Metrics
Metrics |
Score |
Severity |
CVSS Vector |
Source |
V2 |
5 |
|
AV:N/AC:L/Au:N/C:N/I:N/A:P |
[email protected] |
EPSS
EPSS is a scoring model that predicts the likelihood of a vulnerability being exploited.
EPSS Score
The EPSS model produces a probability score between 0 and 1 (0 and 100%). The higher the score, the greater the probability that a vulnerability will be exploited.
EPSS Percentile
The percentile is used to rank CVE according to their EPSS score. For example, a CVE in the 95th percentile according to its EPSS score is more likely to be exploited than 95% of other CVE. Thus, the percentile is used to compare the EPSS score of a CVE with that of other CVE.
Exploit information
Exploit Database EDB-ID : 15261
Publication date : 2010-10-14 22h00 +00:00
Author : Luigi Auriemma
EDB Verified : No
Source: http://aluigi.org/adv/soliddb_1-adv.txt
#######################################################################
Luigi Auriemma
Application: IBM solidDB
http://www-01.ibm.com/software/data/soliddb/
Versions: <= 6.5.0.3
Platforms: AIX, Linux, Solaris, Windows
Bug: Denial of Service
Exploitation: remote, versus server
Date: 15 Oct 2010
Author: Luigi Auriemma
e-mail:
[email protected]
web: aluigi.org
#######################################################################
1) Introduction
2) Bug
3) The Code
4) Fix
#######################################################################
===============
1) Introduction
===============
"IBM solidDB product family features relational, in-memory database
technology that delivers extreme speed, performing up to ten times
faster than conventional, disk-based databases."
#######################################################################
======
2) Bug
======
The solid.exe service listening on port 1315 can be crashed by an
external attacker through a malformed type of packet.
The bugged function is located at address 0063dc60 which is called
recursively if the packet contains a particular value between the range
of values 15001 and 15100 (switch 9).
The effects of the problem can be:
- stack exaustion by using over 14000 of these values so that all the
memory of the stack gets consumed by these recursive callings
- NULL pointer due to the usage of only one of these values where an
unused pointer (set to zero) is used in a comparison operation
- invalid memory access by using also another type of value after those
#######################################################################
===========
3) The Code
===========
http://aluigi.org/poc/soliddb_1.zip
https://gitlab.com/exploit-database/exploitdb-bin-sploits/-/raw/main/bin-sploits/15261.zip
#######################################################################
======
4) Fix
======
No fix.
#######################################################################
Products Mentioned
Configuraton 0
Ibm>>Soliddb >> Version To (including) 6.5.0.3
Ibm>>Soliddb >> Version 4.5.167
Ibm>>Soliddb >> Version 4.5.168
Ibm>>Soliddb >> Version 4.5.169
Ibm>>Soliddb >> Version 4.5.173
Ibm>>Soliddb >> Version 4.5.175
Ibm>>Soliddb >> Version 4.5.176
Ibm>>Soliddb >> Version 4.5.178
Ibm>>Soliddb >> Version 06.00.1018
Ibm>>Soliddb >> Version 6.0.1060
Ibm>>Soliddb >> Version 6.0.1061
Ibm>>Soliddb >> Version 6.0.1064
Ibm>>Soliddb >> Version 6.0.1065
Ibm>>Soliddb >> Version 6.0.1066
Ibm>>Soliddb >> Version 6.1
Ibm>>Soliddb >> Version 6.1.20
Ibm>>Soliddb >> Version 6.3.33
Ibm>>Soliddb >> Version 6.3.37
Ibm>>Soliddb >> Version 6.5.0.0
Ibm>>Soliddb >> Version 6.5.0.1
Ibm>>Soliddb >> Version 6.5.0.2
Ibm>>Soliddb >> Version 6.30.0039
Ibm>>Soliddb >> Version 6.30.0040
Ibm>>Soliddb >> Version 6.30.0044
Ibm>>Soliddb >> Version 06.30.0047
References