ID CVE-2014-2323
Summary SQL injection vulnerability in mod_mysql_vhost.c in lighttpd before 1.4.35 allows remote attackers to execute arbitrary SQL commands via the host name, related to request_check_hostname.
References
Vulnerable Configurations
  • lighttpd 1.4.34
    cpe:2.3:a:lighttpd:lighttpd:1.4.34
  • lighttpd 1.3.16
    cpe:2.3:a:lighttpd:lighttpd:1.3.16
  • lighttpd 1.4.10
    cpe:2.3:a:lighttpd:lighttpd:1.4.10
  • lighttpd 1.4.11
    cpe:2.3:a:lighttpd:lighttpd:1.4.11
  • lighttpd 1.4.12
    cpe:2.3:a:lighttpd:lighttpd:1.4.12
  • lighttpd 1.4.13
    cpe:2.3:a:lighttpd:lighttpd:1.4.13
  • lighttpd lighttpd 1.4.14
    cpe:2.3:a:lighttpd:lighttpd:1.4.14
  • lighttpd 1.4.15
    cpe:2.3:a:lighttpd:lighttpd:1.4.15
  • lighttpd 1.4.16
    cpe:2.3:a:lighttpd:lighttpd:1.4.16
  • lighttpd lighttpd 1.4.17
    cpe:2.3:a:lighttpd:lighttpd:1.4.17
  • lighttpd 1.4.18
    cpe:2.3:a:lighttpd:lighttpd:1.4.18
  • lighttpd lighttpd 1.4.19
    cpe:2.3:a:lighttpd:lighttpd:1.4.19
  • lighttpd lighttpd 1.4.20
    cpe:2.3:a:lighttpd:lighttpd:1.4.20
  • lighttpd lighttpd 1.4.21
    cpe:2.3:a:lighttpd:lighttpd:1.4.21
  • lighttpd lighttpd 1.4.22
    cpe:2.3:a:lighttpd:lighttpd:1.4.22
  • lighttpd lighttpd 1.4.23
    cpe:2.3:a:lighttpd:lighttpd:1.4.23
  • lighttpd lighttpd 1.4.24
    cpe:2.3:a:lighttpd:lighttpd:1.4.24
  • lighttpd lighttpd 1.4.25
    cpe:2.3:a:lighttpd:lighttpd:1.4.25
  • lighttpd lighttpd 1.4.26
    cpe:2.3:a:lighttpd:lighttpd:1.4.26
  • Lighttpd 1.4.27
    cpe:2.3:a:lighttpd:lighttpd:1.4.27
  • lighttpd 1.4.28
    cpe:2.3:a:lighttpd:lighttpd:1.4.28
  • lighttpd 1.4.29
    cpe:2.3:a:lighttpd:lighttpd:1.4.29
  • lighttpd 1.4.3
    cpe:2.3:a:lighttpd:lighttpd:1.4.3
  • lighttpd 1.4.30
    cpe:2.3:a:lighttpd:lighttpd:1.4.30
  • lighttpd 1.4.31
    cpe:2.3:a:lighttpd:lighttpd:1.4.31
  • lighttpd 1.4.32
    cpe:2.3:a:lighttpd:lighttpd:1.4.32
  • lighttpd 1.4.33
    cpe:2.3:a:lighttpd:lighttpd:1.4.33
  • lighttpd 1.4.4
    cpe:2.3:a:lighttpd:lighttpd:1.4.4
  • lighttpd 1.4.5
    cpe:2.3:a:lighttpd:lighttpd:1.4.5
  • lighttpd 1.4.6
    cpe:2.3:a:lighttpd:lighttpd:1.4.6
  • lighttpd 1.4.7
    cpe:2.3:a:lighttpd:lighttpd:1.4.7
  • lighttpd 1.4.8
    cpe:2.3:a:lighttpd:lighttpd:1.4.8
  • lighttpd 1.4.9
    cpe:2.3:a:lighttpd:lighttpd:1.4.9
