| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.7 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Novell NetIQ 3.2. It has been classified as problematic. Affected is an unknown function of the file /nidp/idff/sso. The manipulation of the argument Ecom_User_ID leads to cross site scripting. It is possible to initiate the attack remotely. Furthermore, there is an exploit available. Upgrading the affected component is recommended.
Details
A vulnerability was found in Novell NetIQ 3.2. It has been rated as problematic. This issue affects an unknown code block of the file /nidp/idff/sso. The manipulation of the argument Ecom_User_ID with an unknown input leads to a cross site scripting vulnerability. Using CWE to declare the problem leads to CWE-80. The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special characters such as "<", ">", and "&" that could be interpreted as web-scripting elements when they are sent to a downstream component that processes web pages. Impacted is confidentiality, integrity, and availability.
The weakness was shared 05/27/2013 as not defined knowledge base article (Website). The advisory is shared at novell.com. The vendor cooperated in the coordination of the public release. The exploitation is known to be easy. 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 as well as a public exploit are known. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.
After immediately, there has been an exploit disclosed. The exploit is available at novell.com. It is declared as proof-of-concept.
Upgrading to version 3.2 SP1 eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the databases at OSVDB (93701†) and Secunia (SA53538†). The entry VDB-8910 is related to this item. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
License
Support
Website
- Vendor: https://www.novell.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 5.7
VulDB Base Score: 6.3
VulDB Temp Score: 5.7
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: 🔍
Exploiting
Class: Cross site scriptingCWE: CWE-80 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
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: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Exploit Delay Time: 🔍
Upgrade: NetIQ 3.2 SP1
Timeline
05/27/2013 🔍05/27/2013 🔍
05/27/2013 🔍
05/27/2013 🔍
05/29/2013 🔍
03/23/2019 🔍
Sources
Vendor: novell.comAdvisory: novell.com
Status: Not defined
Coordinated: 🔍
GCVE (VulDB): GCVE-100-8909
Secunia: 53538 - NetIQ Access Manager Identity Server "Ecom_User_ID" Cross-Site Scripting Vulnera, Less Critical
OSVDB: 93701
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 05/29/2013 11:43Updated: 03/23/2019 09:34
Changes: 05/29/2013 11:43 (49), 03/23/2019 09:34 (5)
Complete: 🔍
Committer:
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.