| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.9 | $0-$5k | 0.45 |
Summary
A vulnerability was found in MXChange 0.2.0 Pre3 up to 0.2.0 Pre9. It has been classified as problematic. This affects an unknown part. Performing a manipulation results in cross site scripting. This vulnerability is cataloged as CVE-2005-3970. It is possible to initiate the attack remotely. There is no exploit available. Upgrading the affected component is recommended.
Details
A vulnerability was found in MXChange 0.2.0 Pre3 up to 0.2.0 Pre9. It has been classified as problematic. This affects an unknown code block. The manipulation 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 MXChange before 0.2.0-pre10 PL492 allows remote attackers to inject arbitrary web script or HTML via unknown vectors.
The weakness was shared 12/01/2005 (Website). The advisory is shared at sourceforge.net. This vulnerability is uniquely identified as CVE-2005-3970 since 12/03/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. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.
It is declared as proof-of-concept.
Upgrading to version 0.2.0-pre10 eliminates this vulnerability.
The vulnerability is also documented in the databases at SecurityFocus (BID 15672†), OSVDB (21338†) and Secunia (SA17793†). The entry VDB-27248 is related to this item. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 3.9
VulDB Base Score: 4.3
VulDB Temp Score: 3.9
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
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: 🔍
Upgrade: MXChange 0.2.0-pre10
Timeline
12/01/2005 🔍12/01/2005 🔍
12/01/2005 🔍
12/01/2005 🔍
12/03/2005 🔍
12/03/2005 🔍
03/11/2015 🔍
07/14/2018 🔍
Sources
Advisory: sourceforge.netStatus: Not defined
Confirmation: 🔍
CVE: CVE-2005-3970 (🔍)
GCVE (CVE): GCVE-0-2005-3970
GCVE (VulDB): GCVE-100-27249
SecurityFocus: 15672 - MXChange Multiple Unspecified Input Validation Vulnerabilities
Secunia: 17793 - MXChange Unspecified Cross-Site Scripting and SQL Injection Vulnerabilities, Moderately Critical
OSVDB: 21338 - MXChange Unspecified XSS
Vupen: ADV-2005-2683
See also: 🔍
Entry
Created: 03/11/2015 23:39Updated: 07/14/2018 10:10
Changes: 03/11/2015 23:39 (53), 07/14/2018 10:10 (7)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.