Poly CCX 400/CCX 600/Trio 8800/Trio C60 HTTP Header Cookie denial of service
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic was found in Poly CCX 400, CCX 600, Trio 8800 and Trio C60. The impacted element is an unknown function of the component HTTP Header Handler. Executing a manipulation of the argument Cookie can lead to denial of service. This vulnerability is handled as CVE-2023-4463. The attack can be executed remotely. Additionally, an exploit exists.
Details
A vulnerability classified as problematic was found in Poly CCX 400, CCX 600, Trio 8800 and Trio C60 (version unknown). This vulnerability affects an unknown function of the component HTTP Header Handler. The manipulation of the argument Cookie with an unknown input leads to a denial of service vulnerability. The CWE definition for the vulnerability is CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. As an impact it is known to affect 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 for download at modzero.com. This vulnerability was named CVE-2023-4463. Technical details and also a public exploit are known. The MITRE ATT&CK project declares the attack technique as T1499. The advisory points out:
The webserver of the device expects the user to authenticate through a cookie. When the HTTP header “Cookie” is sent to the server and it contains the expected cookie name (“session”) but does not include a corresponding value [...], the device crashes, and it reboots.
It is possible to download the exploit 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.
Additional details are provided at fahrplan.events.ccc.de. VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Vendor
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
Researcher Base Score: 7.5
Researcher Vector: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
CNA Base Score: 5.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: Denial of serviceCWE: CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
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: Confirmed
CVE: CVE-2023-4463 (🔍)
GCVE (CVE): GCVE-0-2023-4463
GCVE (VulDB): GCVE-100-249256
Misc.: 🔍
Entry
Created: 12/29/2023 10:28Updated: 01/21/2024 07:20
Changes: 12/29/2023 10:28 (39), 12/29/2023 10:31 (15), 12/29/2023 10:38 (1), 01/09/2024 17:12 (2), 01/21/2024 07:15 (2), 01/21/2024 07:20 (27)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.