CVE-2012-2647
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 · uneditedYahoo! Toolbar 1.0.0.5 and earlier for Chrome and Safari allows remote attackers to modify the configured search URL, and intercept search terms, via a crafted web page.
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 confidenceYahoo! Toolbar versions 1.0.0.5 and earlier for Chrome and Safari contains a vulnerability that allows malicious webpages to manipulate the toolbar's configured search URL and intercept search terms. This indicates a lack of proper origin validation or insecure message handling between web pages and the browser extension.
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<= 1.0.0.5CVSS 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.
-
Check if Yahoo! Toolbar is installed in ChromeOpen Chrome and navigate to chrome://extensions. Look for 'Yahoo! Toolbar' in the list of installed extensions.Affected if Yahoo! Toolbar appears in the extensions list
-
Check if Yahoo! Toolbar is installed in SafariOpen Safari, go to Safari > Preferences > Extensions tab. Look for 'Yahoo! Toolbar' in the enabled extensions list.Affected if Yahoo! Toolbar appears in the Safari extensions list
-
Determine the Yahoo! Toolbar version in ChromeIn chrome://extensions, enable 'Developer mode' checkbox if present, then locate Yahoo! Toolbar and note the version number displayed.Affected if Version listed is 1.0.0.5 or earlier
-
Determine the Yahoo! Toolbar version in SafariIn Safari > Preferences > Extensions, select Yahoo! Toolbar from the list. The version information is typically displayed in the extension details pane on the right side.Affected if Version listed is 1.0.0.5 or earlier
If Yahoo! Toolbar is installed and its version is 1.0.0.5 or earlier in either Chrome or Safari, the environment is affected by CVE-2012-2647.
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 dataUpdate Yahoo! Toolbar to a patched version if available. If no update exists (likely given the 2012 disclosure), remove the toolbar to eliminate the attack surface. Consider using browser built-in search or trusted search extensions as alternatives.
- Consultation1.0 h
- Implementation2.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-2647 — 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-2012-2647 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