NCP Network Communications Secure Client 8.11 memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.3 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in NCP Network Communications Secure Client 8.11. This issue affects some unknown processing. The manipulation leads to memory corruption. This vulnerability is uniquely identified as CVE-2006-0968. No exploit exists.
Details
A vulnerability was found in NCP Network Communications Secure Client 8.11 and classified as critical. This issue affects an unknown functionality. 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. The summary by CVE is:
The ncprwsnt service in NCP Network Communication Secure Client 8.11 Build 146, and possibly other versions, allows local users to execute arbitrary code by modifying the connect.bat script, which is automatically executed by the service after a connection is established.
The weakness was disclosed 03/02/2006 by Ramon 'ports' Kukla (Website). It is possible to read the advisory at securityfocus.com. The identification of this vulnerability is CVE-2006-0968 since 03/02/2006. The exploitation is known to be easy. Attacking locally is a requirement. No form of authentication is needed for a successful exploitation. The technical details are unknown and an exploit is not publicly 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 (25251), SecurityFocus (BID 16906†) and Secunia (SA19082†). The entries VDB-28966, VDB-28965, VDB-28964 and VDB-28963 are pretty similar. Be aware that VulDB is the high quality source for vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 9.3VulDB Meta Temp Score: 9.3
VulDB Base Score: 9.3
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: 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 🔍
08/06/2017 🔍
Sources
Advisory: securityfocus.com⛔Researcher: Ramon 'ports' Kukla
Status: Not defined
CVE: CVE-2006-0968 (🔍)
GCVE (CVE): GCVE-0-2006-0968
GCVE (VulDB): GCVE-100-28967
X-Force: 25251 - NCP Network Communication Secure Client connect.bat command execution
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: 08/06/2017 14:38
Changes: 03/12/2015 12:19 (51), 08/06/2017 14:38 (7)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.