ChromeWeb browser · Google
CVE-2011-3964
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 · uneditedGoogle Chrome before 17.0.963.46 does not properly implement the drag-and-drop feature, which makes it easier for remote attackers to spoof the URL bar via unspecified vectors.
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 · moderate confidenceGoogle Chrome before 17.0.963.46 has a vulnerability in its drag-and-drop feature implementation that allows remote attackers to spoof the URL bar, making users believe they are on a different website than they actually are. This is a UI spoofing/phishing vulnerability that exploits how the browser handles drag-and-drop operations.
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
ChromeWeb browser
< 17.0.963.46CVSS 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
- Partial
- Integrity
- Partial
- Availability
- None
AV:N/AC:M/Au:N/C:P/I:P/A:N
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.
-
Verify Google Chrome is installedCheck for the Google Chrome executable. On Windows, look for chrome.exe in typical installation paths (e.g., C:\Program Files\Google\Chrome\Application\ or C:\Users\<user>\AppData\Local\Google\Chrome\Application\). On macOS, check /Applications/Google Chrome.app. On Linux, check /opt/google/chrome/ or /usr/bin/google-chrome.Affected if Google Chrome browser is present on the system
-
Determine the installed Google Chrome versionOpen Google Chrome and navigate to chrome://version in the address bar. The version number is displayed at the top of the page under 'Google Chrome' (e.g., 17.0.963.45). Alternatively, on Windows command prompt run: "C:\Program Files\Google\Chrome\Application\chrome.exe" --versionAffected if Unable to retrieve a version number indicates Chrome may not be properly installed
-
Compare installed version to the affected rangeTake the version number from chrome://version (e.g., 17.0.963.45) and compare it numerically to 17.0.963.46. The version is organized as major.minor.build.patch. If major < 17, or major = 17 and minor < 0, or major = 17 and minor = 0 and build < 963, or major = 17, minor = 0, build = 963 and patch < 46, then the version is affected.Affected if Installed version is less than 17.0.963.46 (e.g., 17.0.963.45, 17.0.963.40, 16.x.x.x, etc.)
-
Understand the attack vectorThe vulnerability exploits the drag-and-drop feature. When a malicious website tricks a user into dragging an element (such as a link) onto the browser's address bar, the browser may display a spoofed URL in the address bar while the actual navigation occurs to a different site. This is a built-in browser feature that cannot be disabled through user settings.Affected if User engages with drag-and-drop operations from untrusted websites while using a vulnerable Chrome version
A user is affected if Google Chrome version is installed and that version is less than 17.0.963.46, combined with the user potentially interacting with drag-and-drop actions from web content.
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 data17.0.963.46
Upgrade Google Chrome to version 17.0.963.46 or later to obtain the patched drag-and-drop implementation that properly validates URL bar updates.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-3964 — 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-2011-3964 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