Skip to content
Fencer Intel
high 7.4

CVE-2015-8466 json

Swift3 before 1.9 allows remote attackers to conduct replay attacks via an Authorization request that lacks a Date header.

published 2016-01-13 10 y ago modified 2026-06-17 4 mo ago also EUVD-2015-8348

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

Summary

Swift3 before 1.9 allows remote attackers to conduct replay attacks via an Authorization request that lacks a Date header.

Patch / fix

  • swift-plugin-s3 Ubuntu Pro 14.04 LTS 1.7-5+deb8u1build0.14.04.1~esm1

ubuntu advisories UBUNTU-CVE-2015-8466

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

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-2015-8466 updated cvss 4.3

openstack-swift-plugin3: replay attack - date/date header unvalidated

  • Red Hat Enterprise Linux OpenStack Platform 5 (Icehouse) openstack-swift-plugin-swift3 Red Hat Enterprise Linux OpenStack Platform 6 (Juno) openstack-swift-plugin-swift3 Red Hat Enterprise Linux OpenStack Platform 7 (Kilo) openstack-swift-plugin-swift3
    affected: no fix planned “Will not fix”
  • Red Hat OpenStack Platform 8 (Liberty) openstack-swift-plugin-swift3
    affected: no fix available
  • Red Hat Storage 3 openstack-swift-plugin-swift3
    not affected: vulnerable code not present

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

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

CVSS scores

assigned by version score vector
NVD 3.0 7.4 CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
NVD 2.0 5.8 AV:N/AC:M/Au:N/C:P/I:P/A:N

Classification

Weakness
  • CWE-20 Improper Input Validation

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.