CVE-2014-3619
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 · uneditedThe __socket_proto_state_machine function in GlusterFS 3.5 allows remote attackers to cause a denial of service (infinite loop) via a "00000000" fragment 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 __socket_proto_state_machine function in GlusterFS 3.5 lacks proper validation of the fragment header field. When a remote attacker sends a packet with a '00000000' fragment header, the state machine enters an infinite loop, causing CPU spinning and denial of service. The vulnerability exists in the network protocol handling code on the server side.
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= 3.5CVSS 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.
-
Check if GlusterFS is installedRun 'glusterfs --version' or 'gluster --version' to retrieve the installed versionAffected if The version shown is 3.5.x (before 3.5.3)
-
Verify the running GlusterFS processesRun 'ps aux | grep -E "glusterd|glusterfsd"' or 'systemctl status glusterd' to confirm GlusterFS daemon is runningAffected if GlusterFS processes are running and version is 3.5.x before 3.5.3
-
Check if GlusterFS network ports are exposedRun 'netstat -tlnp | grep -E "24007|24008"' or 'ss -tlnp | grep -E "24007|24008"' to see if the management and/orRDMA ports are listeningAffected if Ports 24007/tcp or 24008/tcp are listening and accessible from network, with vulnerable version running
-
Confirm server-side exposureCheck the glusterd configuration in /etc/glusterfs/glusterd.vol or review firewall rules to determine if remote clients can reach the serviceAffected if Remote network access to GlusterFS ports is permitted and the vulnerable version is active
You are affected if GlusterFS version 3.5.x (before 3.5.3) is running and its network ports (24007/tcp or 24008/tcp) are accessible to untrusted remote systems.
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 GlusterFS to version 3.5.3 or later which contains the fix. If immediate upgrade is not possible, restrict network access to GlusterFS ports (24007/tcp and 24008/tcp) to untrusted networks to reduce attack surface.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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 $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-3619 — 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-3619 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