ZyXEL NBG-418N v2 V1.00(AARP.9)C0 Authentication wan.htm Firmware improper authentication
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
7.3 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic was found in ZyXEL NBG-418N v2 V1.00(AARP.9)C0. This vulnerability affects unknown code of the file wan.htm of the component Authentication. The manipulation as part of Firmware leads to improper authentication. This vulnerability was named CVE-2019-17354. The attack can be initiated remotely. There is no exploit available. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Details
A vulnerability classified as problematic has been found in ZyXEL NBG-418N v2 V1.00(AARP.9)C0 (Router Operating System). This affects an unknown code block of the file wan.htm of the component Authentication. The manipulation as part of a Firmware leads to a improper authentication vulnerability. CWE is classifying the issue as CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. This is going to have an impact on confidentiality. The summary by CVE is:
wan.htm page on Zyxel NBG-418N v2 with firmware version V1.00(AARP.9)C0 can be accessed directly without authentication, which can lead to disclosure of information about the WAN, and can also be leveraged by an attacker to modify data fields of the page.
The weakness was presented 10/09/2019. This vulnerability is uniquely identified as CVE-2019-17354 since 10/08/2019. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available.
By approaching the search of inurl:wan.htm it is possible to find vulnerable targets with Google Hacking.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.4
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: Improper authenticationCWE: CWE-287
CAPEC: 🔍
ATT&CK: 🔍
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
Google Hack: 🔍
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
10/08/2019 🔍10/09/2019 🔍
10/10/2019 🔍
01/07/2024 🔍
Sources
Vendor: zyxel.comAdvisory: github.com
Status: Not defined
CVE: CVE-2019-17354 (🔍)
GCVE (CVE): GCVE-0-2019-17354
GCVE (VulDB): GCVE-100-143253
Entry
Created: 10/10/2019 10:31 AMUpdated: 01/07/2024 09:21 AM
Changes: 10/10/2019 10:31 AM (37), 09/29/2020 04:47 PM (18), 01/07/2024 09:21 AM (3)
Complete: 🔍
Cache ID: 18:41E:40
No comments yet. Languages: en.
Please log in to comment.