| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in POWERGAP and classified as critical. This vulnerability affects unknown code of the file s03.php. This manipulation of the argument shopid causes memory corruption. This vulnerability appears as CVE-2006-4236. The attack may be initiated remotely. In addition, an exploit is available.
Details
A vulnerability has been found in POWERGAP (the affected version unknown) and classified as critical. Affected by this vulnerability is an unknown part of the file s03.php. The manipulation of the argument shopid 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 weakness was presented 08/17/2006 by Saudi Hackrz as not defined posting (Bugtraq). It is possible to read the advisory at archives.neohapsis.com. This vulnerability is known as CVE-2006-4236. 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 public exploit are known.
It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept. By approaching the search of inurl:s03.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 (28425), Exploit-DB (2201), SecurityFocus (BID 19565†) and OSVDB (29498†). See VDB-31869, VDB-84702, VDB-84704 and VDB-84705 for similar entries. Be aware that VulDB is the high quality source for vulnerability data.
Product
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 6.6
VulDB Base Score: 7.3
VulDB Temp Score: 6.6
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
Download: 🔍
Google Hack: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
08/17/2006 🔍08/17/2006 🔍
08/21/2006 🔍
10/05/2006 🔍
05/08/2016 🔍
07/14/2024 🔍
Sources
Advisory: archives.neohapsis.comResearcher: Saudi Hackrz
Status: Not defined
CVE: CVE-2006-4236 (🔍)
GCVE (CVE): GCVE-0-2006-4236
GCVE (VulDB): GCVE-100-84703
X-Force: 28425 - POWERGAP shopid file include
SecurityFocus: 19565 - Powergap Multiple Remote File Include Vulnerabilities
OSVDB: 29498 - POWERGAP s03.php shopid Parameter Remote File Inclusion
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 05/08/2016 20:03Updated: 07/14/2024 12:58
Changes: 05/08/2016 20:03 (46), 06/07/2017 14:51 (7), 08/05/2022 08:35 (2), 08/05/2022 08:37 (7), 07/14/2024 12:58 (16)
Complete: 🔍
Cache ID: 216:7CF:103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.