CVSS
Base: 7.5 (as of 17-03-2014 - 09:52)
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 Amazon Linux Local Security Checks
    NASL id ALA_ALAS-2014-346.NASL
    description Multiple directory traversal vulnerabilities in (1) mod_evhost and (2) mod_simple_vhost in lighttpd before 1.4.35 allow remote attackers to read arbitrary files via a .. (dot dot) in the host name, related to request_check_hostname. SQL injection vulnerability in mod_mysql_vhost.c in lighttpd before 1.4.35 allows remote attackers to execute arbitrary SQL commands via the host name, related to request_check_hostname.
    last seen 2019-02-21
    modified 2018-04-18
    plugin id 78289
    published 2014-10-12
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=78289
    title Amazon Linux AMI : lighttpd (ALAS-2014-346)
  • NASL family Fedora Local Security Checks
    NASL id FEDORA_2014-3947.NASL
    description 1.4.35, fixes SA-2014-01, CVE-2014-2323, CVE-2014-2324 [1] http://seclists.org/oss-sec/2014/q1/561 [2] http://download.lighttpd.net/lighttpd/security/lighttpd_sa_2014_01.txt [3] http://www.lighttpd.net/2014/3/12/1.4.35/ 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 73194
    published 2014-03-26
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=73194
    title Fedora 19 : lighttpd-1.4.35-1.fc19 (2014-3947)
  • NASL family SuSE Local Security Checks
    NASL id OPENSUSE-2014-257.NASL
    description lighttpd was updated to version 1.4.35, fixing bugs and security issues : CVE-2014-2323: SQL injection vulnerability in mod_mysql_vhost.c in lighttpd allowed remote attackers to execute arbitrary SQL commands via the host name, related to request_check_hostname. CVE-2014-2323: Multiple directory traversal vulnerabilities in (1) mod_evhost and (2) mod_simple_vhost in lighttpd allowed remote attackers to read arbitrary files via a .. (dot dot) in the host name, related to request_check_hostname. More information can be found on the lighttpd advisory page: http://download.lighttpd.net/lighttpd/security/lighttpd_sa_2014_01.txt Other changes : - [network/ssl] fix build error if TLSEXT is disabled - [mod_fastcgi] fix use after free (only triggered if fastcgi debug is active) - [mod_rrdtool] fix invalid read (string not null terminated) - [mod_dirlisting] fix memory leak if pcre fails - [mod_fastcgi,mod_scgi] fix resource leaks on spawning backends - [mod_magnet] fix memory leak - add comments for switch fall throughs - remove logical dead code - [buffer] fix length check in buffer_is_equal_right_len - fix resource leaks in error cases on config parsing and other initializations - add force_assert() to enforce assertions as simple assert()s are disabled by -DNDEBUG (fixes #2546) - [mod_cml_lua] fix NULL pointer dereference - force assertion: setting FD_CLOEXEC must work (if available) - [network] check return value of lseek() - fix unchecked return values from stream_open/stat_cache_get_entry - [mod_webdav] fix logic error in handling file creation error - check length of unix domain socket filenames - fix SQL injection / host name validation (thx Jann Horn) for all the changes see /usr/share/doc/packages/lighttpd/NEWS
    last seen 2019-02-21
    modified 2019-01-02
    plugin id 75308
    published 2014-06-13
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=75308
    title openSUSE Security Update : lighttpd (openSUSE-SU-2014:0449-1)
  • NASL family Solaris Local Security Checks
    NASL id SOLARIS11_LIGHTTPD_20140715.NASL
    description The remote Solaris system is missing necessary patches to address security updates : - SQL injection vulnerability in mod_mysql_vhost.c in lighttpd before 1.4.35 allows remote attackers to execute arbitrary SQL commands via the host name, related to request_check_hostname. (CVE-2014-2323) - Multiple directory traversal vulnerabilities in (1) mod_evhost and (2) mod_simple_vhost in lighttpd before 1.4.35 allow remote attackers to read arbitrary files via a .. (dot dot) in the host name, related to request_check_hostname. (CVE-2014-2324)
    last seen 2019-02-21
    modified 2018-11-15
    plugin id 80698
    published 2015-01-19
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=80698
    title Oracle Solaris Third-Party Patch Update : lighttpd (multiple_vulnerabilities_in_lighttpd)
  • NASL family Debian Local Security Checks
    NASL id DEBIAN_DSA-2877.NASL
    description Several vulnerabilities were discovered in the lighttpd web server. - CVE-2014-2323 Jann Horn discovered that specially crafted host names can be used to inject arbitrary MySQL queries in lighttpd servers using the MySQL virtual hosting module (mod_mysql_vhost). This only affects installations with the lighttpd-mod-mysql-vhost binary package installed and in use. - CVE-2014-2324 Jann Horn discovered that specially crafted host names can be used to traverse outside of the document root under certain situations in lighttpd servers using either the mod_mysql_vhost, mod_evhost, or mod_simple_vhost virtual hosting modules. Servers not using these modules are not affected.
    last seen 2019-02-21
    modified 2018-11-28
    plugin id 72992
    published 2014-03-14
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=72992
    title Debian DSA-2877-1 : lighttpd - security update
  • NASL family Fedora Local Security Checks
    NASL id FEDORA_2014-3887.NASL
    description 1.4.35, fixes SA-2014-01, CVE-2014-2323, CVE-2014-2324 [1] http://seclists.org/oss-sec/2014/q1/561 [2] http://download.lighttpd.net/lighttpd/security/lighttpd_sa_2014_01.txt [3] http://www.lighttpd.net/2014/3/12/1.4.35/ 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 73193
    published 2014-03-26
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=73193
    title Fedora 20 : lighttpd-1.4.35-1.fc20 (2014-3887)
  • NASL family Gentoo Local Security Checks
    NASL id GENTOO_GLSA-201406-10.NASL
    description The remote host is affected by the vulnerability described in GLSA-201406-10 (lighttpd: Multiple vulnerabilities) Multiple vulnerabilities have been discovered in lighttpd. Please review the CVE identifiers referenced below for details. Impact : A remote attacker could create a Denial of Service condition. Futhermore, a remote attacker may be able to execute arbitrary SQL statements. Workaround : There is no known workaround at this time.
    last seen 2019-02-21
    modified 2018-07-12
    plugin id 76062
    published 2014-06-16
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=76062
    title GLSA-201406-10 : lighttpd: Multiple vulnerabilities
  • NASL family Web Servers
    NASL id LIGHTTPD_1_4_35.NASL
    description According to its banner, the version of lighttpd running on the remote host is prior to 1.4.35. It is, therefore, affected by the following vulnerabilities : - A SQL injection flaw exists in the 'mod_mysql_vhost' module where user input passed using the hostname is not properly sanitized. A remote attacker can exploit this to inject or manipulate SQL queries, resulting in the manipulation or disclosure of data. (CVE-2014-2323) - A traverse outside of restricted path flaw exists with the 'mod_evhost' and 'mod_simple_vhost' modules where user input passed using the hostname is not properly sanitized. A remote attacker can exploit this to gain access to potentially sensitive data. (CVE-2014-2324) Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.
    last seen 2019-02-21
    modified 2018-07-12
    plugin id 73123
    published 2014-03-20
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=73123
    title lighttpd < 1.4.35 Multiple Vulnerabilities
refmap via4
confirm
debian DSA-2877
hp HPSBGN03191
mlist
  • [oss-security] 20140312 Re: lighttpd 1.4.34 SQL injection and path traversal CVE request
  • [oss-security] 20140312 lighttpd 1.4.34 SQL injection and path traversal CVE request
secunia
  • 57404
  • 57514
suse
  • SUSE-SU-2014:0474
  • openSUSE-SU-2014:0449
  • openSUSE-SU-2014:0496
Last major update 22-08-2016 - 22:07
Published 14-03-2014 - 11:55
Back to Top