CVE-2003-0823
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 · uneditedInternet Explorer 6 SP1 and earlier allows remote attackers to direct drag and drop behaviors and other mouse click actions to other windows by calling the window.moveBy method, aka HijackClick, a different vulnerability than CVE-2003-1027.
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 confidenceInternet Explorer 6 SP1 and earlier contains a clickjacking vulnerability (HijackClick) where attackers can manipulate the window.moveBy method to redirect drag-and-drop behaviors and mouse click actions to unauthorized windows, allowing execution of unintended operations on other browser windows.
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 data= 6.0= 5.0.1= 5.5= 6.0CVSS 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
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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.
-
Check if Internet Explorer is installedOpen Windows Settings > Apps > Apps & features, or check Program Files folder for Internet Explorer executable (iexplore.exe). On Windows XP/2000, check Start Menu for Internet Explorer shortcut.Affected if Internet Explorer is present on the system
-
Identify the Internet Explorer versionOpen Internet Explorer, click Help > About Internet Explorer, or run 'iexplore.exe -version' from command prompt to display the version number.Affected if The displayed version is 5.0.1, 5.5, or 6.0
-
Check Windows system information for IE versionOpen Control Panel > Add or Remove Programs, look for 'Windows Internet Explorer' in the installed updates or program list and note the version shown.Affected if The listed version matches 5.0.1, 5.5, or 6.0
-
Verify Service Pack level for IE 6If Internet Explorer 6 is found, check the Help > About dialog or system properties to determine if Service Pack 1 is installed (vulnerable) or if it is a later patched version.Affected if Internet Explorer 6 Service Pack 1 or earlier is installed
A system is affected if any version of Internet Explorer 5.0.1, 5.5, or 6.0 is installed and in regular use, as these versions contain the vulnerable window.moveBy behavior that allows clickjacking attacks.
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 dataMigrate from Internet Explorer 6 to a supported modern browser (Internet Explorer 11, Microsoft Edge, or Chrome/Firefox) and remove or disable legacy IE installations across the environment.
- Consultation8.0 h
- Implementation24.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2003-0823 — 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-2003-0823 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