dbcve.org
Qnx MomenticsApplication · Blackberry

CVE-2021-32025

HIGH · 7.8 CVSS v3.1 Published 2022-03-10
Fix available
A fix is available. Upgrade to 1.0.3 / 1.1.2 or later.
See remediation →
80/100
Remediation priority · High
Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An elevation of privilege vulnerability in the QNX Neutrino Kernel of affected versions of QNX Software Development Platform version(s) 6.4.0 to 7.0, QNX Momentics all 6.3.x versions, QNX OS for Safety versions 1.0.0 to 1.0.2, QNX OS for Safety versions 2.0.0 to 2.0.1, QNX for Medical versions 1.0.0 to 1.1.1, and QNX OS for Medical version 2.0.0 could allow an attacker to potentially access data, modify behavior, or permanently crash the system.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Qnx MomenticsApplication
Affected:= 6.3.0= 6.3.2
Qnx Software Development PlatformApplication
Affected:>= 6.4.0, <= 7.0
Qnx Os For MedicalOperating system
Affected:>= 1.0, < 1.1.2= 2.0.0
Qnx Os For SafetyOperating system
Affected:>= 1.0.0, < 1.0.3>= 2.0.0, < 2.0.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.0.3 / 1.1.2 / 2.0.2 or later
Fixed in 1.0.31.1.22.0.2
Vendor patch support.blackberry.com →
Recommended fix High confidence

QNX OS for Safety 1.0.3+, QNX OS for Safety 2.0.2+, QNX OS for Medical 1.1.2+, QNX OS for Medical 2.0.1+, QNX Software Development Platform 7.0.1+, or QNX Momentics 6.3.3+ (whichever applicable)

  1. 1. Navigate to the official BlackBerry support article at http://support.blackberry.com/kb/articleDetail?articleNumber=000090868 to obtain the vendor patch.
  2. 2. Identify your specific QNX product and version from the affected versions list.
  3. 3. Download the corresponding security patch for your product version.
  4. 4. Apply the patch according to the vendor's installation instructions provided in the support article.
  5. 5. Reboot the affected system to ensure the kernel fix takes effect.
  6. 6. Verify the patch has been successfully applied by checking the system version or using vendor-provided verification tools.

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-32025 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-32025 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data