BOSE Soundtouch Spotify Playlist cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.4 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in BOSE Soundtouch. Impacted is an unknown function of the component Spotify Playlist Handler. The manipulation leads to cross site scripting. This vulnerability is uniquely identified as CVE-2017-17750. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability, which was classified as problematic, has been found in BOSE Soundtouch (affected version not known). This issue affects some unknown functionality of the component Spotify Playlist Handler. The manipulation with an unknown input leads to a cross site scripting vulnerability. Using CWE to declare the problem leads to CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. Impacted is integrity. The summary by CVE is:
Bose SoundTouch devices allow XSS via a crafted public playlist from Spotify.
The bug was discovered 12/20/2017. The weakness was disclosed 03/24/2018 (Website). The advisory is shared at aryanitin.com. The identification of this vulnerability is CVE-2017-17750 since 12/18/2017. The attack may be initiated remotely. A simple authentication is required for exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.
The vulnerability was handled as a non-public zero-day exploit for at least 94 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entries VDB-114976 and VDB-114978 are pretty similar. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.4VulDB Meta Temp Score: 4.4
VulDB Base Score: 3.5
VulDB Temp Score: 3.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.4
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: Cross site scriptingCWE: CWE-79 / CWE-94 / CWE-74
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
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
12/18/2017 🔍12/20/2017 🔍
03/24/2018 🔍
03/24/2018 🔍
03/25/2018 🔍
01/16/2020 🔍
Sources
Advisory: aryanitin.comStatus: Not defined
CVE: CVE-2017-17750 (🔍)
GCVE (CVE): GCVE-0-2017-17750
GCVE (VulDB): GCVE-100-114977
See also: 🔍
Entry
Created: 03/25/2018 10:10Updated: 01/16/2020 11:13
Changes: 03/25/2018 10:10 (56), 01/16/2020 11:13 (1)
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.