NCP Network Communications Secure Client 8.11 ncpmon.exe memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.9 | $0-$5k | 0.00 |
Summary
A vulnerability described as problematic has been identified in NCP Network Communications Secure Client 8.11. Affected by this issue is some unknown functionality of the file ncpmon.exe. Such manipulation leads to memory corruption. This vulnerability is traded as CVE-2006-0965. There is no exploit available.
Details
A vulnerability, which was classified as problematic, has been found in NCP Network Communications Secure Client 8.11. Affected by this issue is an unknown code block of the file ncpmon.exe. The manipulation with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability. CVE summarizes:
NCP Network Communication Secure Client 8.11 Build 146, and possibly other versions, allows local users to bypass security protections and configure privileged options via a long argument to ncpmon.exe, which provides access to alternate privileged menus, possibly due to a buffer overflow.
The weakness was shared 03/02/2006 by Ramon 'ports' Kukla (Website). The advisory is shared for download at securityfocus.com. This vulnerability is handled as CVE-2006-0965 since 03/02/2006. The exploitation is known to be easy. The attack needs to be approached locally. No form of authentication is required for exploitation. There are known technical details, 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 (25243), SecurityFocus (BID 16906†) and Secunia (SA19082†). The entries VDB-28967, VDB-28966, VDB-28965 and VDB-28963 are related to this item. Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.9VulDB Meta Temp Score: 5.9
VulDB Base Score: 5.9
VulDB Temp Score: 5.9
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/10/2017 🔍
Sources
Advisory: securityfocus.com⛔Researcher: Ramon 'ports' Kukla
Status: Not defined
CVE: CVE-2006-0965 (🔍)
GCVE (CVE): GCVE-0-2006-0965
GCVE (VulDB): GCVE-100-28964
X-Force: 25243 - NCP Network Communication Secure Client ncpmon.exe buffer overflow
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/10/2017 10:37
Changes: 03/12/2015 12:19 (52), 09/10/2017 10:37 (7)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.