MetInfo 6.1.3 HTTP Header applogin.php $_COOKIE response splitting

Summaryinfo

A vulnerability described as critical has been identified in MetInfo 6.1.3. This affects an unknown part of the file include/interface/applogin.php of the component HTTP Header Handler. Executing a manipulation of the argument $_COOKIE as part of Variable can lead to response splitting. This vulnerability is handled as CVE-2018-19836. The attack can be executed remotely. There is not any exploit available.

Detailsinfo

A vulnerability has been found in MetInfo 6.1.3 (Content Management System) and classified as critical. This vulnerability affects an unknown code block of the file include/interface/applogin.php of the component HTTP Header Handler. The manipulation of the argument $_COOKIE as part of a Variable leads to a response splitting vulnerability. The CWE definition for the vulnerability is CWE-113. The product receives data from an HTTP agent/component (e.g., web server, proxy, browser, etc.), but it does not neutralize or incorrectly neutralizes CR and LF characters before the data is included in outgoing HTTP headers. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

In Metinfo 6.1.3, include/interface/applogin.php allows setting arbitrary HTTP headers (including the Cookie header), and common.inc.php allows registering variables from the $_COOKIE value. This issue can, for example, be exploited in conjunction with CVE-2018-19835 to bypass many XSS filters such as the Chrome XSS filter.

The bug was discovered 12/02/2018. The weakness was released 12/03/2018 (Website). The advisory is available at github.com. This vulnerability was named CVE-2018-19836 since 12/03/2018. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Technical details are known, but there is no available exploit.

The vulnerability was handled as a non-public zero-day exploit for at least 1 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:include/interface/applogin.php it is possible to find vulnerable targets with Google Hacking.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Entry connected to this vulnerability is available at VDB-127425. If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

• Content Management System

Name

• MetInfo

Version

• 6.1.3

License

• commercial

CPE 2.3info

• 🔍

CPE 2.2info

• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion