NetIQ Self Service Password Reset up to 2.x/3.3.1 HF1 cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.8 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in NetIQ Self Service Password Reset up to 2.x/3.3.1 HF1 and classified as problematic. This issue affects some unknown processing. Performing a manipulation results in cross site scripting. This vulnerability is known as CVE-2016-1599. Remote exploitation of the attack is possible. No exploit is available. The affected component should be upgraded.
Details
A vulnerability, which was classified as problematic, was found in NetIQ Self Service Password Reset up to 2.x/3.3.1 HF1. This affects an unknown part. The manipulation with an unknown input leads to a cross site scripting vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, and integrity. The summary by CVE is:
Cross-site scripting (XSS) vulnerability in NetIQ Self Service Password Reset (SSPR) 2.x and 3.x before 3.3.1 HF2 allows remote attackers to inject arbitrary web script or HTML via a crafted URL.
The weakness was published 03/24/2016 (Website). The advisory is shared at netiq.com. This vulnerability is uniquely identified as CVE-2016-1599 since 01/12/2016. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed 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.
Upgrading to version 3.3.1 HF2 eliminates this vulnerability.
The vulnerability is also documented in the databases at SecurityFocus (BID 96837†) and Vulnerability Center (SBV-57744†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.1VulDB Meta Temp Score: 5.9
VulDB Base Score: 6.1
VulDB Temp Score: 5.8
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: UpgradeStatus: 🔍
Upgrade: Self Service Password Reset 3.3.1 HF2
Timeline
01/12/2016 🔍03/23/2016 🔍
03/23/2016 🔍
03/23/2016 🔍
03/24/2016 🔍
03/24/2016 🔍
03/27/2016 🔍
02/03/2019 🔍
Sources
Vendor: microfocus.comAdvisory: netiq.com
Status: Not defined
Confirmation: 🔍
CVE: CVE-2016-1599 (🔍)
GCVE (CVE): GCVE-0-2016-1599
GCVE (VulDB): GCVE-100-81525
SecurityFocus: 96837 - NetIQ Self Service Password Reset CVE-2016-1599 Cross Site Scripting Vulnerability
Vulnerability Center: 57744 - NetIQ Self Service Password Reset 2.x and 3.x before 3.3.1 HF2 XSS Vulnerability, Medium
Entry
Created: 03/24/2016 11:48Updated: 02/03/2019 10:02
Changes: 03/24/2016 11:48 (55), 02/03/2019 10:02 (12)
Complete: 🔍
Cache ID: 216:CBE: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.