ID CVE-2014-8554
Summary SQL injection vulnerability in the mc_project_get_attachments function in api/soap/mc_project_api.php in MantisBT before 1.2.18 allows remote attackers to execute arbitrary SQL commands via the project_id parameter. NOTE: this vulnerability exists because of an incomplete fix for CVE-2014-1609.
References
Vulnerable Configurations
  • MantisBT 1.2.9
    cpe:2.3:a:mantisbt:mantisbt:1.2.9
  • MantisBT 1.2.8
    cpe:2.3:a:mantisbt:mantisbt:1.2.8
  • MantisBT 1.2.7
    cpe:2.3:a:mantisbt:mantisbt:1.2.7
  • MantisBT 1.2.6
    cpe:2.3:a:mantisbt:mantisbt:1.2.6
  • MantisBT 1.2.5
    cpe:2.3:a:mantisbt:mantisbt:1.2.5
  • MantisBT 1.2.4
    cpe:2.3:a:mantisbt:mantisbt:1.2.4
  • MantisBT 1.2.3
    cpe:2.3:a:mantisbt:mantisbt:1.2.3
  • MantisBT 1.2.2
    cpe:2.3:a:mantisbt:mantisbt:1.2.2
  • cpe:2.3:a:mantisbt:mantisbt:1.2.17
    cpe:2.3:a:mantisbt:mantisbt:1.2.17
  • MantisBT 1.2.16
    cpe:2.3:a:mantisbt:mantisbt:1.2.16
  • MantisBT 1.2.15
    cpe:2.3:a:mantisbt:mantisbt:1.2.15
  • MantisBT 1.2.14
    cpe:2.3:a:mantisbt:mantisbt:1.2.14
  • MantisBT 1.2.13
    cpe:2.3:a:mantisbt:mantisbt:1.2.13
  • MantisBT 1.2.12
    cpe:2.3:a:mantisbt:mantisbt:1.2.12
  • MantisBT 1.2.11
    cpe:2.3:a:mantisbt:mantisbt:1.2.11
  • MantisBT 1.2.10
    cpe:2.3:a:mantisbt:mantisbt:1.2.10
  • MantisBT 1.2.1
    cpe:2.3:a:mantisbt:mantisbt:1.2.1
  • cpe:2.3:a:mantisbt:mantisbt:1.2.0a2
    cpe:2.3:a:mantisbt:mantisbt:1.2.0a2
  • cpe:2.3:a:mantisbt:mantisbt:1.2.0a1
    cpe:2.3:a:mantisbt:mantisbt:1.2.0a1
  • MantisBT 1.2.0rc2
    cpe:2.3:a:mantisbt:mantisbt:1.2.0:rc2
  • MantisBT 1.2.0rc1
    cpe:2.3:a:mantisbt:mantisbt:1.2.0:rc1
  • MantisBT 1.2.0a3
    cpe:2.3:a:mantisbt:mantisbt:1.2.0:a3
  • MantisBT 1.2.0a2
    cpe:2.3:a:mantisbt:mantisbt:1.2.0:a2
  • MantisBT 1.2.0a1
    cpe:2.3:a:mantisbt:mantisbt:1.2.0:a1
  • MantisBT 1.2.0
    cpe:2.3:a:mantisbt:mantisbt:1.2.0
  • MantisBT 1.1.9
    cpe:2.3:a:mantisbt:mantisbt:1.1.9
  • MantisBT 1.1.8
    cpe:2.3:a:mantisbt:mantisbt:1.1.8
  • MantisBT 1.1.7
    cpe:2.3:a:mantisbt:mantisbt:1.1.7
  • MantisBT 1.1.6
    cpe:2.3:a:mantisbt:mantisbt:1.1.6
  • MantisBT 1.1.5
    cpe:2.3:a:mantisbt:mantisbt:1.1.5
  • MantisBT 1.1.4
    cpe:2.3:a:mantisbt:mantisbt:1.1.4
  • MantisBT 1.1.3
    cpe:2.3:a:mantisbt:mantisbt:1.1.3
  • MantisBT 1.1.2
    cpe:2.3:a:mantisbt:mantisbt:1.1.2
  • MantisBT 1.1.1
    cpe:2.3:a:mantisbt:mantisbt:1.1.1
  • MantisBT 1.1.0rc3
    cpe:2.3:a:mantisbt:mantisbt:1.1.0:rc3
  • MantisBT 1.1.0rc2
    cpe:2.3:a:mantisbt:mantisbt:1.1.0:rc2
  • MantisBT 1.1.0rc1
    cpe:2.3:a:mantisbt:mantisbt:1.1.0:rc1
  • MantisBT 1.1.0a4
    cpe:2.3:a:mantisbt:mantisbt:1.1.0:a4
  • MantisBT 1.1.0a3
    cpe:2.3:a:mantisbt:mantisbt:1.1.0:a3
  • MantisBT 1.1.0a2
    cpe:2.3:a:mantisbt:mantisbt:1.1.0:a2
  • MantisBT 1.1.0a1
    cpe:2.3:a:mantisbt:mantisbt:1.1.0:a1
  • MantisBT 1.1.0
    cpe:2.3:a:mantisbt:mantisbt:1.1.0
  • MantisBT 1.0.9
    cpe:2.3:a:mantisbt:mantisbt:1.0.9
  • MantisBT 1.0.8
    cpe:2.3:a:mantisbt:mantisbt:1.0.8
  • MantisBT 1.0.7
    cpe:2.3:a:mantisbt:mantisbt:1.0.7
  • MantisBT 1.0.6
    cpe:2.3:a:mantisbt:mantisbt:1.0.6
  • MantisBT 1.0.5
    cpe:2.3:a:mantisbt:mantisbt:1.0.5
  • MantisBT 1.0.4
    cpe:2.3:a:mantisbt:mantisbt:1.0.4
  • MantisBT 1.0.3
    cpe:2.3:a:mantisbt:mantisbt:1.0.3
  • MantisBT 1.0.2
    cpe:2.3:a:mantisbt:mantisbt:1.0.2
  • MantisBT 1.0.1
    cpe:2.3:a:mantisbt:mantisbt:1.0.1
  • cpe:2.3:a:mantisbt:mantisbt:1.0.0a3
    cpe:2.3:a:mantisbt:mantisbt:1.0.0a3
  • cpe:2.3:a:mantisbt:mantisbt:1.0.0a2
    cpe:2.3:a:mantisbt:mantisbt:1.0.0a2
  • cpe:2.3:a:mantisbt:mantisbt:1.0.0a1
    cpe:2.3:a:mantisbt:mantisbt:1.0.0a1
  • MantisBT 1.0.0 Relesae Candidate 5
    cpe:2.3:a:mantisbt:mantisbt:1.0.0:rc5
  • MantisBT 1.0.0 Relesae Candidate 4
    cpe:2.3:a:mantisbt:mantisbt:1.0.0:rc4
  • MantisBT 1.0.0 Relesae Candidate 3
    cpe:2.3:a:mantisbt:mantisbt:1.0.0:rc3
  • MantisBT 1.0.0 Relesae Candidate 2
    cpe:2.3:a:mantisbt:mantisbt:1.0.0:rc2
  • MantisBT 1.0.0 Relesae Candidate 1
    cpe:2.3:a:mantisbt:mantisbt:1.0.0:rc1
  • MantisBT 1.0.0a3
    cpe:2.3:a:mantisbt:mantisbt:1.0.0:a3
  • MantisBT 1.0.0a2
    cpe:2.3:a:mantisbt:mantisbt:1.0.0:a2
  • MantisBT 1.0.0a1
    cpe:2.3:a:mantisbt:mantisbt:1.0.0:a1
  • MantisBT 1.0.0
    cpe:2.3:a:mantisbt:mantisbt:1.0.0
  • MantisBT 0.19.5
    cpe:2.3:a:mantisbt:mantisbt:0.19.5
  • MantisBT 0.19.4
    cpe:2.3:a:mantisbt:mantisbt:0.19.4
  • MantisBT 0.19.3
    cpe:2.3:a:mantisbt:mantisbt:0.19.3
  • MantisBT 0.19.2
    cpe:2.3:a:mantisbt:mantisbt:0.19.2
  • MantisBT 0.19.1
    cpe:2.3:a:mantisbt:mantisbt:0.19.1
  • cpe:2.3:a:mantisbt:mantisbt:0.19.0a2
    cpe:2.3:a:mantisbt:mantisbt:0.19.0a2
  • cpe:2.3:a:mantisbt:mantisbt:0.19.0a1
    cpe:2.3:a:mantisbt:mantisbt:0.19.0a1
  • MantisBT 0.19.0 Release Candidate 1
    cpe:2.3:a:mantisbt:mantisbt:0.19.0:rc1
  • MantisBT 0.19.0a2
    cpe:2.3:a:mantisbt:mantisbt:0.19.0:a2
  • MantisBT 0.19.0a1
    cpe:2.3:a:mantisbt:mantisbt:0.19.0:a1
  • MantisBT 0.19.0
    cpe:2.3:a:mantisbt:mantisbt:0.19.0
  • MantisBT 0.18.0
    cpe:2.3:a:mantisbt:mantisbt:0.18.0
