Poly Trio 8500/Trio 8800/Trio C60 Poly Lens Management Cloud Registration authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Poly Trio 8500, Trio 8800 and Trio C60. It has been classified as critical. Affected by this issue is some unknown functionality of the component Poly Lens Management Cloud Registration. Performing a manipulation results in authorization. This vulnerability is identified as CVE-2023-4468. The attack may be carried out on the physical device. Additionally, an exploit exists.
Details
A vulnerability was found in Poly Trio 8500, Trio 8800 and Trio C60 (unknown version). It has been classified as problematic. This affects an unknown code block of the component Poly Lens Management Cloud Registration. The manipulation with an unknown input leads to a authorization vulnerability. CWE is classifying the issue as CWE-862. The product does not perform an authorization check when an actor attempts to access a resource or perform an action. This is going to have an impact on confidentiality, integrity, and availability.
The weakness was released 12/29/2023 by Christoph Wolff and Pascal Zenker with modzero AG as MZ-23-01. The advisory is shared at modzero.com. This vulnerability is uniquely identified as CVE-2023-4468. Technical details are unknown but a public exploit is available. The advisory points out:
To register a Poly device in the Poly Lens management cloud, a short alphanumeric code must be entered. This code is displayed on the device, without having to enter the administrator’s PIN. Registering the device allows for administrative access via the Lens interface, providing an elevation of privilege to a local attacker.
The exploit is shared for download at github.com. It is declared as proof-of-concept.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Further details are available at fahrplan.events.ccc.de. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.4
VulDB Base Score: 4.3
VulDB Temp Score: 3.9
VulDB Vector: 🔍
VulDB Reliability: 🔍
Researcher Base Score: 5.7
Researcher Vector: 🔍
NVD Base Score: 7.6
NVD Vector: 🔍
CNA Base Score: 4.3
CNA Vector (VulDB): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: AuthorizationCWE: CWE-862 / CWE-863 / CWE-285
CAPEC: 🔍
ATT&CK: 🔍
Physical: Yes
Local: Yes
Remote: No
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
08/21/2023 🔍12/29/2023 🔍
12/29/2023 🔍
01/21/2024 🔍
Sources
Advisory: MZ-23-01Researcher: Christoph Wolff, Pascal Zenker
Organization: modzero AG
Status: Not defined
Confirmation: 🔍
CVE: CVE-2023-4468 (🔍)
GCVE (CVE): GCVE-0-2023-4468
GCVE (VulDB): GCVE-100-249261
Misc.: 🔍
Entry
Created: 12/29/2023 10:28Updated: 01/21/2024 08:12
Changes: 12/29/2023 10:28 (39), 12/29/2023 10:36 (15), 12/29/2023 10:41 (2), 01/09/2024 17:12 (2), 01/09/2024 17:20 (3), 01/21/2024 08:10 (2), 01/21/2024 08:12 (28)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.