| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in phpChess and classified as critical. Affected is an unknown function of the file layout_t_top.php. Performing a manipulation of the argument Root_Path results in Remote Code Execution. This vulnerability is reported as CVE-2007-2677. Moreover, an exploit is present.
Details
A vulnerability, which was classified as critical, was found in phpChess (the affected version unknown). This affects an unknown part of the file layout_t_top.php. The manipulation of the argument Root_Path with an unknown input leads to a remote code execution vulnerability. This is going to have an impact on confidentiality, integrity, and availability.
The weakness was disclosed 05/03/2007 by GolD_M [Mahmood_ali] (Website). The advisory is shared at attrition.org. This vulnerability is uniquely identified as CVE-2007-2677 since 05/14/2007. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details and a public exploit are known.
After before and not just, there has been an exploit disclosed. The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept. By approaching the search of inurl:layout_t_top.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 (3837), SecurityFocus (BID 23797†), OSVDB (35595†) and Secunia (SA25147†). The entries VDB-36803, VDB-85555 and VDB-85556 are pretty similar. 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: 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: Remote Code ExecutionCWE: Unknown
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: 🔍
Suricata ID: 2003742
Suricata Class: 🔍
Suricata Message: 🔍
Timeline
05/03/2007 🔍05/03/2007 🔍
05/03/2007 🔍
05/04/2007 🔍
05/04/2007 🔍
05/14/2007 🔍
05/14/2007 🔍
05/08/2016 🔍
09/10/2024 🔍
Sources
Advisory: attrition.orgResearcher: GolD_M [Mahmood_ali]
Status: Not defined
CVE: CVE-2007-2677 (🔍)
GCVE (CVE): GCVE-0-2007-2677
GCVE (VulDB): GCVE-100-85557
X-Force: 34056
SecurityFocus: 23797 - PHPChess Root_Path Multiple Remote File Include Vulnerabilities
Secunia: 25147 - phpChess Multiple File Inclusion Vulnerabilities, Highly Critical
OSVDB: 35595 - phpChess Community Edition layout_t_top.php Root_Path Parameter Remote File Inclusion
Vupen: ADV-2007-1649
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 05/08/2016 21:55Updated: 09/10/2024 12:30
Changes: 05/08/2016 21:55 (57), 01/09/2019 07:59 (7), 08/10/2022 15:22 (4), 08/10/2022 15:28 (1), 09/10/2024 12:30 (17)
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.