CVSS
Base: 7.5 (as of 30-11-2015 - 13:33)
Impact:
Exploitability:
CWE CWE-89
CAPEC
  • Command Line Execution through SQL Injection
    An attacker uses standard SQL injection methods to inject data into the command line for execution. This could be done directly through misuse of directives such as MSSQL_xp_cmdshell or indirectly through injection of data into the database that would be interpreted as shell commands. Sometime later, an unscrupulous backend application (or could be part of the functionality of the same application) fetches the injected data stored in the database and uses this data as command line arguments without performing proper validation. The malicious data escapes that data plane by spawning new commands to be executed on the host.
  • Object Relational Mapping Injection
    An attacker leverages a weakness present in the database access layer code generated with an Object Relational Mapping (ORM) tool or a weakness in the way that a developer used a persistence framework to inject his or her own SQL commands to be executed against the underlying database. The attack here is similar to plain SQL injection, except that the application does not use JDBC to directly talk to the database, but instead it uses a data access layer generated by an ORM tool or framework (e.g. Hibernate). While most of the time code generated by an ORM tool contains safe access methods that are immune to SQL injection, sometimes either due to some weakness in the generated code or due to the fact that the developer failed to use the generated access methods properly, SQL injection is still possible.
  • SQL Injection through SOAP Parameter Tampering
    An attacker modifies the parameters of the SOAP message that is sent from the service consumer to the service provider to initiate a SQL injection attack. On the service provider side, the SOAP message is parsed and parameters are not properly validated before being used to access a database in a way that does not use parameter binding, thus enabling the attacker to control the structure of the executed SQL query. This pattern describes a SQL injection attack with the delivery mechanism being a SOAP message.
  • Expanding Control over the Operating System from the Database
    An attacker is able to leverage access gained to the database to read / write data to the file system, compromise the operating system, create a tunnel for accessing the host machine, and use this access to potentially attack other machines on the same network as the database machine. Traditionally SQL injections attacks are viewed as a way to gain unauthorized read access to the data stored in the database, modify the data in the database, delete the data, etc. However, almost every data base management system (DBMS) system includes facilities that if compromised allow an attacker complete access to the file system, operating system, and full access to the host running the database. The attacker can then use this privileged access to launch subsequent attacks. These facilities include dropping into a command shell, creating user defined functions that can call system level libraries present on the host machine, stored procedures, etc.
  • SQL Injection
    This attack exploits target software that constructs SQL statements based on user input. An attacker crafts input strings so that when the target software constructs SQL statements based on the input, the resulting SQL statement performs actions other than those the application intended. SQL Injection results from failure of the application to appropriately validate input. When specially crafted user-controlled input consisting of SQL syntax is used without proper validation as part of SQL queries, it is possible to glean information from the database in ways not envisaged during application design. Depending upon the database and the design of the application, it may also be possible to leverage injection to have the database execute system-related commands of the attackers' choice. SQL Injection enables an attacker to talk directly to the database, thus bypassing the application completely. Successful injection can cause information disclosure as well as ability to add or modify data in the database. In order to successfully inject SQL and retrieve information from a database, an attacker:
  • Blind SQL Injection
    Blind SQL Injection results from an insufficient mitigation for SQL Injection. Although suppressing database error messages are considered best practice, the suppression alone is not sufficient to prevent SQL Injection. Blind SQL Injection is a form of SQL Injection that overcomes the lack of error messages. Without the error messages that facilitate SQL Injection, the attacker constructs input strings that probe the target through simple Boolean SQL expressions. The attacker can determine if the syntax and structure of the injection was successful based on whether the query was executed or not. Applied iteratively, the attacker determines how and where the target is vulnerable to SQL Injection. For example, an attacker may try entering something like "username' AND 1=1; --" in an input field. If the result is the same as when the attacker entered "username" in the field, then the attacker knows that the application is vulnerable to SQL Injection. The attacker can then ask yes/no questions from the database server to extract information from it. For example, the attacker can extract table names from a database using the following types of queries: If the above query executes properly, then the attacker knows that the first character in a table name in the database is a letter between m and z. If it doesn't, then the attacker knows that the character must be between a and l (assuming of course that table names only contain alphabetic characters). By performing a binary search on all character positions, the attacker can determine all table names in the database. Subsequently, the attacker may execute an actual attack and send something like:
