Home
» Security vulnerabilities
» CVE-2022-31463
Owl Labs Meeting Owl 5.2.0.15 does not require a password for Bluetooth commands, because only client-side authentication is used.
NVD Status： Modified ，CVE State: published
Threat Intelligence & Risk Assessment for CVE-2022-31463
Conclusion & alert: CVE-2022-31463 is rated High Exploit Risk (68.5/100) : CVSS High severity, with medium exploitation likelihood (EPSS 0.97%).Core evidence: 1 public exploit reference(s) are indexed (Exploit-DB).Mandatory action: Public exploits are available—assess exposure, apply mitigations, and prioritize patching.
Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.
Public exploit references (Exploit-DB) for CVE-2022-31463
EDB-ID
Source
Kind
Published
Link
—
nvd_ref
exploit_tag
Exploit-DB ↗
Exploit prediction scoring system (EPSS) score for CVE-2022-31463
EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).
#
Date
Old EPSS score
New EPSS score
Delta (New - Old)
1
2026-06-15
0.19%
0.97%
+0.78%
2
2025-11-21
0.08%
0.19%
+0.10%
3
2025-11-18
—
0.08%
—
Full EPSS history
(13 records total)
Common vulnerability scoring system (CVSS) metrics for CVE-2022-31463
CVSS metrics for this CVE.
Base score
Version
Severity
Vector
Exploitability
Impact
Score source
8.2
3.1
HIGH
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N
Click to expand
Attack vector (AV:A)
Attacker has to be nearby on the network—same office, same link, that vibe—not the whole wide internet.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
2.8
4.7
[email protected]
7.1
3.1
HIGH
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
Click to expand
Attack vector (AV:A)
Attacker has to be nearby on the network—same office, same link, that vibe—not the whole wide internet.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
2.8
4.2
[email protected]
4.3
2.0
MEDIUM
AV:A/AC:M/Au:N/C:P/I:P/A:N
Click to expand
Access vector (AV:A)
Requires access to an adjacent network segment.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:N)
No availability impact.
5.5
4.9
[email protected]
Weakness enumeration for CVE-2022-31463
Affected software / configurations for CVE-2022-31463
References for CVE-2022-31463
cvelogic
Threat Intelligence