CVE-2022-31460
Published: 02 June 2022
Summary
CVE-2022-31460 is a high-severity Use of Hard-coded Credentials (CWE-798) vulnerability in Owllabs Meeting Owl Pro Firmware. Its CVSS base score is 7.4 (High).
Operationally, ranked in the top 9.0% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
Deeper analysis
Owl Labs Meeting Owl version 5.2.0.15 contains a use of hard-coded credentials vulnerability (CWE-798) that permits activation of Tethering Mode through a specific command value when the fixed "hoothoot" credentials are supplied. The affected component is the videoconferencing hardware itself, which exposes this functionality over the local network without requiring authentication or user interaction.
An attacker with adjacent network access can exploit the flaw to enable Tethering Mode, resulting in a high-integrity impact within a changed scope as reflected by the CVSS 7.4 rating. This allows unauthorized control over device connectivity features that would otherwise be restricted.
Vendor advisories and the associated security disclosure report indicate that Owl Labs released firmware updates to address the issue, with installation guidance provided through their support resources. The references also point to independent analysis confirming the presence of the hard-coded credential mechanism in the examined firmware.
The EPSS score has remained flat at 0.0617 with no material increase observed after disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2022-52924
Vulnerability details
Owl Labs Meeting Owl 5.2.0.15 allows attackers to activate Tethering Mode with hard-coded hoothoot credentials via a certain c 150 value.
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Enables users to notice when hard-coded credentials have been exploited for unauthorized access.
Security training explicitly warns against hard-coded credentials, lowering their use in systems.
Policy and procedures prohibit hard-coded credentials in favor of managed authentication.
External identity providers eliminate the need for hard-coded credentials in applications.
Changing default authenticators prior to first use and protecting content prevents use of hard-coded credentials.
Central credential stores and rotation policies remove the need for hard-coded credentials in configuration files or code.
Intelligence programs surface reports of campaigns that abuse hard-coded credentials in products, prompting removal or replacement and thereby reducing successful exploitation.
Planned investment enables secure credential storage and management systems instead of hard-coded credentials.