CVE-2008-3435
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 · uneditedLinkedIn Browser Toolbar 3.0.3.1100 and earlier does not properly verify the authenticity of updates, which allows man-in-the-middle attackers to execute arbitrary code via a Trojan horse update, as demonstrated by evilgrade and DNS cache poisoning.
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 LinkedIn Browser Toolbar versions 3.0.3.1100 and earlier lack proper cryptographic verification of update authenticity. The toolbar downloads updates without validating the server's identity or the integrity of update files, allowing an attacker positioned on the network path (via MITM or DNS poisoning) to substitute malicious code that executes with the toolbar's privileges.
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<= 3.0.3.1100CVSS 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.
-
Verify if LinkedIn Browser Toolbar is installedOpen your browser's extension or add-on manager (for Internet Explorer: Tools > Manage Add-ons > Show: All Add-ons, look for 'LinkedIn Browser Toolbar' or 'Bing Bar' which included LinkedIn). For Firefox: Tools > Add-ons > Extensions. For Chrome: Settings > Extensions.Affected if The toolbar appears in the list of installed extensions or add-ons.
-
Determine the installed toolbar versionIn the browser's extension/add-on manager, locate the LinkedIn Browser Toolbar entry and click on it to view its Details or About information, which typically displays the version number (such as 3.0.3.1100).Affected if The version displayed is 3.0.3.1100 or lower.
-
Check if automatic updates are enabled for the toolbarIn the browser's extension manager, look for an 'Auto-update' or 'Update automatically' checkbox or setting associated with the LinkedIn Browser Toolbar entry.Affected if Automatic updates are turned on, making the vulnerable update mechanism actively reachable.
-
Verify the toolbar's update URL configurationInspect the toolbar's configuration files or registry entries (for IE toolbar: check HKEY_CURRENT_USER\Software\LinkedIn or HKEY_LOCAL_MACHINE\Software\LinkedIn in Windows Registry) for update server URLs.Affected if The update URL points to a non-HTTPS endpoint or does not include certificate validation parameters.
If the LinkedIn Browser Toolbar is installed and the version is 3.0.3.1100 or earlier with automatic updates enabled, the environment is affected by this vulnerability.
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 dataDiscontinue use of the LinkedIn Browser Toolbar as it is likely end-of-life; if continued use is required, disable automatic updates and manually obtain updates from verified sources only. Implement network-level protections such as DNSSEC and VPN usage to reduce DNS poisoning risk.
- Consultation2.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2008-3435 — 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-2008-3435 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