Nokia IP440 1.0 Voyager Web Administration Interface URL memory corruption

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.7 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Nokia IP440 1.0. Affected is an unknown function of the component Voyager Web Administration Interface. This manipulation as part of URL causes memory corruption. This vulnerability is handled as CVE-2001-0299. Additionally, an exploit exists. It is advisable to implement restrictive firewalling.
Details
A vulnerability classified as critical was found in Nokia IP440 1.0. Affected by this vulnerability is an unknown code of the component Voyager Web Administration Interface. The manipulation as part of a URL leads to a memory corruption vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
Buffer overflow in Voyager web administration server for Nokia IP440 allows local users to cause a denial of service, and possibly execute arbitrary commands, via a long URL.
The weakness was released 12/04/2000 by K2 (Website). The advisory is shared at marc.theaimsgroup.com. This vulnerability is known as CVE-2001-0299. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are unknown but an exploit is available.
After even before and not, there has been an exploit disclosed. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 7 days. During that time the estimated underground price was around $0-$5k.
Proper firewalling of is able to address this issue.
The vulnerability is also documented in the databases at X-Force (5640), SecurityFocus (BID 2054†) and OSVDB (6020†). 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.nokia.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 6.7
VulDB Base Score: 7.3
VulDB Temp Score: 6.7
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: Memory corruptionCWE: CWE-119
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: FirewallStatus: 🔍
0-Day Time: 🔍
Timeline
11/27/2000 🔍12/04/2000 🔍
12/04/2000 🔍
06/02/2001 🔍
04/09/2004 🔍
07/04/2014 🔍
05/30/2018 🔍
Sources
Vendor: nokia.comAdvisory: marc.theaimsgroup.com
Researcher: K2
Status: Not defined
CVE: CVE-2001-0299 (🔍)
GCVE (CVE): GCVE-0-2001-0299
GCVE (VulDB): GCVE-100-16741
X-Force: 5640 - Nokia IP440 integrated FireWall-1/IDS buffer overflow
SecurityFocus: 2054 - Nokia IP440 Remote Denial of Service Vulnerability
OSVDB: 6020 - Nokia Voyager Web Admin Server Long URL Overflow
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 07/04/2014 12:33Updated: 05/30/2018 11:23
Changes: 07/04/2014 12:33 (60), 05/30/2018 11:23 (1)
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.