| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.3 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in Day Communique 4. Impacted is an unknown function. Performing a manipulation of the argument Query results in cross site scripting. This vulnerability was named CVE-2005-4580. The attack may be initiated remotely. There is no available exploit.
Details
A vulnerability, which was classified as problematic, was found in Day Communique 4. This affects some unknown functionality. The manipulation of the argument query 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 integrity. The summary by CVE is:
Cross-site scripting (XSS) vulnerability in Day Communique 4 allows remote attackers to inject arbitrary web script or HTML via the query parameter in a search.
The weakness was presented 12/23/2005 by r0t (Website). The advisory is shared at securityfocus.com. This vulnerability is uniquely identified as CVE-2005-4580 since 12/29/2005. 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.
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 X-Force (23860), SecurityFocus (BID 16072†), OSVDB (21930†) and Secunia (SA18258†). 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: 4.3VulDB Meta Temp Score: 4.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.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: 🔍
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: 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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
12/23/2005 🔍12/27/2005 🔍
12/27/2005 🔍
12/27/2005 🔍
12/29/2005 🔍
12/29/2005 🔍
03/12/2015 🔍
07/15/2018 🔍
Sources
Advisory: securityfocus.com⛔Researcher: r0t
Status: Not defined
CVE: CVE-2005-4580 (🔍)
GCVE (CVE): GCVE-0-2005-4580
GCVE (VulDB): GCVE-100-27813
X-Force: 23860 - Communiqué search function cross-site scripting
SecurityFocus: 16072 - Day Communique Search Cross-Site Scripting Vulnerability
Secunia: 18258 - communique "query" Cross-Site Scripting Vulnerability, Less Critical
OSVDB: 21930 - Communique Search Module query Parameter XSS
Entry
Created: 03/12/2015 11:11Updated: 07/15/2018 16:29
Changes: 03/12/2015 11:11 (54), 07/15/2018 16: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.