Deltascripts Pro Publish 2.0 set_inc.php Stored memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as critical has been discovered in Deltascripts Pro Publish 2.0. Affected is an unknown function of the file set_inc.php. Such manipulation leads to memory corruption (Stored). This vulnerability is documented as CVE-2006-2129. There is not any exploit available.
Details
A vulnerability was found in Deltascripts Pro Publish 2.0. It has been rated as critical. Affected by this issue is an unknown functionality of the file set_inc.php. The manipulation with an unknown input leads to a memory corruption vulnerability (Stored). Using CWE to declare the problem leads to 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. Impacted is confidentiality, and integrity. CVE summarizes:
Direct static code injection vulnerability in Pro Publish 2.0 allows rmeote authenticated administrators to execute arbitrary PHP code by editing certain settings, which are stored in set_inc.php.
The weakness was released 04/30/2006 by Aliaksandr Hartsuyeu (Website). The advisory is shared for download at vupen.com. This vulnerability is handled as CVE-2006-2129 since 05/01/2006. The exploitation is known to be easy. The attack may be launched remotely. The successful exploitation needs a simple authentication. There are known technical details, but no exploit is available.
It is declared as proof-of-concept. By approaching the search of inurl:set_inc.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 (26149), SecurityFocus (BID 17762†), OSVDB (25128†) and Secunia (SA19882†). Entries connected to this vulnerability are available at VDB-29995, VDB-83895, VDB-83896 and VDB-83897. Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.4
VulDB Temp Score: 5.1
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
Name: StoredClass: Memory corruption / Stored
CWE: 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/30/2006 🔍05/01/2006 🔍
05/01/2006 🔍
05/01/2006 🔍
05/01/2006 🔍
03/12/2015 🔍
09/06/2017 🔍
Sources
Advisory: vupen.com⛔Researcher: Aliaksandr Hartsuyeu
Status: Not defined
CVE: CVE-2006-2129 (🔍)
GCVE (CVE): GCVE-0-2006-2129
GCVE (VulDB): GCVE-100-29996
X-Force: 26149 - Pro Publish set_inc.php file include
SecurityFocus: 17762 - DeltaScripts PHP Pro Publish Multiple SQL Injection Vulnerabilities
Secunia: 19882
OSVDB: 25128 - PHP Pro Publish set_inc.php Arbitrary PHP Code Execution
Vupen: ADV-2006-1578
See also: 🔍
Entry
Created: 03/12/2015 12:19Updated: 09/06/2017 14:54
Changes: 03/12/2015 12:19 (60), 09/06/2017 14:54 (1)
Complete: 🔍
Cache ID: 216:7B7:103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.