Sitecore.NET 7.1/7.2 /Search-Results searchStr cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.2 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Sitecore.NET 7.1/7.2. It has been rated as problematic. Impacted is an unknown function of the file /Search-Results. The manipulation of the argument searchStr as part of Parameter leads to cross site scripting. This vulnerability is uniquely identified as CVE-2017-9356. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability was found in Sitecore.NET 7.1/7.2 and classified as problematic. This issue affects an unknown function of the file /Search-Results. The manipulation of the argument searchStr as part of a Parameter 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:
Sitecore.NET 7.1 through 7.2 has a Cross Site Scripting Vulnerability via the searchStr parameter to the /Search-Results URI.
The bug was discovered 06/21/2017. The weakness was disclosed 06/23/2017 (Website). It is possible to read the advisory at seclists.org. The identification of this vulnerability is CVE-2017-9356 since 06/01/2017. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1059.007 according to MITRE ATT&CK.
The vulnerability was handled as a non-public zero-day exploit for at least 2 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 vulnerability is also documented in the vulnerability database at SecurityFocus (BID 99239†). Be aware that VulDB is the high quality source for vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.2VulDB Meta Temp Score: 5.2
VulDB Base Score: 4.3
VulDB Temp Score: 4.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.1
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
06/01/2017 🔍06/21/2017 🔍
06/21/2017 🔍
06/23/2017 🔍
06/23/2017 🔍
06/23/2017 🔍
12/29/2020 🔍
Sources
Advisory: seclists.orgResearcher: Hamed Izadi
Status: Not defined
CVE: CVE-2017-9356 (🔍)
GCVE (CVE): GCVE-0-2017-9356
GCVE (VulDB): GCVE-100-102767
SecurityFocus: 99239 - Sitecore CMS 'searchStr' Parameter Cross Site Scripting Vulnerability
Entry
Created: 06/23/2017 15:22Updated: 12/29/2020 14:46
Changes: 06/23/2017 15:22 (59), 10/20/2019 07:02 (3), 12/29/2020 14:46 (2)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.