Skip to content
Fencer Intel
medium 4.0

CVE-2014-7960 json

OpenStack Swift metadata constraints are not correctly enforced

published 2014-10-17 12 y ago modified 2026-07-07 4 mo ago also GHSA-g6x3-55qv-x6p2 , PYSEC-2026-933 , EUVD-2022-3908

cvss
4.0
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
3.1%
EPSS 3.1% chance of exploitation in 30 days, percentile 87%
public exploits
0
none known

Summary

OpenStack Object Storage (Swift) before 2.2.0 allows remote authenticated users to bypass the max_meta_count and other metadata constraints via multiple crafted requests which exceed the limit when combined.

Patch / fix

  • pypi swift 2.2.0
  • swift Debian 14, Debian 13, Debian 12 2.2.0-1

debian advisories DEBIAN-CVE-2014-7960

  • swift Ubuntu 14.04 LTS 1.13.1-0ubuntu1.2

ubuntu advisories UBUNTU-CVE-2014-7960

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • ccs storage 3.1 0.16.2-81.el6
  • pcs storage 3.1 0.9.139-9.el6
  • cman storage 3.1 3.0.12.1-73.el6
  • nrpe storage 3.1 2.15-4.1.el6rhs
  • vdsm storage 3.1 4.16.20-1.2.el6rhs
  • libqb storage 3.1 0.17.1-1.el6
  • pynag storage 3.1 0.9.1-1.el6rhs
  • ricci storage 3.1 0.16.2-81.el6

red hat advisories RHSA-2015:1495RHSA-2015:0835RHSA-2015:0836

  • openstack-swift OpenStack Cloud 5 2.1.0-11.1

suse advisories SUSE-SU-2015:1846-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2014-7960 updated cvss 4.0

openstack-swift: Swift metadata constraints are not correctly enforced

  • Red Hat OpenStack Platform 4 openstack-swift
    affected: no fix planned “Will not fix”
  • Red Hat Enterprise Linux OpenStack Platform 5.0 (Icehouse) for RHEL 6 openstack-swift 1.13.1-4.el6ost, openstack-swift-proxy 1.13.1-4.el6ost, openstack-swift-object 1.13.1-4.el6ost, openstack-swift-account 1.13.1-4.el6ost, openstack-swift-container 1.13.1-4.el6ost
    fixed: vendor fix RHSA-2015:0836
  • Red Hat Enterprise Linux OpenStack Platform 5.0 (Icehouse) for RHEL 7 openstack-swift 1.13.1-4.el7ost, openstack-swift-proxy 1.13.1-4.el7ost, openstack-swift-object 1.13.1-4.el7ost, openstack-swift-account 1.13.1-4.el7ost, openstack-swift-container 1.13.1-4.el7ost
    fixed: vendor fix RHSA-2015:0835
  • Red Hat Gluster 3 Samba on RHEL-6 pytalloc 2.1.1-4.el6rhs, libtalloc 2.1.1-4.el6rhs Red Hat Gluster Storage Nagios 3.1 on RHEL-6 nrpe 2.15-4.1.el6rhs, pynag 0.9.1-1.el6rhs, check-mk 1.2.6p1-3.el6rhs, python-cpopen 1.3-4.el6_5, pnp4nagios 0.6.22-2.1.el6rhs, pynag-examples 0.9.1-1.el6rhs, +7 more Red Hat Gluster Storage NFS 3.1 on RHEL-6 nfs-ganesha 2.2.0-5.el6rhs, nfs-ganesha-nullfs 2.2.0-5.el6rhs, nfs-ganesha-gluster 2.2.0-5.el6rhs Red Hat Gluster Storage Server 3.1 on RHEL-6 ccs 0.16.2-81.el6, pcs 0.9.139-9.el6, libqb 0.17.1-1.el6, augeas 1.0.0-10.el6, openais 1.1.1-7.el6, ricci 0.16.2-81.el6, +82 more Red Hat Storage Native Client for Red Hat Enterprise Linux 5 glusterfs 3.7.1-11.el5, glusterfs-api 3.7.1-11.el5, glusterfs-cli 3.7.1-11.el5, glusterfs-fuse 3.7.1-11.el5, glusterfs-libs 3.7.1-11.el5, glusterfs-rdma 3.7.1-11.el5, +2 more Red Hat Storage Native Client for Red Hat Enterprise Linux 6 glusterfs 3.7.1-11.el6, glusterfs-api 3.7.1-11.el6, glusterfs-cli 3.7.1-11.el6, glusterfs-fuse 3.7.1-11.el6, glusterfs-libs 3.7.1-11.el6, glusterfs-rdma 3.7.1-11.el6, +2 more
    fixed: vendor fix RHSA-2015:1495

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

3.13% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 4.0 AV:N/AC:L/Au:S/C:N/I:P/A:N

Affected packages

ecosystem package affected fixed in
pypi swift
<2.2.0
2.2.0

Classification

Weakness
  • CWE-399 Resource Management Errors

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.