| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.8 | $0-$5k | 0.00 |
Summary
A vulnerability was found in TemaTres. It has been rated as critical. The impacted element is an unknown function of the file index.php. Performing a manipulation results in sql injection. It is possible to initiate the attack remotely. Furthermore, there is an exploit available. It is suggested to enhance authentication.
Details
A vulnerability, which was classified as critical, was found in TemaTres (version unknown). This affects an unknown function of the file index.php. The manipulation 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 bug was discovered 04/23/2009. The weakness was shared 05/05/2009. It is possible to initiate the attack remotely. Technical details and a exploit are known. MITRE ATT&CK project uses the attack technique T1505 for this issue.
After immediately, there has been an exploit disclosed. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 11 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:index.php it is possible to find vulnerable targets with Google Hacking.
It is possible to mitigate the problem by adding an authentication mechanism. A possible mitigation has been published before and not just after the disclosure of the vulnerability.
The vulnerability is also documented in the vulnerability database at OSVDB (54246†). 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: 6.3VulDB Meta Temp Score: 5.8
VulDB Base Score: 6.3
VulDB Temp Score: 5.8
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: 🔍
Exploiting
Class: Sql injectionCWE: CWE-89 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Proof-of-Concept
Google Hack: 🔍
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: AuthenticationStatus: 🔍
0-Day Time: 🔍
Exploit Delay Time: 🔍
Timeline
04/23/2009 🔍05/04/2009 🔍
05/05/2009 🔍
05/05/2009 🔍
05/06/2009 🔍
05/09/2016 🔍
04/23/2019 🔍
Sources
Status: Not definedGCVE (VulDB): GCVE-100-86709
OSVDB: 54246 - TemaTres index.php Multiple Parameter SQL Injection
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 05/09/2016 15:36Updated: 04/23/2019 14:55
Changes: 05/09/2016 15:36 (40), 04/23/2019 14:55 (1)
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.