Microsoft Office on Mac PID Checker Product Announcement denial of service
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic was found in Microsoft Office on Mac. The impacted element is an unknown function of the component PID Checker. Such manipulation as part of Product Announcement leads to denial of service. This vulnerability is listed as CVE-2002-0021. There is no available exploit. It is advisable to implement a patch to correct this issue.
Details
A vulnerability, which was classified as problematic, has been found in Microsoft Office on Mac (Office Suite Software) (version unknown). Affected by this issue is an unknown function of the component PID Checker. The manipulation as part of a Product Announcement leads to a denial of service vulnerability. Using CWE to declare the problem leads to CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. Impacted is availability. CVE summarizes:
Network Product Identification (PID) Checker in Microsoft Office v. X for Mac allows remote attackers to cause a denial of service (crash) via a malformed product announcement.
The weakness was presented 02/06/2002 by Marty Schoch as MS02-002 as confirmed bulletin (Technet). The advisory is shared for download at microsoft.com. This vulnerability is handled as CVE-2002-0021. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. There are neither technical details nor an exploit publicly available.
Applying the patch MS02-002 is able to eliminate this problem. The bugfix is ready for download at microsoft.com.
The vulnerability is also documented in the databases at X-Force (8087), SecurityFocus (BID 4045†), OSVDB (2041†) and Vulnerability Center (SBV-3993†). Once again VulDB remains the best source for vulnerability data.
Product
Type
Vendor
Name
License
Website
- Vendor: https://www.microsoft.com/
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: Denial of serviceCWE: CWE-404
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: PatchStatus: 🔍
0-Day Time: 🔍
Patch: MS02-002
Timeline
02/06/2002 🔍02/06/2002 🔍
02/06/2002 🔍
03/08/2002 🔍
02/21/2003 🔍
03/17/2004 🔍
07/11/2014 🔍
05/20/2019 🔍
Sources
Vendor: microsoft.comAdvisory: MS02-002
Researcher: Marty Schoch
Status: Confirmed
CVE: CVE-2002-0021 (🔍)
GCVE (CVE): GCVE-0-2002-0021
GCVE (VulDB): GCVE-100-17948
X-Force: 8087
SecurityFocus: 4045 - Microsoft Office v. X for Macintosh Network PID Checker Denial of Service Vulnerability
OSVDB: 2041 - Microsoft Office for Macintosh Network PID Checker DoS
Vulnerability Center: 3993 - [MS02-002] DoS in Microsoft Office v.X Network Product Identification (PID) via Malformed Announceme, Medium
Entry
Created: 07/11/2014 13:39Updated: 05/20/2019 15:29
Changes: 07/11/2014 13:39 (65), 05/20/2019 15:29 (2)
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.