owllabs vulnerabilities
Recent CVEs affecting owllabs products. 5 tracked.
owllabs has 5 tracked vulnerabilities, 1 critical. A fixed release or vendor patch exists for 5. Most recent: 2022-06-02. Highest priority: CVE-2022-31460 (score 53/100).
- CVE-2022-31463 HIGH 8.2 UPGRADE Owl Labs Meeting Owl 5.2.0.15 does not require a password for Bluetooth commands, because only client-side aut
- CVE-2022-31462 CRITICAL 9.3 UPGRADE Owl Labs Meeting Owl 5.2.0.15 allows attackers to control the device via a backdoor password (derived from the
- CVE-2022-31461 HIGH 7.4 UPGRADE Owl Labs Meeting Owl 5.2.0.15 allows attackers to deactivate the passcode protection mechanism via a certain c
- CVE-2022-31460 HIGH 7.4 UPGRADE Owl Labs Meeting Owl 5.2.0.15 allows attackers to activate Tethering Mode with hard-coded hoothoot credentials
- CVE-2022-31459 HIGH 7.4 UPGRADE Owl Labs Meeting Owl 5.2.0.15 allows attackers to retrieve the passcode hash via a certain c 10 value over Blu
FAQ
How do I fix owllabs 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 owllabs being exploited right now?
None of the tracked owllabs CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which owllabs CVE should I patch first?
CVE-2022-31460 currently ranks highest (53/100): Owl Labs Meeting Owl 5.2.0.15 allows attackers to activate Tethering Mode with hard-coded hoothoot credentials.