Microsoft Windows Media Rights Manager 4.0/4.1 denial of service
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in Microsoft Windows Media Rights Manager 4.0/4.1. This affects an unknown function. This manipulation causes denial of service. This vulnerability is tracked as CVE-2000-0228. No exploit exists. Applying a patch is the recommended action to fix this issue.
Details
A vulnerability was found in Microsoft Windows Media Rights Manager 4.0/4.1 (Operating System). It has been declared as problematic. Affected by this vulnerability is an unknown code. The manipulation with an unknown input leads to a denial of service vulnerability. The CWE definition for the vulnerability is CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. As an impact it is known to affect availability. The summary by CVE is:
Microsoft Windows Media License Manager allows remote attackers to cause a denial of service by sending a malformed request that causes the manager to halt, aka the "Malformed Media License Request" Vulnerability.
The weakness was disclosed 03/17/2000 by arma with Microsoft as MS00-016 as confirmed bulletin (Technet). The advisory is shared at microsoft.com. This vulnerability is known as CVE-2000-0228. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available.
Applying the patch MS00-016 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 (4108), SecurityFocus (BID 1058†) and Vulnerability Center (SBV-4090†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
Support
- end of life (old version)
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: MS00-016
Timeline
03/17/2000 🔍03/17/2000 🔍
03/17/2000 🔍
03/17/2000 🔍
03/31/2004 🔍
06/23/2014 🔍
04/21/2026 🔍
Sources
Vendor: microsoft.comAdvisory: MS00-016
Researcher: Discovered by Ranjiv Sharma, publicized in Microsoft Security Bulletin (MS00-016) released on March 17, 2000. (arma)
Organization: Microsoft
Status: Confirmed
CVE: CVE-2000-0228 (🔍)
GCVE (CVE): GCVE-0-2000-0228
GCVE (VulDB): GCVE-100-15397
X-Force: 4108
SecurityFocus: 1058 - Microsoft Windows Media License Manager DoS Vulnerability
Vulnerability Center: 4090 - [MS00-016] DoS in Microsoft Windows Media License Manager via Malformed License Requests, Medium
Entry
Created: 06/24/2014 00:38Updated: 04/21/2026 01:13
Changes: 06/24/2014 00:38 (43), 05/20/2019 18:06 (20), 10/08/2020 14:55 (1), 04/21/2026 01:13 (16)
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.