dotCMS up to 3.5.0 lucene_search.jsp Query cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.6 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as problematic has been discovered in dotCMS up to 3.5.0. This affects an unknown function of the file lucene_search.jsp. Executing a manipulation of the argument Query can lead to cross site scripting. This vulnerability is tracked as CVE-2016-3971. The attack can be launched remotely. No exploit exists. It is advisable to upgrade the affected component.
Details
A vulnerability has been found in dotCMS up to 3.5.0 (Content Management System) and classified as problematic. This vulnerability affects an unknown functionality of the file lucene_search.jsp. The manipulation of the argument query with an unknown input leads to a cross site scripting vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, and integrity. CVE summarizes:
Cross-site scripting (XSS) vulnerability in lucene_search.jsp in dotCMS before 3.5.1 allows remote authenticated administrators to inject arbitrary web script or HTML via the query parameter to c/portal/layout.
The weakness was disclosed 04/18/2016 (Website). The advisory is shared for download at seclists.org. This vulnerability was named CVE-2016-3971 since 04/07/2016. The exploitation appears to be easy. The attack can be initiated remotely. The successful exploitation needs a single authentication. Successful exploitation requires user interaction by the victim. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1059.007.
By approaching the search of inurl:lucene_search.jsp it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 3.5.1 eliminates this vulnerability.
The entry VDB-82553 is pretty similar. VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.8VulDB Meta Temp Score: 4.7
VulDB Base Score: 4.8
VulDB Temp Score: 4.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 4.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: Cross site scriptingCWE: CWE-79 / CWE-94 / CWE-74
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 |
OpenVAS ID: 103306
OpenVAS Name: dotCMS Multiple Vulnerabilities
OpenVAS File: 🔍
OpenVAS Family: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Upgrade: dotCMS 3.5.1
Timeline
04/07/2016 🔍04/18/2016 🔍
04/18/2016 🔍
04/19/2016 🔍
10/13/2018 🔍
Sources
Advisory: seclists.orgStatus: Not defined
Confirmation: 🔍
CVE: CVE-2016-3971 (🔍)
GCVE (CVE): GCVE-0-2016-3971
GCVE (VulDB): GCVE-100-82552
See also: 🔍
Entry
Created: 04/19/2016 11:59Updated: 10/13/2018 08:37
Changes: 04/19/2016 11:59 (49), 10/13/2018 08:37 (15)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.