Skip to content
Noroxi
CVE-2014-3497· NVD / CVE Program· CNA redhat

Cross-site scripting (XSS) vulnerability in OpenStack Swift 1.11.0 through 1.13.1 allows remote attackers to inject arbitrary web script or

Cross-site scripting (XSS) vulnerability in OpenStack Swift 1.11.0 through 1.13.1 allows remote attackers to inject arbitrary web script or HTML via the WWW-Authenticate header.

MediumCVSS 4.3 · v2.0—No exploit Fix available
Published
Jul 3, 2014
Updated
Jun 16, 2026
EPSS
2.1% · 81th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

18

Monitor

Low priority for now.

CVSS
17 / 40 · 4.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 2.1%

Affected systems

VendorProduct
openstackswift

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • openstack swift1.11.0
  • openstack swift1.12.0
  • openstack swift1.13.0
  • openstack swift1.13.1

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12swiftbefore 1.13.1-11.13.1-1
PyPIswiftfrom 1.11.0 · before 2.0.02.0.0
Red Hat:openstack:5::el7openstack-swiftbefore 0:1.13.1-3.el7ost0:1.13.1-3.el7ost
Red Hat:openstack:5::el7openstack-swift-accountbefore 0:1.13.1-3.el7ost0:1.13.1-3.el7ost
Red Hat:openstack:5::el7openstack-swift-containerbefore 0:1.13.1-3.el7ost0:1.13.1-3.el7ost
Red Hat:openstack:5::el7openstack-swift-docbefore 0:1.13.1-3.el7ost0:1.13.1-3.el7ost
Red Hat:openstack:5::el7openstack-swift-objectbefore 0:1.13.1-3.el7ost0:1.13.1-3.el7ost
Red Hat:openstack:5::el7openstack-swift-proxybefore 0:1.13.1-3.el7ost0:1.13.1-3.el7ost
Red Hat:openstack:5::el7python-swiftclientbefore 0:2.1.0-2.el7ost0:2.1.0-2.el7ost
Red Hat:openstack:5::el7python-swiftclient-docbefore 0:2.1.0-2.el7ost0:2.1.0-2.el7ost

Other highest-scoring records for the same primary product.

  • CVE-2012-4406OpenStack Object Storage (swift) before 1.7.0 uses the loads function in the pickle Python module unsafely when storing and loading metadata
    41Plan
  • CVE-2026-71190In OpenStack Swift through 2.38.0, the proxy server Accept header parser contains a regular expression vulnerable to catastrophic backtracki
    34Monitor
  • CVE-2016-0738OpenStack Object Storage (Swift) before 2.3.1 (Kilo), 2.4.x, and 2.5.x before 2.5.1 (Liberty) do not properly close server connections, whic
    31Monitor
  • CVE-2016-0737OpenStack Object Storage (Swift) before 2.4.0 does not properly close client connections, which allows remote attackers to cause a denial of
    31Monitor
  • CVE-2026-49017In OpenStack Swift before 2.36.2 and 2.37.2, s3api middleware enters an infinite loop when processing a truncated aws-chunked PUT request bo
    28Monitor
  • CVE-2022-47950An issue was discovered in OpenStack Swift before 2.28.1, 2.29.x before 2.29.2, and 2.30.0.
    26Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:swift1.13.1-1 · Debian:12Package registry (OSV)
PyPI:swift2.0.0Package registry (OSV)
red hat:openstack-swift0:1.13.1-3.el7ost · Red Hat:openstack:5::el7Package registry (OSV)
red hat:openstack-swift-account0:1.13.1-3.el7ost · Red Hat:openstack:5::el7Package registry (OSV)
red hat:openstack-swift-container0:1.13.1-3.el7ost · Red Hat:openstack:5::el7Package registry (OSV)
red hat:openstack-swift-doc0:1.13.1-3.el7ost · Red Hat:openstack:5::el7Package registry (OSV)
red hat:openstack-swift-object0:1.13.1-3.el7ost · Red Hat:openstack:5::el7Package registry (OSV)
red hat:openstack-swift-proxy0:1.13.1-3.el7ost · Red Hat:openstack:5::el7Package registry (OSV)
red hat:python-swiftclient0:2.1.0-2.el7ost · Red Hat:openstack:5::el7Package registry (OSV)
red hat:python-swiftclient-doc0:2.1.0-2.el7ost · Red Hat:openstack:5::el7Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

    If successful

    Confidentiality
    none
    Integrity
    P · data or configuration can be modified
    Availability
    none
    Attack complexity
    M
    Confidentiality impact
    None
    Integrity impact
    P
    Availability impact
    None

    CVSS vector

    AV:N/AC:M/Au:N/C:N/I:P/A:N

    nvd-primary

    Root cause

    User content is inserted into the page as HTML. The browser interprets the content as code rather than data.

    A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

    Vulnerable

    ts
    commentEl.innerHTML = comment.body;

    Fixed

    ts
    commentEl.textContent = comment.body;

    Noroxi analysis

    No Noroxi analysis for this record yet

    We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

    We use this product, ask for help

    Change log

    1. Fix✗ → ✓

    For records you follow, these changes also arrive as notifications. →

    References

    All records