Breaking News: Hijacked Releases of Microsoft’s Official agent-framework Steals Azure and CI Credentials
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2016-0737

openstack-swift: Client to proxy DoS through Large Objects

Overview

Published
29 Jan 2016
Modified
6 May 2026
High CVE
1 Registry packages
10 OS packages
3 Linux distributions
Yes Fix available

Description

OpenStack Object Storage (Swift) before 2.4.0 does not properly close client connections, which allows remote attackers to cause a denial of service (proxy-server resource consumption) via a series of interrupted requests to a Large Object URL.

Source: OX vulnerability database

Severity

7.5 · HIGH

CVSS 3.0 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Weakness: CWE-399

Affected packages · 1

Packages affected by CVE-2016-0737
EcosystemPackageVulnerableFixed in
PyPI swift <2.4.0 2.4.0

Open a package to see all its vulnerabilities.

Operating systems · 11 fixes

Red Hat 4 releases · 2 packages

fixed 3 eol 3
openstack-swift openstack-swift-account
Red Hat fixes for CVE-2016-0737
ReleasePackageFixed inAdvisory
openstack-swift +5 0:1.13.1-8.el6ost RHSA-2016:0329
openstack-swift +5 0:1.13.1-8.el7ost RHSA-2016:0328
7 openstack-swift-account +5 eol —
7 openstack-swift +5 0:2.3.0-3.el7ost RHSA-2016:0155
8 openstack-swift +5 eol —
9 openstack-swift +5 eol —

debian 4 releases · 1 package

fixed 4
swift
debian fixes for CVE-2016-0737
ReleasePackageFixed in
11 swift 2.4.0-1
12 swift 2.4.0-1
13 swift 2.4.0-1
14 swift 2.4.0-1

echo 1 release · 1 package

fixed 1
swift
echo fixes for CVE-2016-0737
ReleasePackageFixed in
swift 2.4.0-1

References

Show all 24 references

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.