CVE-2014-3775
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 · uneditedlibgadu before 1.11.4 and 1.12.0 before 1.12.0-rc3, as used in Pidgin and other products, allows remote Gadu-Gadu file relay servers to cause a denial of service (memory overwrite) or possibly execute arbitrary code via a crafted message.
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 confidenceA memory corruption vulnerability in libgadu library allows remote Gadu-Gadu file relay servers to send crafted messages that overwrite memory, potentially enabling arbitrary code execution. The flaw exists in versions before 1.11.4 and 1.12.0-rc3.
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.11.4= 1.12.0CVSS 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.
-
Locate libgadu library filesSearch for libgadu shared library files on the system using commands like 'find /usr -name "libgadu*" -type f' or check package manager listingsAffected if No libgadu library files are found - the library is not installed and the system is not affected
-
Determine installed libgadu versionRun 'pkg-config --modversion libgadu' or check the library file version with 'ldd' if linked, or query the package manager (dpkg -l libgadu, rpm -q libgadu)Affected if Version is 1.11.4 or lower, OR version is exactly 1.12.0 (the 1.12.0 release, not rc3)
-
Identify applications using libgaduCheck for applications that link to libgadu such as Pidgin, Finch, or other instant messaging clients. Use 'ldd /path/to/binary | grep gadu' or check package dependenciesAffected if Applications using libgadu are present on the system
-
Verify Gadu-Gadu protocol is enabledIn client applications like Pidgin, check if the Gadu-Gadu protocol plugin is loaded or if any Gadu-Gaddy accounts are configured. Inspect client configuration files in ~/.purple/ or similarAffected if Gadu-Gaddy accounts exist or the protocol is actively configured for use
-
Check for incoming file relay connectionsMonitor network connections or inspect application logs for activity from Gadu-Gaddy file relay servers. Review any established connections to Gadu-Gaddy serversAffected if Connections to Gadu-Gaddy file relay servers are active or expected in the environment
A system is affected if it has libgadu version 1.11.4 or lower, or exactly version 1.12.0, AND uses an application with Gadu-Gaddy protocol enabled that can receive file relay connections from remote servers.
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 dataUpgrade libgadu to version 1.11.4 or later (stable branch) or 1.12.0-rc3 or later (development branch). Verify that all products using libgadu (including Pidgin) are rebuilt against the patched library.
- Consultation3.0 h
- Implementation6.0 h
- Testing8.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,472.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-3775 — 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-2014-3775 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