CVE-2005-0875
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 · uneditedMultiple buffer overflows in the Yahoo plug-in for Trillian 2.0, 3.0, and 3.1 allow remote web servers to cause a denial of service (application crash) via a long string in an HTTP 1.1 response header.
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 Yahoo plugin in Trillian versions 2.0, 3.0, and 3.1 contains buffer overflows when parsing HTTP 1.1 response headers. When receiving a response from a remote web server, the plugin copies long header string values into fixed-size buffers without proper bounds checking, causing an application crash.
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= 2.0= 3.0= 3.1CVSS 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
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/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.
-
Identify Trillian installationLocate Trillian on the system by checking common installation directories or searching for the executable (typically in Program Files on Windows)Affected if Trillian version 2.0, 3.0, or 3.1 is installed
-
Confirm installed versionRight-click the Trillian executable, select Properties, and check the Version tab to determine the exact version numberAffected if The version shown is 2.0, 3.0, or 3.1 specifically
-
Check if Yahoo plugin is activeLaunch Trillian and go to the plugins or modules settings menu to see if the Yahoo plugin is enabledAffected if The Yahoo plugin is loaded and active in the client
-
Verify network connectivity capabilityAttempt to determine if Trillian can make outbound HTTP connections to remote web servers, which is required for the vulnerable code path to be triggeredAffected if Trillian has the ability to connect to remote web servers and the Yahoo plugin is in use
A user is affected if Trillian versions 2.0, 3.0, or 3.1 is installed with the Yahoo plugin enabled and the application can connect to remote web servers, as the buffer overflow occurs when parsing HTTP response headers.
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 dataSince this is a legacy client from 2005 that is likely no longer supported, the primary mitigation is to discontinue use of affected Trillian versions or ensure the client cannot connect to untrusted web servers. If the software must be used, network segmentation can limit exposure.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2005-0875 — 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-2005-0875 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