Administrator-level code execution via message broker
Published Nov 10, 2021 · Updated Aug 3, 2024
Code execution in the message broker of BlackBerry Protect for Windows 1574 and earlier allows local users to run code with service administrator rights. BlackBerry identifies the message broker as the vulnerable locus but has not published the malformed input, message path, or erroneous operation that triggers the condition. Low local privileges are required; successful exploitation places code in an administrator-rights Cylance service context, enabling host data access, modification, and service interruption.
Summary
What happened
Code execution in the message broker of BlackBerry Protect for Windows 1574 and earlier allows local users to run code with service administrator rights. BlackBerry identifies the message broker as the vulnerable locus but has not published the malformed input, message path, or erroneous operation that triggers the condition. Low local privileges are required; successful exploitation places code in an administrator-rights Cylance service context, enabling host data access, modification, and service interruption.
The record
- CVE
- CVE-2021-32021
- Published
- Nov 10, 2021
- Updated
- Aug 3, 2024
- Vendor
- BlackBerry
- Product
- BlackBerry Protect for Windows
- Classifications
- T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 10, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Version 1574 and earlier
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo