| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.9 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Chucky A. Ivey N.T. 1.1.0. It has been rated as critical. This impacts an unknown function of the file ticker.db.php. This manipulation causes memory corruption. This vulnerability appears as CVE-2006-1658. There is no available exploit.
Details
A vulnerability has been found in Chucky A. Ivey N.T. 1.1.0 and classified as critical. Affected by this vulnerability is an unknown function of the file ticker.db.php. The manipulation with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
Direct static code injection vulnerability in ticker.db.php in Chucky A. Ivey N.T. 1.1.0 allows remote administrators to insert arbitrary PHP code into the config file, which is included other N.T. scripts.
The weakness was presented 04/05/2006 by Aliaksandr Hartsuyeu (Website). The advisory is shared at vupen.com. This vulnerability is known as CVE-2006-1658 since 04/07/2006. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available.
It is declared as proof-of-concept. By approaching the search of inurl:ticker.db.php it is possible to find vulnerable targets with Google Hacking.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the databases at X-Force (25639), SecurityFocus (BID 17387†), OSVDB (24398†) and Secunia (SA19526†). See VDB-29532 for similar entry. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 6.9
VulDB Base Score: 7.3
VulDB Temp Score: 6.9
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: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Proof-of-Concept
Google Hack: 🔍
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
04/05/2006 🔍04/05/2006 🔍
04/05/2006 🔍
04/05/2006 🔍
04/07/2006 🔍
04/07/2006 🔍
03/12/2015 🔍
07/22/2018 🔍
Sources
Advisory: vupen.com⛔Researcher: Aliaksandr Hartsuyeu
Status: Not defined
CVE: CVE-2006-1658 (🔍)
GCVE (CVE): GCVE-0-2006-1658
GCVE (VulDB): GCVE-100-29533
X-Force: 25639 - N.T. ticker.db.php file include
SecurityFocus: 17387 - Chucky A. Ivey N.T. Index.PHP Multiple HTML Injection Vulnerabilities
Secunia: 19526 - N.T. Multiple Vulnerabilities, Moderately Critical
OSVDB: 24398 - N.T. ticker.db.php Arbitrary PHP Code Execution
Vupen: ADV-2006-1243
See also: 🔍
Entry
Created: 03/12/2015 12:19Updated: 07/22/2018 10:06
Changes: 03/12/2015 12:19 (55), 07/22/2018 10:06 (8)
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.