CVE-2005-3650
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe CodeSupport.ocx ActiveX control, as used by Sony to uninstall the First4Internet XCP DRM, has "safe for scripting" enabled, which allows remote attackers to execute arbitrary code by calling vulnerable functions such as RebootMachine, IsAdministrator, and ExecuteCode.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe CodeSupport.ocx ActiveX control, distributed with Sony's XCP DRM uninstaller, has 'safe for scripting' enabled, which incorrectly allows any web page to invoke its methods without user consent. Attackers can call functions like ExecuteCode, RebootMachine, and IsAdministrator to execute arbitrary code on affected systems.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/Au:N/C:C/I:C/A:C
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate the CodeSupport.ocx fileSearch for CodeSupport.ocx in Windows system directories (C:\Windows\System32\, C:\Windows\SysWOW64\) and any Sony-related program folders. Use: dir /s C:\CodeSupport.ocx or Get-ChildItem -Path C:\ -Filter CodeSupport.ocx -Recurse -ErrorAction SilentlyContinueAffected if The file exists on the system
-
Verify the ActiveX control is registeredCheck Windows registry under HKEY_CLASSES_ROOT\CLSID for the component's CLSID. Look for keys containing 'CodeSupport' or search registry for the ocx file registration using reg query commandsAffected if The control is registered in the Windows registry as an ActiveX component
-
Confirm Sony XCP DRM software presenceCheck Program Files for Sony XCP DRM uninstaller folders, or check Add/Remove Programs for Sony DRM removal utilities. Also check for First4internet entries in installed programsAffected if The Sony XCP DRM uninstaller software remains installed on the system
-
Verify the Safe for Scripting flagExamine registry keys under the control's CLSID for values indicating 'Safe for Scripting' or 'SafeScript' (typically found in Implemented Categories or ScriptSafe flags). Use regedit or reg query on the registered CLSID pathAffected if The control is marked as safe for scripting in the registry
A system is affected if CodeSupport.ocx is present and registered as an ActiveX control with the safe-for-scripting flag enabled, typically from the legacy Sony XCP DRM uninstaller software.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataDisable or remove the CodeSupport.ocx ActiveX control from all affected systems. Since this component was part of Sony's 2005 DRM removal utility and is no longer needed, the recommended remediation is complete removal of the legacy Sony uninstall software.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2005-3650 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2005-3650 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data