# CVE-2014-3619: Denial of service in n/a > Remote attackers can cause a denial of service in GlusterFS via a specific fragment header, leading to an infinite loop. - **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 27 Mar 2015 - **Updated:** 6 Aug 2024 - **Also known as:** DEBIAN-CVE-2014-3619, GHSA-7hxx-57vq-gp63, MGASA-2015-0145, RHBA-2015:0038, RHBA-2015:0040, UBUNTU-CVE-2014-3619 ## What is CVE-2014-3619? CVE-2014-3619 is a medium-severity denial of service vulnerability in Opensuse Opensuse, published on 27 Mar 2015. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description The __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. Weakness: CWE-399 ## Which versions are affected by CVE-2014-3619? It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `glusterfs` | Red Hat:rhel_common:7::el7 | All versions | 0:3.6.0.42-1.el7 | | `glusterfs-api` | Red Hat:rhel_common:7::el7 | All versions | 0:3.6.0.42-1.el7 | | `glusterfs-api-devel` | Red Hat:rhel_common:7::el7 | All versions | 0:3.6.0.42-1.el7 | | `glusterfs-debuginfo` | Red Hat:rhel_common:7::el7 | All versions | 0:3.6.0.42-1.el7 | | `glusterfs-devel` | Red Hat:rhel_common:7::el7 | All versions | 0:3.6.0.42-1.el7 | | `glusterfs-fuse` | Red Hat:rhel_common:7::el7 | All versions | 0:3.6.0.42-1.el7 | | `glusterfs-libs` | Red Hat:rhel_common:7::el7 | All versions | 0:3.6.0.42-1.el7 | | `glusterfs-rdma` | Red Hat:rhel_common:7::el7 | All versions | 0:3.6.0.42-1.el7 | | `glusterfs` | Red Hat:storage:2:client:el5 | All versions | 0:3.6.0.42-1.el5 | | `glusterfs-api` | Red Hat:storage:2:client:el5 | All versions | 0:3.6.0.42-1.el5 | | `glusterfs-api-devel` | Red Hat:storage:2:client:el5 | All versions | 0:3.6.0.42-1.el5 | | `glusterfs-debuginfo` | Red Hat:storage:2:client:el5 | All versions | 0:3.6.0.42-1.el5 | | `glusterfs-devel` | Red Hat:storage:2:client:el5 | All versions | 0:3.6.0.42-1.el5 | | `glusterfs-fuse` | Red Hat:storage:2:client:el5 | All versions | 0:3.6.0.42-1.el5 | | `glusterfs-libs` | Red Hat:storage:2:client:el5 | All versions | 0:3.6.0.42-1.el5 | | `glusterfs-rdma` | Red Hat:storage:2:client:el5 | All versions | 0:3.6.0.42-1.el5 | | `glusterfs` | Red Hat:storage:3:client:el6 | All versions | 0:3.6.0.42-1.el6 | | `glusterfs-api` | Red Hat:storage:3:client:el6 | All versions | 0:3.6.0.42-1.el6 | | `glusterfs-api-devel` | Red Hat:storage:3:client:el6 | All versions | 0:3.6.0.42-1.el6 | | `glusterfs-debuginfo` | Red Hat:storage:3:client:el6 | All versions | 0:3.6.0.42-1.el6 | | `glusterfs-devel` | Red Hat:storage:3:client:el6 | All versions | 0:3.6.0.42-1.el6 | | `glusterfs-fuse` | Red Hat:storage:3:client:el6 | All versions | 0:3.6.0.42-1.el6 | | `glusterfs-libs` | Red Hat:storage:3:client:el6 | All versions | 0:3.6.0.42-1.el6 | | `glusterfs-rdma` | Red Hat:storage:3:client:el6 | All versions | 0:3.6.0.42-1.el6 | | `gluster-nagios-common` | Red Hat:storage:3:nagios:el6 | All versions | 0:0.1.4-1.el6rhs | | `gluster-nagios-addons` | Red Hat:storage:3:server:el6 | All versions | 0:0.1.14-1.el6rhs | | `gluster-nagios-addons-debuginfo` | Red Hat:storage:3:server:el6 | All versions | 0:0.1.14-1.el6rhs | | `gluster-nagios-common` | Red Hat:storage:3:server:el6 | All versions | 0:0.1.4-1.el6rhs | | `glusterfs` | Red Hat:storage:3:server:el6 | All versions | 0:3.6.0.42-1.el6rhs | | `glusterfs-api` | Red Hat:storage:3:server:el6 | All versions | 0:3.6.0.42-1.el6rhs | | `glusterfs-api-devel` | Red Hat:storage:3:server:el6 | All versions | 0:3.6.0.42-1.el6rhs | | `glusterfs-cli` | Red Hat:storage:3:server:el6 | All versions | 0:3.6.0.42-1.el6rhs | | `glusterfs-debuginfo` | Red Hat:storage:3:server:el6 | All versions | 0:3.6.0.42-1.el6rhs | | `glusterfs-devel` | Red Hat:storage:3:server:el6 | All versions | 0:3.6.0.42-1.el6rhs | | `glusterfs-fuse` | Red Hat:storage:3:server:el6 | All versions | 0:3.6.0.42-1.el6rhs | | `glusterfs-geo-replication` | Red Hat:storage:3:server:el6 | All versions | 0:3.6.0.42-1.el6rhs | | `glusterfs-libs` | Red Hat:storage:3:server:el6 | All versions | 0:3.6.0.42-1.el6rhs | | `glusterfs-rdma` | Red Hat:storage:3:server:el6 | All versions | 0:3.6.0.42-1.el6rhs | | `glusterfs-server` | Red Hat:storage:3:server:el6 | All versions | 0:3.6.0.42-1.el6rhs | | `gstatus` | Red Hat:storage:3:server:el6 | All versions | 0:0.62-1.el6rhs | Products: Gluster Glusterfs, Opensuse Opensuse. ## How do I fix CVE-2014-3619? Apply the vendor's patch. ## Is CVE-2014-3619 being exploited? There is no known exploitation of CVE-2014-3619 in the wild and no public exploit code. ## Other vulnerabilities in Opensuse Opensuse - [CVE-2018-1112](https://insights.sbomify.com/CVE-2018-1112/): Auth bypass in glusterfs (high 8.0) - [CVE-2022-48340](https://insights.sbomify.com/CVE-2022-48340/): Use after free in n/a (high 7.5) - [CVE-2023-26253](https://insights.sbomify.com/CVE-2023-26253/): Memory corruption in n/a (high 7.5) - [CVE-2018-10924](https://insights.sbomify.com/CVE-2018-10924/): Denial of service in glusterfs (medium 5.3) - [CVE-2012-4417](https://insights.sbomify.com/CVE-2012-4417/): Path traversal in n/a (low 3.6) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2014-3619 and fix it if it is affected. What it is: CVE-2014-3619 is a medium-severity denial of service vulnerability in Opensuse Opensuse, published on 27 Mar 2015. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2014-3619 in the wild and no public exploit code. Affected product: Opensuse Opensuse. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2014-3619/ (Markdown: https://insights.sbomify.com/CVE-2014-3619/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2014-3619 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2014-3619 - OSV: https://osv.dev/vulnerability/CVE-2014-3619 --- From sbomify Insights: https://insights.sbomify.com/CVE-2014-3619/ Summaries are generated and may contain mistakes; the official description above is the record.