DIGISOL DG-BR4000NG Authorization Header HTTP Header memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.2 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in DIGISOL DG-BR4000NG. This vulnerability affects unknown code of the component Authorization Header Handler. The manipulation as part of HTTP Header leads to memory corruption. This vulnerability is uniquely identified as CVE-2018-12706. The attack is possible to be carried out remotely. Moreover, an exploit is present.
Details
A vulnerability, which was classified as critical, has been found in DIGISOL DG-BR4000NG (the affected version is unknown). This issue affects an unknown code of the component Authorization Header Handler. The manipulation as part of a HTTP Header leads to a memory corruption vulnerability. Using CWE to declare the problem leads to CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
DIGISOL DG-BR4000NG devices have a Buffer Overflow via a long Authorization HTTP header.
The bug was discovered 06/24/2018. The weakness was disclosed 06/24/2018 (Website). The advisory is shared at hackings8n.blogspot.com. The identification of this vulnerability is CVE-2018-12706 since 06/23/2018. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are unknown but a public exploit is available.
The exploit is available at exploit-db.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.
The vulnerability is also documented in the vulnerability database at Exploit-DB (44934). The entry VDB-119836 is pretty similar. 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: 8.5VulDB Meta Temp Score: 8.4
VulDB Base Score: 7.3
VulDB Temp Score: 6.9
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
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: Memory corruptionCWE: CWE-119
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 |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
Timeline
06/23/2018 🔍06/24/2018 🔍
06/24/2018 🔍
06/24/2018 🔍
06/25/2018 🔍
07/25/2024 🔍
Sources
Advisory: hackings8n.blogspot.comStatus: Not defined
CVE: CVE-2018-12706 (🔍)
GCVE (CVE): GCVE-0-2018-12706
GCVE (VulDB): GCVE-100-119837
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 06/25/2018 08:44Updated: 07/25/2024 22:17
Changes: 06/25/2018 08:44 (57), 02/21/2020 15:20 (4), 07/25/2024 22:17 (18)
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.