SocialEngine up to 2.7 profile_comments.php comment_secure sql injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.1 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, was found in SocialEngine up to 2.7. The impacted element is an unknown function of the file profile_comments.php. The manipulation of the argument comment_secure results in sql injection. This vulnerability is reported as CVE-2008-6120. The attack can be launched remotely. No exploit exists.
Details
A vulnerability was found in SocialEngine up to 2.7. It has been classified as critical. Affected is some unknown functionality of the file profile_comments.php. The manipulation of the argument comment_secure 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. CVE summarizes:
SQL injection vulnerability in profile_comments.php in SocialEngine (SE) 2.7 and earlier allows remote attackers to execute arbitrary SQL commands via the comment_secure parameter.
The weakness was disclosed 02/11/2009 by David Vieira-Kurz (Website). The advisory is available at marc.info. This vulnerability is traded as CVE-2008-6120 since 02/11/2009. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1505 by the MITRE ATT&CK project.
It is declared as highly functional. By approaching the search of inurl:profile_comments.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 X-Force (46770) and SecurityFocus (BID 32382†). The entry VDB-46483 is pretty similar. If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
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
Google Hack: 🔍
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
11/20/2008 🔍02/11/2009 🔍
02/11/2009 🔍
02/11/2009 🔍
03/17/2015 🔍
10/28/2018 🔍
Sources
Advisory: marc.infoResearcher: David Vieira-Kurz
Status: Not defined
CVE: CVE-2008-6120 (🔍)
GCVE (CVE): GCVE-0-2008-6120
GCVE (VulDB): GCVE-100-46482
X-Force: 46770 - SocialEngine profile_comments.php SQL injection
SecurityFocus: 32382 - SocialEngine HTTP Response Splitting and SQL-injection Vulnerabilities
See also: 🔍
Entry
Created: 03/17/2015 16:11Updated: 10/28/2018 07:49
Changes: 03/17/2015 16:11 (49), 10/28/2018 07:49 (6)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.