| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.1 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in Fr. Simon Rundell Ste Prayer 0.0.1. The affected element is an unknown function. The manipulation leads to sql injection. This vulnerability is traded as CVE-2008-6694. It is possible to initiate the attack remotely. There is no exploit available.
Details
A vulnerability was found in Fr. Simon Rundell Ste Prayer 0.0.1 and classified as critical. This issue affects some unknown processing. The manipulation with an unknown input leads to a sql injection vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
SQL injection vulnerability in Random Prayer (ste_prayer) 0.0.1 for TYPO3 allows remote attackers to execute arbitrary SQL commands via unknown vectors.
The weakness was shared 06/19/2008 by Georg Ringer (Website). The advisory is shared at securityfocus.com. The identification of this vulnerability is CVE-2008-6694 since 04/10/2009. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1505 for this issue.
It is declared as highly functional.
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 (43209), SecurityFocus (BID 29827†) and OSVDB (46391†). The entries VDB-47674, VDB-47673, VDB-47672 and VDB-47671 are related to this item. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.1
VulDB Base Score: 7.3
VulDB Temp Score: 7.1
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: 🔍
Status: Highly functional
EPSS Score: 🔍
EPSS Percentile: 🔍
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
06/19/2008 🔍06/19/2008 🔍
06/19/2008 🔍
04/10/2009 🔍
04/10/2009 🔍
03/17/2015 🔍
12/14/2017 🔍
Sources
Advisory: securityfocus.com⛔Researcher: Georg Ringer
Status: Not defined
Confirmation: 🔍
CVE: CVE-2008-6694 (🔍)
GCVE (CVE): GCVE-0-2008-6694
GCVE (VulDB): GCVE-100-47669
X-Force: 43209 - Random Prayer extension for TYPO3 unspecified SQL injection
SecurityFocus: 29827 - TYPO3 Random Prayer Extension SQL Injection Vulnerability
OSVDB: 46391 - Random Prayer (ste_prayer) Extension for TYPO3 Unspecified SQL Injection
See also: 🔍
Entry
Created: 03/17/2015 23:38Updated: 12/14/2017 08:29
Changes: 03/17/2015 23:38 (52), 12/14/2017 08:29 (6)
Complete: 🔍
Cache ID: 216:072: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.