CVE-2005-0050 in the critical feed json
The License Logging service for Windows NT Server, Windows 2000 Server, and Windows Server 2003 does not properly validate the length of me…
published 2005-02-08 21 y ago modified 2026-06-16 4 mo ago also EUVD-2005-0051
- cvss
- 10.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 46.7%
- EPSS 46.7% chance of exploitation in 30 days, percentile 98%
- public exploits
- 0
- none known
Summary
The License Logging service for Windows NT Server, Windows 2000 Server, and Windows Server 2003 does not properly validate the length of messages, which leads to an "unchecked buffer" and allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code, aka the "License Logging Service Vulnerability."
Patch / fix
- us-cert.gov/cas/techalerts/TA05-039A.html advisory
- kb.cert.org/vuls/id/130433 advisory
Exploit prediction
46.69% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 10.0 | AV:N/AC:L/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
-
us-cert.gov
/cas/techalerts/TA05-039A.html
third-party-advisory, patch, us-government-resource
-
kb.cert.org
/vuls/id/130433
third-party-advisory, patch, us-government-resource
-
docs.microsoft.com
/en-us/security-updates/securitybulletins/2005/ms05-010
vendor-advisory
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A644
vdb-entry, signature
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A4786
vdb-entry, signature
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A2568
vdb-entry, signature
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A3582
vdb-entry, signature
-
exchange.xforce.ibmcloud.com
/vulnerabilities/19101
vdb-entry
Sources
- CVE List CVE-2005-0050
- NVD CVE-2005-0050
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.