IDevSpot PhpLinkExchange 1.0 bits_listings.php svr_rootPhpStart memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.9 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in IDevSpot PhpLinkExchange 1.0. This affects an unknown part of the file bits_listings.php. The manipulation of the argument svr_rootPhpStart leads to memory corruption. This vulnerability is listed as CVE-2006-4741. In addition, an exploit is available.
Details
A vulnerability was found in IDevSpot PhpLinkExchange 1.0 and classified as critical. This issue affects an unknown functionality of the file bits_listings.php. The manipulation of the argument svr_rootPhpStart with an unknown input leads to a memory corruption vulnerability. 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, integrity, and availability. The summary by CVE is:
PHP remote file inclusion vulnerability in bits_listings.php in IDevSpot PhpLinkExchange 1.0 allows remote attackers to execute arbitrary code via the svr_rootPhpStart parameter.
The weakness was presented 09/13/2006 by S3rv3r_hack3r (Website). It is possible to read the advisory at securityfocus.com. The identification of this vulnerability is CVE-2006-4741 since 09/13/2006. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details as well as a public exploit are known.
A public exploit has been developed in Perl. The exploit is available at securityfocus.com. It is declared as proof-of-concept. By approaching the search of inurl:bits_listings.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 vulnerability database at SecurityFocus (BID 19931†). See VDB-32244 for similar entry. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
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: 🔍
Access: Public
Status: Proof-of-Concept
Programming Language: 🔍
Download: 🔍
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
09/09/2006 🔍09/13/2006 🔍
09/13/2006 🔍
09/13/2006 🔍
03/12/2015 🔍
08/04/2018 🔍
Sources
Advisory: securityfocus.com⛔Researcher: S3rv3r_hack3r
Status: Not defined
CVE: CVE-2006-4741 (🔍)
GCVE (CVE): GCVE-0-2006-4741
GCVE (VulDB): GCVE-100-32243
SecurityFocus: 19931 - PhpLinkExchange Multiple Input Validation Vulnerabilities
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 03/12/2015 15:51Updated: 08/04/2018 09:31
Changes: 03/12/2015 15:51 (49), 08/04/2018 09:31 (8)
Complete: 🔍
Cache ID: 216:4D8:103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.