Oempro campaign_track.php FormValue_SearchKeywords sql injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.0 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Oempro. It has been declared as critical. Impacted is an unknown function of the file /client/campaign_track.php. The manipulation of the argument FormValue_SearchKeywords results in sql injection. The attack can be launched remotely. Moreover, an exploit is present.
Details
A vulnerability classified as critical has been found in Oempro (version now known). Affected is some unknown processing of the file /client/campaign_track.php. The manipulation of the argument FormValue_SearchKeywords 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 07/02/2008. The weakness was disclosed 12/01/2008. It is possible to launch the attack remotely. Technical details and a exploit are known. The MITRE ATT&CK project declares the attack technique as T1505.
After even before and not, 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 143 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:client/campaign_track.php it is possible to find vulnerable targets with Google Hacking.
A possible mitigation has been published even before and not after the disclosure of the vulnerability.
The vulnerability is also documented in the vulnerability database at OSVDB (50323†). Once again VulDB remains the best source 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: 6.0
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
07/02/2008 🔍11/21/2008 🔍
11/22/2008 🔍
12/01/2008 🔍
12/01/2008 🔍
05/09/2016 🔍
04/23/2019 🔍
Sources
Status: Not definedGCVE (VulDB): GCVE-100-86652
OSVDB: 50323 - Oempro /client/campaign_track.php FormValue_SearchKeywords Parameter SQL Injection
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 05/09/2016 15:31Updated: 04/23/2019 15:15
Changes: 05/09/2016 15:31 (40), 04/23/2019 15:15 (1)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.