Access
VectorComplexityAuthentication
NETWORK LOW NONE
Impact
ConfidentialityIntegrityAvailability
PARTIAL PARTIAL PARTIAL
nessus via4
  • NASL family CGI abuses
    NASL id MANTIS_1_2_18.NASL
    description According to its version number, the MantisBT application hosted on the remote web server is 1.2.x prior to 1.2.18. It is, therefore, affected by the following vulnerabilities : - Multiple input-validation errors exist that could allow cross-site scripting attacks. (CVE-2014-7146, CVE-2014-8986, CVE-2014-8987, CVE-2014-9269, CVE-2014-9270, CVE-2014-9271, CVE-2014-9272, CVE-2014-9280, CVE-2014-9281) - Two unspecified errors exist that could allow SQL injection attacks. (CVE-2014-8554, CVE-2014-9089) - Three unspecified errors exist that could allow information disclosure attacks. (CVE-2014-8553, CVE-2014-8988, CVE-2014-9279) - An error exists in the file 'core/string_api.php' that could allow open redirect attacks. (CVE-2014-6316) - An error exists in the file 'gpc_api.php' that could allow an attacker to bypass authentication protections by using a password that starts with a NULL byte. (CVE-2014-6387) - An error exists in the 'XML Import/Export' plugin that could allow unauthorized attackers to upload XML files or obtain sensitive information. (CVE-2014-8598) - An error exists related to the CAPTCHA protection mechanism and the parameter 'public_key' that could allow security bypasses. (CVE-2014-9117) Note that Nessus has not attempted to exploit this issue but has instead relied only on the application's self-reported version number.
    last seen 2019-02-21
    modified 2018-11-28
    plugin id 80914
    published 2015-01-22
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=80914
    title MantisBT 1.2.x < 1.2.18 Multiple Vulnerabilities
  • NASL family Fedora Local Security Checks
    NASL id FEDORA_2014-15142.NASL
    description fix CVE-2014-7146, CVE-2014-8598 (#1162046) fix CVE-2014-8554 (#1159295) Note that Tenable Network Security has extracted the preceding description block directly from the Fedora security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.
    last seen 2019-02-21
    modified 2018-12-05
    plugin id 79895
    published 2014-12-15
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=79895
    title Fedora 21 : mantis-1.2.17-4.fc21 (2014-15142)
  • NASL family Fedora Local Security Checks
    NASL id FEDORA_2014-15108.NASL
    description fix CVE-2014-7146, CVE-2014-8598 (#1162046) fix CVE-2014-8554 (#1159295) Note that Tenable Network Security has extracted the preceding description block directly from the Fedora security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.
    last seen 2019-02-21
    modified 2018-12-05
    plugin id 79894
    published 2014-12-15
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=79894
    title Fedora 20 : mantis-1.2.17-4.fc20 (2014-15108)
  • NASL family Debian Local Security Checks
    NASL id DEBIAN_DSA-3120.NASL
    description Multiple security issues have been found in the Mantis bug tracking system, which may result in phishing, information disclosure, CAPTCHA bypass, SQL injection, cross-site scripting or the execution of arbitrary PHP code.
    last seen 2019-02-21
    modified 2018-11-28
    plugin id 80401
    published 2015-01-08
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=80401
    title Debian DSA-3120-1 : mantis - security update
  • NASL family Fedora Local Security Checks
    NASL id FEDORA_2014-15079.NASL
    description fix CVE-2014-7146, CVE-2014-8598 (#1162046) fix CVE-2014-8554 (#1159295) Note that Tenable Network Security has extracted the preceding description block directly from the Fedora security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.
    last seen 2019-02-21
    modified 2018-12-05
    plugin id 79893
    published 2014-12-15
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=79893
    title Fedora 19 : mantis-1.2.17-4.fc19 (2014-15079)
refmap via4
bid 70856
confirm
debian DSA-3120
mlist
  • [oss-security] 20141030 RE: SQL injection vulnerability in MantisBT SOAP API
  • [oss-security] 20141102 Re: SQL injection vulnerability in MantisBT SOAP API [CVE-2014-8554]
secunia 62101
xf mantisbt-cve20148554-sql-injection(98457)
Last major update 02-01-2017 - 21:59
Published 13-11-2014 - 16:32
Last modified 07-09-2017 - 21:29
Back to Top