CVE-2007-6535
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 · uneditedBuffer overflow in the YShortcut ActiveX control in YShortcut.dll 2006.8.15.1 in Yahoo! Toolbar might allow attackers to execute arbitrary code via a long string to the IsTaggedBM method.
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 confidenceBuffer overflow vulnerability in the YShortcut ActiveX control (YShortcut.dll version 2006.8.15.1) bundled with Yahoo! Toolbar. The IsTaggedBM method fails to properly validate input length, allowing attackers to overwrite stack memory and execute arbitrary code by supplying an overly long string parameter.
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
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/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.
-
Confirm Yahoo Toolbar installationCheck Programs and Features or search for Yahoo Toolbar folder in Program Files and Program Files (x86) directoriesAffected if Yahoo Toolbar is installed on the system
-
Locate YShortcut.dll fileSearch for YShortcut.dll in the Yahoo Toolbar installation directory, typically found in a subfolder like Yahoo!\Common or YHT\binAffected if YShortcut.dll file exists on the system
-
Check YShortcut.dll versionRight-click the YShortcut.dll file, select Properties, and view the File Version attributeAffected if File version is 2006.8.15.1
-
Verify ActiveX control registrationOpen Registry Editor and search for YShortcut or YShortcut.YShortcut under HKEY_CLASSES_ROOT to confirm the ActiveX control is registeredAffected if The YShortcut ActiveX control is registered in the Windows registry
If Yahoo Toolbar is present with YShortcut.dll version 2006.8.15.1 and the ActiveX control is registered, the environment is vulnerable to CVE-2007-6535
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 dataRemove or disable the Yahoo! Toolbar and its ActiveX components. If the software cannot be removed, configure browser killbits to disable the vulnerable YShortcut ActiveX control, or deploy compensating controls such as network segmentation and application whitelisting to limit exposure.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-6535 — 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-2007-6535 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