QaTraq 6.5 queries_view_search.php content cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.1 | $0-$5k | 0.00 |
Summary
A vulnerability was found in QaTraq 6.5. It has been classified as problematic. Affected is an unknown function of the file queries_view_search.php. The manipulation of the argument content leads to cross site scripting. This vulnerability is referenced as CVE-2006-3312. Remote exploitation of the attack is possible. Furthermore, an exploit is available. Upgrading the affected component is recommended.
Details
A vulnerability was found in QaTraq 6.5. It has been rated as problematic. This issue affects an unknown code block of the file queries_view_search.php. The manipulation of the argument content 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 integrity. The summary by CVE is:
Multiple cross-site scripting (XSS) vulnerabilities in ashmans and Bill Echlin QaTraq 6.5 RC and earlier allow remote attackers to inject arbitrary web script or HTML via the (1) link_print, (2) link_upgrade, (3) link_sql, (4) link_next, (5) link_prev, and (6) link_list parameters in top.inc as included by queries_view_search.php; the (7) msg, (8) component_name, and (9) component_desc parameters in (a) components_copy_content.php, (b) components_modify_content.php, and (c) components_new_content.php; the (10) title, (11) version, and (12) content parameters in design_copy_content.php; the (13) plan_title and (14) plan_content parameters in design_copy_plan_search.php; the (15) title, (16) minor_version, (17) new_version, and (18) content parameters in design_modify_content.php; the (19) title, (20) version, and (21) content parameters in design_new_content.php; the (22) plan_name and (23) plan_desc parameters in design_new_search.php; the (24) file_name parameter in download.php; the (25) username and (26) password parameters in login.php; the (27) title, (28) version, and (29) content parameters in phase_copy_content.php; the (30) content parameter in phase_delete_search.php; the (31) title, (32) minor_version, (33) new_version, and (34) content parameters in phase_modify_content.php; the (35) content, (36) title, (37) version, and (38) content parameters in phase_modify_search.php; the (39) content parameter in phase_view_search.php; the (40) msg, (41) product_name, and (42) product_desc parameters in products_copy_content.php; and possibly the (43) product_name and (44) product_desc parameters in (d) products_copy_search.php, and a large number of additional parameters and executables. NOTE: the vendor notified CVE via e-mail that this issue has been fixed in the 6.8 RC release.
The weakness was published 06/23/2006 by Nenad Jovanovic (Website). The advisory is shared at testmanagement.com. The identification of this vulnerability is CVE-2006-3312 since 06/29/2006. 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 even before and not, there has been an exploit disclosed. The exploit is available at securityfocus.com. It is declared as highly functional. By approaching the search of inurl:queries_view_search.php it is possible to find vulnerable targets with Google Hacking.
Upgrading eliminates this vulnerability.
The vulnerability is also documented in the databases at X-Force (27355), SecurityFocus (BID 18620†), OSVDB (27599†) and SecurityTracker (ID 1016381†). Similar entries are available at VDB-84393, VDB-84394, VDB-84395 and VDB-84396. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.1
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Cross site scriptingCWE: CWE-80 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Highly functional
Download: 🔍
Google Hack: 🔍
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: 🔍
0-Day Time: 🔍
Timeline
05/24/2006 🔍06/23/2006 🔍
06/23/2006 🔍
06/26/2006 🔍
06/29/2006 🔍
06/29/2006 🔍
07/27/2006 🔍
03/12/2015 🔍
07/30/2018 🔍
Sources
Advisory: testmanagement.comResearcher: Nenad Jovanovic
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2006-3312 (🔍)
GCVE (CVE): GCVE-0-2006-3312
GCVE (VulDB): GCVE-100-31085
X-Force: 27355 - QaTraq multiple scripts and parameters cross-site scripting
SecurityFocus: 18620 - QaTraq Multiple Cross-Site Scripting Vulnerabilities
OSVDB: 27599 - QaTraq top.inc Multiple Parameter XSS
SecurityTracker: 1016381
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 03/12/2015 14:25Updated: 07/30/2018 07:58
Changes: 03/12/2015 14:25 (66), 07/30/2018 07:58 (2)
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.