BlackBerry QNX Software Development Platform up to 6.5.0 SP1/6.6.0 QNX SDP entropy
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.7 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in BlackBerry QNX Software Development Platform up to 6.5.0 SP1/6.6.0 and classified as critical. The impacted element is an unknown function of the component QNX SDP. Performing a manipulation results in entropy. This vulnerability was named CVE-2017-9371. The attack may be initiated remotely. There is no available exploit.
Details
A vulnerability classified as critical has been found in BlackBerry QNX Software Development Platform up to 6.5.0 SP1/6.6.0 (Operating System). This affects an unknown part of the component QNX SDP. The manipulation with an unknown input leads to a entropy vulnerability. CWE is classifying the issue as CWE-332. The lack of entropy available for, or used by, a Pseudo-Random Number Generator (PRNG) can be a stability and security threat. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
In BlackBerry QNX Software Development Platform (SDP) 6.6.0 and 6.5.0 SP1 and earlier, a loss of integrity vulnerability in the default configuration of the QNX SDP could allow an attacker being able to reduce the entropy of the PRNG, making other blended attacks more practical by gaining control over environmental factors that influence seed generation.
The bug was discovered 11/14/2017. The weakness was presented 11/14/2017 (Website). The advisory is shared at support.blackberry.com. This vulnerability is uniquely identified as CVE-2017-9371 since 06/02/2017. The exploitability is told to be difficult. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 08/22/2025). MITRE ATT&CK project uses the attack technique T1600.001 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
See VDB-109412 for similar entry. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.7VulDB Meta Temp Score: 4.7
VulDB Base Score: 5.6
VulDB Temp Score: 5.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.9
NVD Vector: 🔍
CNA Base Score: 2.6
CNA Vector: 🔍
CVSSv2
| 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: 🔍
Exploiting
Class: EntropyCWE: CWE-332 / CWE-331 / CWE-330
CAPEC: 🔍
ATT&CK: 🔍
Physical: Yes
Local: Partially
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 |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
06/02/2017 🔍11/14/2017 🔍
11/14/2017 🔍
11/14/2017 🔍
11/15/2017 🔍
08/22/2025 🔍
Sources
Advisory: support.blackberry.comStatus: Not defined
Confirmation: 🔍
CVE: CVE-2017-9371 (🔍)
GCVE (CVE): GCVE-0-2017-9371
GCVE (VulDB): GCVE-100-109413
See also: 🔍
Entry
Created: 11/15/2017 11:23Updated: 08/22/2025 18:35
Changes: 11/15/2017 11:23 (58), 12/06/2019 15:42 (2), 08/22/2025 18:35 (27)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.