CyberSecBulletin
CVE-2022-31462NVD status: Modified

Meeting Owl Pro Firmware: Use of Hard-coded Credentials

Published Updated By the CyberSecBulletin desk

CVE-2022-31462 is a high-severity use of hard-coded credentials vulnerability in Meeting Owl Pro Firmware from Owllabs, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited from the same local network by an unauthenticated attacker, without any action from a user. The record lists version 5.4.2.3 as the first without the flaw, so updating Meeting Owl Pro Firmware to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.81% chance of exploitation within 30 days, higher than 58% of scored CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Meeting Owl Pro Firmware to 5.4.2.3 or a later version.
  2. Read the advisory on resources.owllabs.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
OwllabsMeeting Owl Pro Firmwarebefore 5.4.2.35.4.2.3

Version data comes from NVD's product matching. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
AdjacentThe attacker must be on the same local network segment.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.19.3CriticalCNA (mitre.org)
CVSS 3.18.8HighNVD
CVSS 2.05.4MediumNVD

Official description

Owl Labs Meeting Owl 5.2.0.15 allows attackers to control the device via a backdoor password (derived from the serial number) that can be found in Bluetooth broadcast data.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Use of Hard-coded Credentials

The product contains hard-coded credentials, such as a password or cryptographic key.

How developers prevent this class of flaw

  • For outbound authentication: store passwords, keys, and other credentials outside of the code in a strongly-protected, encrypted configuration file or database that is protected from access by all outsiders, including other local users on the same system. Properly protect the key (CWE-320). If you cannot use encryption to protect the file, then make sure that the permissions are as restrictive as possible. In Windows environments, the Encrypted File System (EFS) may provide some protection.
  • For inbound authentication: Rather than hard-code a default username and password, key, or other authentication credentials for first time logins, utilize a first login mode that requires the user to enter a unique strong password or key.
  • If the product must contain hard-coded credentials or they cannot be removed, perform access control checks and limit which entities can access the feature that requires the hard-coded credentials. For example, a feature might only be enabled through the system console instead of through a network connection.

More Use of Hard-coded Credentials vulnerabilities (CWE-798)

Timeline

  1. CVE record published.
  2. Record last changed materially (score, affected products, status or references).

References

Technical write-ups (may include proof of concept)

Recent Use of Hard-coded Credentials vulnerabilities

Spotted an error? Tell us.