VDB-93219 · CVE-2016-6496 · BID 93826

Crowd up to 2.8.7/2.9.4 LDAP input validation

CVSS Meta Temp Score CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.	Current Exploit Price (≈) Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.	CTI Interest Score Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
9.0	$0-$5k	0.00

Summaryinfo

A vulnerability was found in Crowd up to 2.8.7/2.9.4. It has been rated as critical. Impacted is an unknown function of the component LDAP. Performing a manipulation results in input validation. This vulnerability is cataloged as CVE-2016-6496. It is possible to initiate the attack remotely. There is no exploit available. Upgrading the affected component is advised.

Detailsinfo

A vulnerability was found in Crowd up to 2.8.7/2.9.4. It has been classified as very critical. This affects an unknown function of the component LDAP. The manipulation with an unknown input leads to a input validation vulnerability. CWE is classifying the issue as CWE-20. The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

The LDAP directory connector in Atlassian Crowd before 2.8.8 and 2.9.x before 2.9.5 allows remote attackers to execute arbitrary code via an LDAP attribute with a crafted serialized Java object, aka LDAP entry poisoning.

The weakness was shared 10/31/2016 by Alvaro Munoz and Alexander Mirosh as October 2016 - Crowd - Critical Security Advisory as not defined mailinglist post (Bugtraq). It is possible to read the advisory at seclists.org. The vendor cooperated in the coordination of the public release. This vulnerability is uniquely identified as CVE-2016-6496 since 08/01/2016. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 05/21/2019). The advisory points out:

The Crowd LDAP directory connector allowed an attacker to gain remote code execution in Crowd by injecting malicious attributes in LDAP entries. To exploit this issue, attackers either need to modify an entry in an LDAP directory that Crowd is configured to use or successfully execute a Man-in-The-Middle attack between an LDAP server and Crowd. Crowd installations configured to communicate with an LDAP server using the LDAPS protocol with the Secure SSL option enabled are immune to the Man-in-The-Middle attack vector only (unless an attacker is able to obtain the private key of the SSL/TLS certificate used to secure the communication).

Upgrading to version 2.8.8, 2.9.5 or 2.10.1 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 93826†). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Affected

Crowd up to 1.4.1

Productinfo

Name

Crowd

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 9.8
VulDB Meta Temp Score: 9.4

VulDB Base Score: 9.8
VulDB Temp Score: 9.0
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 9.8
NVD Vector: 🔍

CVSSv2info

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: 🔍

Exploitinginfo

Class: Input validation
CWE: CWE-20
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-Day	Unlock	Unlock	Unlock	Unlock
Today	Unlock	Unlock	Unlock	Unlock

OpenVAS ID: 103512
OpenVAS Name: Atlassian Crowd LDAP Java Object Injection Vulnerability
OpenVAS File: 🔍
OpenVAS Family: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: Crowd 2.8.8/2.9.5/2.10.1

Timelineinfo

08/01/2016 🔍
10/19/2016 +79 days 🔍
10/31/2016 +12 days 🔍
10/31/2016 +0 days 🔍
12/09/2016 +39 days 🔍
05/21/2019 +893 days 🔍

Sourcesinfo

Advisory: October 2016 - Crowd - Critical Security Advisory
Researcher: Alvaro Munoz, Alexander Mirosh
Status: Not defined
Confirmation: 🔍
Coordinated: 🔍

CVE: CVE-2016-6496 (🔍)
GCVE (CVE): GCVE-0-2016-6496
GCVE (VulDB): GCVE-100-93219
SecurityFocus: 93826 - Atlassian Crowd CVE-2016-6496 LDAP Injection Vulnerability

Entryinfo

Created: 10/31/2016 21:39
Updated: 05/21/2019 11:00
Changes: 10/31/2016 21:39 (60), 05/21/2019 11:00 (12)
Complete: 🔍
Cache ID: 216:32A:103

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