Mantis up to 1.0.0a3 Monitoring core/database_api.php g_db_type cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.0 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in Mantis up to 1.0.0a3. Affected by this vulnerability is an unknown functionality of the file core/database_api.php of the component Monitoring. The manipulation of the argument g_db_type leads to cross site scripting. This vulnerability is uniquely identified as CVE-2005-2556. The attack is possible to be carried out remotely. No exploit exists. You should upgrade the affected component.
Details
A vulnerability, which was classified as critical, has been found in Mantis up to 1.0.0a3 (Bug Tracking Software). This issue affects some unknown functionality of the file core/database_api.php of the component Monitoring. The manipulation of the argument g_db_type 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 confidentiality, integrity, and availability. The summary by CVE is:
core/database_api.php in Mantis 0.19.0a1 through 1.0.0a3, with register_globals enabled, allows remote attackers to connect to internal databases by modifying the g_db_type variable and monitoring the speed of responses, as identified by bug#0005956.
The bug was discovered 08/19/2005. The weakness was disclosed 08/24/2005 (Website). It is possible to read the advisory at securityfocus.com. The identification of this vulnerability is CVE-2005-2556 since 08/16/2005. The exploitation is known to be easy. 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 of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1059.007 according to MITRE ATT&CK.
The vulnerability was handled as a non-public zero-day exploit for at least 5 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:core/database_api.php it is possible to find vulnerable targets with Google Hacking. The vulnerability scanner Nessus provides a plugin with the ID 19815 (GLSA-200509-16 : Mantis: XSS and SQL injection vulnerabilities), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Gentoo Local Security Checks and running in the context l.
Upgrading eliminates this vulnerability. A possible mitigation has been published 2 months after the disclosure of the vulnerability.
The vulnerability is also documented in the databases at X-Force (21961), Tenable (19815), SecurityFocus (BID 14604†), OSVDB (18903†) and Secunia (SA16506†). The entries VDB-26701, VDB-26700, VDB-26698 and VDB-26446 are pretty similar. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.0
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
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
Google Hack: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 19815
Nessus Name: GLSA-200509-16 : Mantis: XSS and SQL injection vulnerabilities
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
Nessus Port: 🔍
OpenVAS ID: 55116
OpenVAS Name: Debian Security Advisory DSA 778-1 (mantis)
OpenVAS File: 🔍
OpenVAS Family: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Timeline
08/16/2005 🔍08/19/2005 🔍
08/19/2005 🔍
08/24/2005 🔍
08/24/2005 🔍
08/24/2005 🔍
08/28/2005 🔍
09/24/2005 🔍
10/05/2005 🔍
03/11/2015 🔍
06/08/2019 🔍
Sources
Advisory: securityfocus.com⛔Status: Not defined
CVE: CVE-2005-2556 (🔍)
GCVE (CVE): GCVE-0-2005-2556
GCVE (VulDB): GCVE-100-26147
X-Force: 21961
SecurityFocus: 14604 - Mantis Multiple Input Validation Vulnerabilities
Secunia: 16506
OSVDB: 18903 - CVE-2005-2556 - Mantis - Security Bypass Issue
Vulnerability Center: 8993 - Mantis SQL Injection Attack via g_db_type Variable, High
See also: 🔍
Entry
Created: 03/11/2015 23:39Updated: 06/08/2019 14:40
Changes: 03/11/2015 23:39 (75), 06/08/2019 14:40 (6)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.