| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.3 | $5k-$25k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in NetBSD 3.0/3.1/4.0. This affects an unknown function. The manipulation leads to input validation. This vulnerability is uniquely identified as CVE-2008-3584. No exploit exists.
Details
A vulnerability was found in NetBSD 3.0/3.1/4.0 (Operating System) and classified as critical. This issue affects some unknown functionality. The manipulation with an unknown input leads to a input validation vulnerability. Using CWE to declare the problem leads to CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
NetBSD 3.0, 3.1, and 4.0, when a pppoe instance exists, does not properly check the length of a PPPoE packet tag, which allows remote attackers to cause a denial of service (system crash) via a crafted PPPoE packet.
The weakness was disclosed 09/11/2008 (Website). The advisory is shared at ftp.netbsd.org. The identification of this vulnerability is CVE-2008-3584 since 08/11/2008. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 08/02/2021).
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 (44679), SecurityFocus (BID 30838†), Secunia (SA31597†), SecurityTracker (ID 1020749†) and Vulnerability Center (SBV-22897†). The entries VDB-44311 and VDB-43942 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 9.8VulDB Meta Temp Score: 9.3
VulDB Base Score: 9.8
VulDB Temp Score: 9.3
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: Input validationCWE: CWE-20
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: 🔍
Timeline
08/11/2008 🔍08/26/2008 🔍
08/26/2008 🔍
08/26/2008 🔍
09/11/2008 🔍
09/11/2008 🔍
09/11/2008 🔍
07/15/2009 🔍
03/17/2015 🔍
08/02/2021 🔍
Sources
Advisory: ftp.netbsd.orgStatus: Confirmed
Confirmation: 🔍
CVE: CVE-2008-3584 (🔍)
GCVE (CVE): GCVE-0-2008-3584
GCVE (VulDB): GCVE-100-43997
X-Force: 44679
SecurityFocus: 30838
Secunia: 31597 - NetBSD PPPoE Packet Processing Tag Length Vulnerability, Less Critical
SecurityTracker: 1020749 - NetBSD PPPoE Discovery Packet Processing Bug Lets Remote Users Deny Service
Vulnerability Center: 22897 - NetBSD 3.0, 3.1 and 4.0 Remote DoS Vulnerability via a Crafted PPPoE Packet, High
Vupen: ADV-2009-0633
See also: 🔍
Entry
Created: 03/17/2015 16:11Updated: 08/02/2021 08:46
Changes: 03/17/2015 16:11 (48), 02/11/2017 16:44 (16), 08/02/2021 08:46 (4)
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.