RIM BlackBerry 10 BBM information disclosure

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.
4.9	$0-$5k	0.00

Summaryinfo

A vulnerability was found in RIM BlackBerry 10. It has been classified as problematic. This affects an unknown part of the component BBM. The manipulation leads to information disclosure. In addition, an exploit is available. It is advisable to use the suggested workaround.

Detailsinfo

A vulnerability was found in RIM BlackBerry 10. It has been rated as problematic. This issue affects an unknown code block of the component BBM. The manipulation with an unknown input leads to a information disclosure vulnerability. Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality.

The weakness was presented 03/31/2013 as not defined posting (Website). The advisory is shared at crackberry.com. The public release happened without involvement of RIM. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are unknown but a public exploit is available. MITRE ATT&CK project uses the attack technique T1592 for this issue.

After immediately, there has been an exploit disclosed. The exploit is available at geek.com. It is declared as proof-of-concept.

The best possible mitigation is suggested to be Workaround.

The vulnerability is also documented in the vulnerability database at OSVDB (91894†). crackberry.com is providing further details. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

Name

BlackBerry

Version

License

commercial

Website

Vendor: http://www.rim.com/

CPE 2.3info

🔍

CPE 2.2info

🔍

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.3
VulDB Meta Temp Score: 4.9

VulDB Base Score: 5.3
VulDB Temp Score: 4.9
VulDB Vector: 🔍
VulDB Reliability: 🔍

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

Exploitinginfo

Class: Information disclosure
CWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍

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

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Workaround
Status: 🔍

0-Day Time: 🔍
Exploit Delay Time: 🔍

Workaround: Disable BBM

Timelineinfo

03/31/2013 🔍
03/31/2013 +0 days 🔍
04/04/2013 +4 days 🔍
05/05/2018 +1857 days 🔍

Sourcesinfo

Vendor: rim.com

Advisory: crackberry.com
Status: Not defined

GCVE (VulDB): GCVE-100-8153
OSVDB: 91894

scip Labs: https://www.scip.ch/en/?labs.20161013
Misc.: 🔍

Entryinfo

Created: 04/04/2013 16:19
Updated: 05/05/2018 18:00
Changes: 04/04/2013 16:19 (46), 05/05/2018 18:00 (1)
Complete: 🔍
Committer:
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.