SOGo up to 2.3.11/3.1.0 Appointment information disclosure

Summaryinfo

A vulnerability marked as problematic has been reported in SOGo up to 2.3.11/3.1.0. This issue affects some unknown processing of the component Appointment Handler. Performing a manipulation results in information disclosure. This vulnerability is identified as CVE-2016-6190. The attack can be initiated remotely. There is not any exploit available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability classified as problematic has been found in SOGo up to 2.3.11/3.1.0. This affects an unknown code of the component Appointment Handler. The manipulation with an unknown input leads to a information disclosure vulnerability. CWE is classifying the issue as CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. This is going to have an impact on confidentiality. The summary by CVE is:

SOGo before 2.3.12 and 3.x before 3.1.1 does not restrict access to the UID and DTSTAMP attributes, which allows remote authenticated users to obtain sensitive information about appointments with the "View the Date & Time" restriction, as demonstrated by correlating UIDs and DTSTAMPs between all users.

The bug was discovered 07/09/2016. The weakness was released 02/17/2017 (oss-sec). The advisory is shared at openwall.com. This vulnerability is uniquely identified as CVE-2016-6190 since 07/09/2016. It is possible to initiate the attack remotely. A authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.

The vulnerability was handled as a non-public zero-day exploit for at least 223 days. During that time the estimated underground price was around $0-$5k. The vulnerability scanner Nessus provides a plugin with the ID 246992 (Linux Distros Unpatched Vulnerability : CVE-2016-6190), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 2.3.12 or 3.1.1 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at Tenable (246992). Entries connected to this vulnerability are available at VDB-96533, VDB-97082, VDB-97100 and VDB-97102. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• SOGo

Version

• 2.3.0
• 2.3.1
• 2.3.2
• 2.3.3
• 2.3.4
• 2.3.5
• 2.3.6
• 2.3.7
• 2.3.8
• 2.3.9
• 2.3.10
• 2.3.11
• 3.0
• 3.1.0

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion