CVE-2019-8998 json
An information disclosure vulnerability leading to a potential local escalation of privilege in the procfs service (the /proc filesystem) o…
published 2019-07-12 7 y ago modified 2026-06-17 4 mo ago also EUVD-2019-18385
- cvss
- 7.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 12%
- public exploits
- 0
- none known
Summary
An information disclosure vulnerability leading to a potential local escalation of privilege in the procfs service (the /proc filesystem) of BlackBerry QNX Software Development Platform version(s) 6.5.0 SP1 and earlier could allow an attacker to potentially gain unauthorized access to a chosen process address space.
Patch / fix
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSA-19-262-01 updated cvss 7.8
Tridium Niagara
-
Tridium Niagara 4.7u1 (JACE-8000 Edge 10), 4.4u3 (JACE 3e JACE 6e JACE 7 JACE-8000) Tridium Niagara AX 3.8u4 (JACE 3e JACE 6e JACE 7 JACE-8000)affected: vendor fix, mitigation “Niagara 4.4u3: OS Dist: 4.4.73.38.1 NRE Config” tridium.com
From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf
Exploit prediction
0.22% chance of exploitation in the next 30 days, higher than 12% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H |
| NVD | 3.0 | 7.8 | CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 4.6 | AV:L/AC:L/Au:N/C:P/I:P/A:P |
Affected products
- BlackBerry QNX Software Development Platform (QNX SDP)
Classification
- Weakness
-
- CWE-413 Improper Resource Locking
References
-
support.blackberry.com
/kb/articleDetail?articleNumber=000057178
mitigation, patch, vendor-advisory
Sources
- CVE List CVE-2019-8998
- NVD CVE-2019-8998
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.