bigware Bigware Shop up to 2.1.3 main_bigware_43.php lastname sql injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.0 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in bigware Bigware Shop up to 2.1.3. This affects an unknown function of the file main_bigware_43.php. The manipulation of the argument lastname leads to sql injection. This vulnerability is traded as CVE-2012-5317. It is possible to initiate the attack remotely. There is no exploit available. It is advisable to upgrade the affected component.
Details
A vulnerability was found in bigware Bigware Shop up to 2.1.3 and classified as critical. This issue affects an unknown functionality of the file main_bigware_43.php. The manipulation of the argument lastname 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 main_bigware_43.php in Bigware Shop before 2.1.5 allows remote attackers to execute arbitrary SQL commands via the lastname parameter in a process action.
The weakness was shared 10/08/2012 (Website). The advisory is shared at bigware.de. The identification of this vulnerability is CVE-2012-5317 since 10/08/2012. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1505 for this issue.
By approaching the search of inurl:main_bigware_43.php it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 2.1.4 eliminates this vulnerability.
The vulnerability is also documented in the databases at SecurityFocus (BID 51640†) and Secunia (SA47713†). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
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.0
VulDB Base Score: 7.3
VulDB Temp Score: 7.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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Sql injectionCWE: CWE-89 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Bigware Shop 2.1.4
Timeline
01/23/2012 🔍10/08/2012 🔍
10/08/2012 🔍
10/08/2012 🔍
03/24/2015 🔍
01/31/2018 🔍
Sources
Advisory: bigware.deStatus: Not defined
CVE: CVE-2012-5317 (🔍)
GCVE (CVE): GCVE-0-2012-5317
GCVE (VulDB): GCVE-100-62609
SecurityFocus: 51640 - Bigware Shop 'main_bigware_43.php' SQL Injection Vulnerability
Secunia: 47713
Entry
Created: 03/24/2015 12:22Updated: 01/31/2018 07:55
Changes: 03/24/2015 12:22 (48), 01/31/2018 07:55 (6)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.