| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.7 | $0-$5k | 0.00 |
Summary
A vulnerability was found in @1 File Store. It has been classified as critical. This issue affects some unknown processing of the file control/files/edit.php. Performing a manipulation of the argument ID results in sql injection. This vulnerability is identified as CVE-2006-1278. The attack can be initiated remotely. Additionally, an exploit exists.
Details
A vulnerability was found in @1 File Store (unknown version). It has been classified as critical. This affects an unknown code block of the file control/files/edit.php. The manipulation of the argument id with an unknown input leads to a sql injection vulnerability. CWE is classifying the issue as CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. This is going to have an impact on confidentiality, integrity, and availability.
The weakness was released 03/11/2006 by Aliaksandr Hartsuyeu (Website). It is possible to read the advisory at evuln.com. This vulnerability is uniquely identified as CVE-2006-1278. It is possible to initiate the attack remotely. Technical details and a public exploit are known. The attack technique deployed by this issue is T1505 according to MITRE ATT&CK.
It is declared as proof-of-concept. By approaching the search of inurl:control/files/edit.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 SecurityFocus (BID 17090†), OSVDB (23854†) and Secunia (SA19224†). Entries connected to this vulnerability are available at VDB-29247, VDB-29246, VDB-83569 and VDB-83570. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 5.7
VulDB Base Score: 6.3
VulDB Temp Score: 5.7
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: Sql injectionCWE: CWE-89 / CWE-74 / CWE-707
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
03/11/2006 🔍03/13/2006 🔍
03/14/2006 🔍
03/18/2006 🔍
05/05/2016 🔍
11/01/2024 🔍
Sources
Advisory: evuln.comResearcher: Aliaksandr Hartsuyeu
Status: Not defined
CVE: CVE-2006-1278 (🔍)
GCVE (CVE): GCVE-0-2006-1278
GCVE (VulDB): GCVE-100-83571
X-Force: 25183
SecurityFocus: 17090 - @1 File Store Multiple Input Validation Vulnerabilities
Secunia: 19224
OSVDB: 23854 - @1 File Store control/files/edit.php id Parameter SQL Injection
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 05/05/2016 22:16Updated: 11/01/2024 20:00
Changes: 05/05/2016 22:16 (43), 11/16/2018 09:21 (3), 07/28/2022 23:41 (5), 07/28/2022 23:54 (8), 11/01/2024 20:00 (24)
Complete: 🔍
Cache ID: 216::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.