| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in QaTraq. It has been classified as problematic. Impacted is an unknown function of the file design_copy_plan_search.php. This manipulation causes cross site scripting. The attack is possible to be carried out remotely. Moreover, an exploit is present.
Details
A vulnerability has been found in QaTraq (unknown version) and classified as problematic. Affected by this vulnerability is an unknown code block of the file design_copy_plan_search.php. The manipulation with an unknown input leads to a cross site scripting vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect integrity.
The weakness was disclosed 06/23/2006 by Nenad Jovanovic (Website). The advisory is shared at seclab.tuwien.ac.at. The attack can be launched remotely. It demands that the victim is doing some kind of user interaction. Technical details and also a public exploit are known. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.
After even before and not, there has been an exploit disclosed. It is possible to download the exploit at securityfocus.com. It is declared as proof-of-concept. By approaching the search of inurl:design_copy_plan_search.php it is possible to find vulnerable targets with Google Hacking.
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 databases at SecurityFocus (BID 18620†) and OSVDB (27604†). The entries VDB-31085, VDB-84393, VDB-84394 and VDB-84395 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.5VulDB Meta Temp Score: 3.3
VulDB Base Score: 3.5
VulDB Temp Score: 3.3
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: 🔍
Google Hack: 🔍
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
05/24/2006 🔍06/23/2006 🔍
06/23/2006 🔍
07/27/2006 🔍
05/08/2016 🔍
12/02/2018 🔍
Sources
Advisory: seclab.tuwien.ac.atResearcher: Nenad Jovanovic
Status: Not defined
GCVE (VulDB): GCVE-100-84397
SecurityFocus: 18620 - QaTraq Multiple Cross-Site Scripting Vulnerabilities
OSVDB: 27604 - QaTraq design_copy_plan_search.php Multiple Parameter XSS
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 05/08/2016 19:54Updated: 12/02/2018 09:56
Changes: 05/08/2016 19:54 (46), 12/02/2018 09:56 (1)
Complete: 🔍
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.