NCP Network Communications Secure Client 8.11 ncprwsnt.exe memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.0 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in NCP Network Communications Secure Client 8.11. This affects an unknown part of the file ncprwsnt.exe. Performing a manipulation results in memory corruption. This vulnerability is known as CVE-2006-0966. No exploit is available.
Details
A vulnerability, which was classified as problematic, was found in NCP Network Communications Secure Client 8.11. This affects some unknown processing of the file ncprwsnt.exe. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as 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. This is going to have an impact on availability. The summary by CVE is:
NCP Network Communication Secure Client 8.11 Build 146, and possibly other versions, allows local users cause a denial of service (CPU consumption) via a large number of arguments to ncprwsnt.exe, possibly due to a buffer overflow.
The weakness was published 03/02/2006 by Ramon 'ports' Kukla (Website). The advisory is shared at securityfocus.com. This vulnerability is uniquely identified as CVE-2006-0966 since 03/02/2006. The exploitability is told to be easy. An attack has to be approached locally. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available.
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 (25248), SecurityFocus (BID 16906†) and Secunia (SA19082†). Similar entries are available at VDB-28967, VDB-28966, VDB-28964 and VDB-28963. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.0VulDB Meta Temp Score: 4.0
VulDB Base Score: 4.0
VulDB Temp Score: 4.0
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: Partially
Local: Yes
Remote: No
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
03/01/2006 🔍03/02/2006 🔍
03/02/2006 🔍
03/02/2006 🔍
03/02/2006 🔍
03/12/2015 🔍
09/08/2017 🔍
Sources
Advisory: securityfocus.com⛔Researcher: Ramon 'ports' Kukla
Status: Not defined
CVE: CVE-2006-0966 (🔍)
GCVE (CVE): GCVE-0-2006-0966
GCVE (VulDB): GCVE-100-28965
X-Force: 25248 - NCP Network Communication Secure Client ncprwsnt.exe denial of service
SecurityFocus: 16906 - NCP Secure Client Multiple Vulnerabilities
Secunia: 19082 - NCP Secure Entry/Enterprise Client Two Vulnerabilities, Less Critical
See also: 🔍
Entry
Created: 03/12/2015 12:19Updated: 09/08/2017 09:14
Changes: 03/12/2015 12:19 (51), 09/08/2017 09:14 (8)
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.