| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.7 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Goss iCM 7.0 and classified as problematic. This affects an unknown function of the file index.cfm. Performing a manipulation of the argument keyword results in cross site scripting. This vulnerability is identified as CVE-2006-2804. The attack can be initiated remotely. There is not any exploit available.
Details
A vulnerability, which was classified as problematic, was found in Goss iCM 7.0. This affects an unknown part of the file index.cfm. The manipulation of the argument keyword with an unknown input leads to a cross site scripting vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Cross-site scripting (XSS) vulnerability in index.cfm in Goss Intelligent Content Management (iCM) 7.0 and earlier allows remote attackers to inject arbitrary web script or HTML via the keyword parameter. NOTE: the provenance of this information is unknown; the details are obtained solely from third party sources.
The weakness was released 06/03/2006 (Website). The advisory is shared at vupen.com. This vulnerability is uniquely identified as CVE-2006-2804 since 06/02/2006. 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. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.
It is declared as proof-of-concept. By approaching the search of inurl:index.cfm it is possible to find vulnerable targets with Google Hacking.
The vulnerability is also documented in the databases at X-Force (26822), SecurityFocus (BID 18221†) and Secunia (SA20372†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Cross site scriptingCWE: CWE-80 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Proof-of-Concept
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
06/01/2006 🔍06/01/2006 🔍
06/02/2006 🔍
06/03/2006 🔍
06/03/2006 🔍
03/12/2015 🔍
07/28/2018 🔍
Sources
Advisory: vupen.com⛔Status: Confirmed
CVE: CVE-2006-2804 (🔍)
GCVE (CVE): GCVE-0-2006-2804
GCVE (VulDB): GCVE-100-30621
X-Force: 26822 - GOSS iCM index.cfm cross-site scripting
SecurityFocus: 18221
Secunia: 20372 - Goss iCM "keyword" Cross-Site Scripting Vulnerability, Less Critical
Vupen: ADV-2006-2089
Entry
Created: 03/12/2015 14:25Updated: 07/28/2018 08:29
Changes: 03/12/2015 14:25 (51), 07/28/2018 08:29 (7)
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.