CVE-2005-3981: n/a vulnerability

CVE-2005-3981: NOTE: this issue has been disputed by third parties.

NOTE: this issue has been disputed by third parties. Microsoft Windows XP, 2000, and 2003 allows local users to kill a writable process by using the CreateRemoteThread function with certain arguments on a process that has been opened using the OpenProcess function, possibly involving an invalid address for the start routine. NOTE: followup posts have disputed this issue, saying that if a user already has privileges to write to a process, then other functions could be called or the process could be terminated using PROCESS_TERMINATE

UnknownCVSS not scoredNot KEV-listedUpdatedAug 7, 2024, 23:31 UTC (UTC+00:00)

Security readout for executives and security teams

This is a disputed 2005 Windows local issue. It alleges a signed-in local user could crash a process they already have permission to open and write. Follow-up discussion argued this may not be a vulnerability because that level of access already permits termination. No severity score, patch, or active exploitation is provided. Exposure appears limited to legacy Windows XP, 2000, and 2003 systems where local users can obtain write access to target processes. Modern impact, affected configurations, and vendor remediation are not established in the supplied sources. Treat this as a legacy-platform hygiene issue, not a confirmed emergency. The main business risk is continued operation of unsupported Windows systems with weak local access controls, rather than a clearly proven remotely exploitable vulnerability. Mitigation focus: Check current Microsoft or vendor guidance for any historical advisory or superseding position.; Prioritize retiring or isolating Windows XP, 2000, and 2003 systems.; Restrict local interactive access to legacy Windows hosts..

Prepared: Jun 29, 2026, 16:18 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2005-3981 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup

Vulnerability profileCVE Program record

Severity: Unknown
CVSS: Not scored
Known Exploited: No
Published: Dec 4, 2005, 11:00 UTC (UTC+00:00)

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors

0Timeline events

0ADP providers

1Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

n/an/an/aListed

Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.