Netis WF2880/WF2411 2.1.36123 HTTP Header /bin/boa Authorization memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.4 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical was found in Netis WF2880 and WF2411 2.1.36123. This impacts an unknown function of the file /bin/boa of the component HTTP Header Handler. Such manipulation of the argument Authorization as part of GET Request leads to memory corruption. This vulnerability is documented as CVE-2019-8985. The attack can be executed remotely. There is not any exploit available. Restrictive firewalling should be applied.
Details
A vulnerability, which was classified as critical, has been found in Netis WF2880 and WF2411 2.1.36123. Affected by this issue is an unknown function of the file /bin/boa of the component HTTP Header Handler. The manipulation of the argument Authorization as part of a GET Request 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. CVE summarizes:
On Netis WF2880 and WF2411 2.1.36123 devices, there is a stack-based buffer overflow that does not require authentication. This can cause denial of service (device restart) or remote code execution. This vulnerability can be triggered by a GET request with a long HTTP "Authorization: Basic" header that is mishandled by user_auth->user_ok in /bin/boa.
The bug was discovered 02/21/2019. The weakness was released 02/21/2019. This vulnerability is handled as CVE-2019-8985 since 02/21/2019. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. There are known technical details, but no exploit is available.
Addressing this vulnerability is possible by firewalling .
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Vendor
Name
Version
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: 7.1
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: 🔍
Status: Not defined
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: FirewallStatus: 🔍
0-Day Time: 🔍
Timeline
02/21/2019 🔍02/21/2019 🔍
02/21/2019 🔍
02/22/2019 🔍
07/19/2023 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2019-8985 (🔍)
GCVE (CVE): GCVE-0-2019-8985
GCVE (VulDB): GCVE-100-131096
Entry
Created: 02/22/2019 07:01Updated: 07/19/2023 08:28
Changes: 02/22/2019 07:01 (56), 05/12/2020 09:11 (1), 07/19/2023 08:28 (4)
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.