CVE-2014-2977
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 integer signedness errors in the Dispatch_Write function in proxy/dispatcher/idirectfbsurface_dispatcher.c in DirectFB 1.4.13 allow remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via the Voodoo interface, which triggers a stack-based buffer overflow.
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 confidenceDirectFB 1.4.13 contains integer signedness errors in the Dispatch_Write function within the Voodoo interface dispatcher. These errors allow incorrect size calculations when processing remote requests, which triggers a stack-based buffer overflow. Remote attackers can exploit this via the Voodoo protocol to crash the application or potentially execute arbitrary code.
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= 13.1= 13.2= 12= 12= 12= 12= 1.4.13CVSS 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
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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 DirectFB is installedOn SUSE/openSUSE systems, run: rpm -qa | grep -i directfb or dpkg -l | grep -i directfb on Debian-based systems. Alternatively, check for the library file: find /usr -name 'libdirectfb*' 2>/dev/nullAffected if DirectFB package or library files are found on the system
-
Identify the installed DirectFB versionRun: rpm -q --queryformat '%{VERSION}' directfb or check the library version with: ls -la /usr/lib*/libdirectfb*.so*Affected if The version returned is 1.4.13 exactly
-
Check if DirectFB version falls within affected SUSE/openSUSE releasesRun: cat /etc/os-release to identify the distribution version. Then check if the installed DirectFB package version matches the vulnerable version listed for openSUSE 13.1, 13.2, or SUSE Linux Enterprise 12Affected if The system runs openSUSE 13.1, 13.2, or SUSE Linux Enterprise 12 and has DirectFB installed
-
Verify if the Voodoo interface is enabledCheck DirectFB configuration files: ls /etc/directfbrc /etc/directfbrc ~/.directfbrc 2>/dev/null and inspect for any 'voodoo' or 'Voodoo' keywords. Also check for Voodoo-related configuration under /etc/directfb/Affected if Voodoo interface or Voodoo protocol is explicitly enabled in DirectFB configuration files
The system is affected if DirectFB version 1.4.13 is installed and the Voodoo interface is enabled or accessible, allowing remote Voodoo protocol requests to trigger the signedness error and buffer overflow.
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 to a patched version of DirectFB that addresses the signedness errors in proxy/dispatcher/idirectfbsurface_dispatcher.c. If upgrading is not feasible, disable or restrict access to the Voodoo interface to limit attack surface.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-2977 — 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-2977 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