| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.1 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in ZyXEL ZyNOS Vt020225a. This issue affects some unknown processing of the component ARP Request Handler. This manipulation causes information disclosure. This vulnerability appears as CVE-2004-1684. In addition, an exploit is available.
Details
A vulnerability classified as problematic was found in ZyXEL ZyNOS Vt020225a. Affected by this vulnerability is some unknown functionality of the component ARP Request Handler. The manipulation with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality. The summary by CVE is:
Zyxel P681 running ZyNOS Vt020225a contains portions of memory in an ARP request, which allows remote attackers to obtain sensitive information by sniffing the network.
The weakness was presented 09/13/2004 by Przemyslaw Frasunek (Website). The advisory is shared at marc.theaimsgroup.com. This vulnerability is known as CVE-2004-1684 since 02/21/2005. The exploitation appears to be easy. The attack can only be initiated within the local network. The exploitation doesn't need any form of authentication. Technical details are unknown but an exploit is available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
After immediately, there has been an exploit disclosed. 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 databases at X-Force (17372), SecurityFocus (BID 11167†) and OSVDB (9962†). See VDB-27 and VDB-68772 for similar entries. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
License
Website
- Vendor: https://www.zyxel.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.1
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Proof-of-Concept
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: 🔍
Exploit Delay Time: 🔍
Timeline
09/13/2004 🔍09/13/2004 🔍
09/13/2004 🔍
09/13/2004 🔍
09/14/2004 🔍
02/21/2005 🔍
04/14/2015 🔍
06/21/2018 🔍
Sources
Vendor: zyxel.comAdvisory: marc.theaimsgroup.com
Researcher: Przemyslaw Frasunek
Status: Not defined
CVE: CVE-2004-1684 (🔍)
GCVE (CVE): GCVE-0-2004-1684
GCVE (VulDB): GCVE-100-22213
X-Force: 17372 - ZyXEL Prestige 681 SDSL information disclosure
SecurityFocus: 11167 - ZyXEL P681 ARP Request Information Disclosure Vulnerability
OSVDB: 9962 - ZyXEL Prestige 681 ARP Request Packet Information Disclosure
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 04/14/2015 13:19Updated: 06/21/2018 09:08
Changes: 04/14/2015 13:19 (55), 06/21/2018 09:08 (5)
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.