protect vulnerabilities and fixes
Recent CVEs affecting protect, with upgrade or downgrade steps. 4 tracked.
protect has 4 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 3. Most recent: 2022-06-16. Highest priority: CVE-2022-31464 (score 40/100).
- CVE-2022-31464 HIGH 7.8 DOWNGRADE Insecure permissions configuration in Adaware Protect v1.2.439.4251 allows attackers to escalate privileges vi
- CVE-2021-32023 HIGH 7.8 UPGRADE An elevation of privilege vulnerability in the message broker of BlackBerry Protect for Windows version(s) ver
- CVE-2021-32022 MEDIUM 5.5 UPGRADE A low privileged delete vulnerability using CEF RPC server of BlackBerry Protect for Windows version(s) versio
- CVE-2021-32021 HIGH 7.8 UPGRADE A denial of service vulnerability in the message broker of BlackBerry Protect for Windows version(s) versions
FAQ
How do I fix protect vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is protect being exploited right now?
None of the tracked protect CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which protect CVE should I patch first?
CVE-2022-31464 currently ranks highest (40/100): Insecure permissions configuration in Adaware Protect v1.2.439.4251 allows attackers to escalate privileges vi.