| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.0 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in phpHtmlLib. This vulnerability affects unknown code of the file divtag_utils.php. The manipulation of the argument phphtmllib leads to privileges management. This vulnerability is documented as CVE-2006-4287. Additionally, an exploit exists.
Details
A vulnerability was found in phpHtmlLib (version now known) and classified as critical. This issue affects some unknown processing of the file divtag_utils.php. The manipulation of the argument phphtmllib with an unknown input leads to a privileges management vulnerability. Using CWE to declare the problem leads to CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. Impacted is confidentiality, integrity, and availability.
The weakness was released 08/20/2006 by Kacper (Website). The advisory is shared at exploit-db.com. The identification of this vulnerability is CVE-2006-4287. Technical details as well as a public exploit are known. MITRE ATT&CK project uses the attack technique T1068 for this issue.
A public exploit has been developed by Kacper and been published even before and not after the advisory. The exploit is available at exploit-db.com. It is declared as proof-of-concept. By approaching the search of inurl:divtag_utils.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 Exploit-DB (2226), SecurityFocus (BID 19611†), OSVDB (28045†) and Secunia (SA21593†). Entries connected to this vulnerability are available at VDB-31908, VDB-84462, VDB-84463 and VDB-84464. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.0
VulDB Base Score: 5.3
VulDB Temp Score: 5.0
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: Privileges managementCWE: CWE-269 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Author: Kacper
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/20/2006 🔍08/20/2006 🔍
08/20/2006 🔍
08/20/2006 🔍
08/21/2006 🔍
08/22/2006 🔍
05/08/2016 🔍
07/14/2024 🔍
Sources
Advisory: exploit-db.comResearcher: Kacper
Status: Confirmed
CVE: CVE-2006-4287 (🔍)
GCVE (CVE): GCVE-0-2006-4287
GCVE (VulDB): GCVE-100-84461
X-Force: 28486
SecurityFocus: 19611 - NES Game and NES System Multiple Remote File Include Vulnerabilities
Secunia: 21593
OSVDB: 28045 - NES Game & NES System divtag_utils.php phphtmllib Parameter Remote File Inclusion
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 05/08/2016 19:56Updated: 07/14/2024 22:38
Changes: 05/08/2016 19:56 (49), 11/27/2018 10:41 (4), 08/03/2022 10:17 (4), 08/03/2022 10:23 (8), 07/14/2024 22:38 (15)
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.