Is CVE-2016-3130 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2016-3130 being exploited in the wild.

How severe is CVE-2016-3130?

High severity, with a CVSS score of 8.1, published 13 January 2017.

Which products and versions are affected?

BlackBerry Enterprise Service (BES) 12 12 through 12.5.2.

Is there a fix for CVE-2016-3130?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2016-3130 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2016-3130?

Check whether you run Blackberry Enterprise Service 12. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2016-3130: BlackBerry Enterprise Server information disclosure in Management Console

CVE-2016-3130 · Severity: high · CVSS 8.1 · Published 2017-01-13

A security vulnerability in BlackBerry Enterprise Server (BES) 12 could allow an attacker to intercept sensitive login information. By monitoring network traffic between the server's core components and its management console, an attacker could capture the usernames and passwords of administrators or regular users. This could lead to unauthorized access to the management system and potential compromise of the organization's mobile device management infrastructure.

Vendors: Blackberry.

Quick answers

Is CVE-2016-3130 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2016-3130 being exploited in the wild.
How severe is CVE-2016-3130?: High severity, with a CVSS score of 8.1, published 13 January 2017.
Which products and versions are affected?: BlackBerry Enterprise Service (BES) 12 12 through 12.5.2.
Is there a fix for CVE-2016-3130?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2016-3130 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2016-3130?: Check whether you run Blackberry Enterprise Service 12. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

An information disclosure vulnerability exists in BlackBerry Enterprise Server (BES) versions 12 through 12.5.2. The flaw is located within the communication channel between the BES Core and the Management Console. A remote attacker positioned to perform network sniffing (e.g., via a man-in-the-middle position) can intercept unencrypted or insufficiently protected traffic during login attempts. This allows the attacker to obtain plaintext local or domain credentials for administrator or user accounts. The vulnerability is classified under CWE-200 (Information Exposure) and CWE-255 (Credentials Management Errors). Users are advised to upgrade to a patched version of BES to ensure secure communication between internal components.

Affected products

BlackBerry Enterprise Service (BES) 12 12 through 12.5.2

Timeline

2017-01-13: disclosed
2017-01-13: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.