Microsoft Windows 95/98/ME/NT 4.0 Chart widechartomultibyte memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Microsoft Windows 95/98/ME/NT 4.0 and classified as critical. This impacts the function widechartomultibyte of the component Chart. The manipulation leads to memory corruption.
This vulnerability is traded as CVE-2005-3172. There is no exploit available.
The affected component should be upgraded.
Details
A vulnerability was found in Microsoft Windows 95/98/ME/NT 4.0 (Operating System) and classified as critical. This issue affects the function widechartomultibyte of the component Chart. 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 availability. The summary by CVE is:
The WideCharToMultiByte function in Microsoft Windows 2000 before Update Rollup 1 for SP4 does not properly convert strings with Japanese composite characters in the last character, which could prevent the string from being null terminated and lead to data corruption or enable buffer overflow attacks.
The issue has been introduced in 08/24/1995. The weakness was shared 10/06/2005 (Website). It is possible to read the advisory at support.microsoft.com. The identification of this vulnerability is CVE-2005-3172 since 10/06/2005. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details of the vulnerability are known, but there is no available exploit.
The vulnerability was handled as a non-public zero-day exploit for at least 3696 days. During that time the estimated underground price was around $100k and more.
Upgrading to version 2000 eliminates this vulnerability.
The entries VDB-26523, VDB-26522, VDB-26521 and VDB-26520 are related to this item. Be aware that VulDB is the high quality source for vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.microsoft.com/
- Product: https://www.microsoft.com/en-us/windows
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
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: 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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Windows 2000
Timeline
08/24/1995 🔍10/06/2005 🔍
10/06/2005 🔍
10/06/2005 🔍
03/11/2015 🔍
04/14/2019 🔍
Sources
Vendor: microsoft.comProduct: microsoft.com
Advisory: support.microsoft.com
Status: Not defined
CVE: CVE-2005-3172 (🔍)
GCVE (CVE): GCVE-0-2005-3172
GCVE (VulDB): GCVE-100-26519
scip Labs: https://www.scip.ch/en/?labs.20140213
See also: 🔍
Entry
Created: 03/11/2015 23:39Updated: 04/14/2019 17:50
Changes: 03/11/2015 23:39 (52), 04/14/2019 17:50 (1)
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.