Shopware up to 5.1.4 Backend backend/Login/load/ input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.4 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Shopware up to 5.1.4 and classified as critical. Affected by this issue is some unknown functionality of the file backend/Login/load/ of the component Backend. This manipulation causes input validation. This vulnerability appears as CVE-2016-3109. The attack may be initiated remotely. There is no available exploit. The affected component should be upgraded.
Details
A vulnerability has been found in Shopware up to 5.1.4 and classified as critical. Affected by this vulnerability is an unknown part of the file backend/Login/load/ of the component Backend. The manipulation with an unknown input leads to a input validation vulnerability. The CWE definition for the vulnerability is CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
The backend/Login/load/ script in Shopware before 5.1.5 allows remote attackers to execute arbitrary code.
The bug was discovered 04/24/2016. The weakness was presented 04/21/2017 as not defined posting (Bugtraq). The advisory is shared at securityfocus.com. This vulnerability is known as CVE-2016-3109 since 03/10/2016. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available.
It is declared as highly functional. The vulnerability was handled as a non-public zero-day exploit for at least 362 days. During that time the estimated underground price was around $0-$5k.
Upgrading to version 5.1.5 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 97979†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.4
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
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: Input validationCWE: CWE-20
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 |
D2Sec: Shopware Server Side Template Injection RCE
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Shopware 5.1.5
Patch: github.com
Timeline
03/10/2016 🔍04/24/2016 🔍
04/21/2017 🔍
04/21/2017 🔍
04/22/2017 🔍
04/23/2017 🔍
12/02/2022 🔍
Sources
Product: github.comAdvisory: 136781⛔
Researcher: David Vieira-Kurz
Status: Not defined
Confirmation: 🔍
CVE: CVE-2016-3109 (🔍)
GCVE (CVE): GCVE-0-2016-3109
GCVE (VulDB): GCVE-100-100453
SecurityFocus: 97979 - Shopware CVE-2016-3109 Arbitrary Code Execution Vulnerability
OSVDB: - CVE-2016-3109 - Shopware - Code Execution Issue
Entry
Created: 04/22/2017 08:47Updated: 12/02/2022 07:13
Changes: 04/22/2017 08:47 (64), 09/19/2020 14:28 (4), 12/21/2020 12:37 (2), 12/02/2022 07:13 (4)
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.