Elasticsearch up to 1.6.0 Transport Protocol injection ⚔ [Disputed]

Summaryinfo

A vulnerability was found in Elasticsearch up to 1.6.0. It has been rated as critical. This issue affects some unknown processing of the component Transport Protocol. The manipulation leads to injection. This vulnerability is uniquely identified as CVE-2015-5377. The attack is possible to be carried out remotely. No exploit exists. It is still unclear if this vulnerability genuinely exists. Upgrading the affected component is advised.

Detailsinfo

A vulnerability was found in Elasticsearch up to 1.6.0 and classified as critical. This issue affects an unknown function of the component Transport Protocol. The manipulation with an unknown input leads to a injection vulnerability. Using CWE to declare the problem leads to CWE-74. The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

** DISPUTED ** Elasticsearch before 1.6.1 allows remote attackers to execute arbitrary code via unspecified vectors involving the transport protocol. NOTE: ZDI appears to claim that CVE-2015-3253 and CVE-2015-5377 are the same vulnerability.

The bug was discovered 07/16/2015. The weakness was disclosed 03/06/2018 by cpnrodzc7 (Website) via ZDI (Zero Day Initiative). It is possible to read the advisory at discuss.elastic.co. The identification of this vulnerability is CVE-2015-5377 since 07/06/2015. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1055 according to MITRE ATT&CK.

The vulnerability was handled as a non-public zero-day exploit for at least 20 days. During that time the estimated underground price was around $0-$5k. The real existence of this vulnerability is still doubted at the moment. The vulnerability scanner Nessus provides a plugin with the ID 85246 (FreeBSD : elasticsearch -- remote code execution via transport protocol (fb3668df-32d7-11e5-a4a5-002590263bf5)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family FreeBSD Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 11585 (Elasticsearch transport.tcp.port Remote Code Execution Vulnerability).

Upgrading to version 1.6.1 eliminates this vulnerability. A possible mitigation has been published before and not just after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Tenable (85246) and SecurityFocus (BID 75938†). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Name

• Elasticsearch

Version

• 0.20.0
• 0.20.1
• 0.20.2
• 0.20.3
• 0.20.4
• 0.20.5
• 0.20.6
• 0.90.0
• 0.90.0.Beta1
• 0.90.0.RC1
• 0.90.0.RC2
• 0.90.1
• 0.90.2
• 0.90.3
• 0.90.4
• 0.90.5
• 0.90.6
• 0.90.7
• 0.90.8
• 0.90.9
• 0.90.10
• 0.90.11
• 0.90.12
• 0.90.13
• 1.0.0
• 1.0.0.Beta1
• 1.0.0.Beta2
• 1.0.0.RC1
• 1.0.0.RC2
• 1.1.0
• 1.1.1
• 1.1.2
• 1.2.0
• 1.2.1
• 1.2.2
• 1.2.3
• 1.3.0
• 1.3.1
• 1.3.2
• 1.3.3
• 1.3.4
• 1.3.5
• 1.3.6
• 1.3.7
• 1.3.8
• 1.3.9
• 1.4.0
• 1.4.0.Beta1
• 1.4.1
• 1.4.2
• 1.4.3
• 1.4.4
• 1.4.5
• 1.5.0
• 1.5.1
• 1.5.2
• 1.6.0

License

• free

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion