BlackBerry QNX Software Development Platform up to 6.6.0 Slinger Web Server control sequence
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.0 | $5k-$25k | 0.00 |
Summary
A vulnerability has been found in BlackBerry QNX Software Development Platform up to 6.6.0 and classified as critical. This impacts an unknown function of the component Slinger Web Server. Performing a manipulation results in input validation. This vulnerability is cataloged as CVE-2020-6932. It is possible to initiate the attack remotely. There is no exploit available.
Details
A vulnerability was found in BlackBerry QNX Software Development Platform up to 6.6.0 (Operating System). It has been classified as critical. This affects an unknown part of the component Slinger Web Server. The manipulation with an unknown input leads to a input validation vulnerability. CWE is classifying the issue as CWE-150. The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as escape, meta, or control character sequences when they are sent to a downstream component. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
An information disclosure and remote code execution vulnerability in the slinger web server of the BlackBerry QNX Software Development Platform versions 6.4.0 to 6.6.0 could allow an attacker to potentially read arbitrary files and run arbitrary executables in the context of the web server.
The weakness was shared 08/12/2020. This vulnerability is uniquely identified as CVE-2020-6932 since 01/13/2020. The exploitability is told to be easy. 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 $5k-$25k at the moment (estimation calculated on 08/22/2025).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 9.0VulDB Meta Temp Score: 9.0
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CNA Base Score: 10.0
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: Control sequenceCWE: CWE-150 / 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 |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
01/13/2020 🔍08/12/2020 🔍
08/13/2020 🔍
08/22/2025 🔍
Sources
Status: Not definedCVE: CVE-2020-6932 (🔍)
GCVE (CVE): GCVE-0-2020-6932
GCVE (VulDB): GCVE-100-159729
Entry
Created: 08/13/2020 07:03Updated: 08/22/2025 18:35
Changes: 08/13/2020 07:03 (36), 08/13/2020 07:08 (18), 08/22/2025 18:35 (29)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.