CVE-2015-5271: TripleO Heat templates might allow remote attackers to obtain sensitive information from private containers

CVE-2015-5271 · Severity: low · CVSS 3 · Published 2016-04-15

The TripleO Heat templates (tripleo-heat-templates) do not properly order the Identity Service (keystone) before the OpenStack Object Storage (Swift) staticweb middleware in the swiftproxy pipeline when the staticweb middleware is enabled, which might allow remote attackers to obtain sensitive information from private containers via unspecified vectors.

Technologies: tripleo-heat-templates (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2015-5271 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2015-5271 being exploited in the wild.
How severe is CVE-2015-5271?
Low severity, with a CVSS score of 3, published 15 April 2016.
Which products and versions are affected?
tripleo-heat-templates (PyPI) ECOSYSTEM:introduced=0,fixed=0.8.7.
Is there a fix for CVE-2015-5271?
Yes. tripleo-heat-templates (PyPI): upgrade to 0.8.7 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2015-5271?
Check whether you run tripleo-heat-templates (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • tripleo-heat-templates (PyPI): upgrade to 0.8.7 or later
    pip install "tripleo-heat-templates>=0.8.7"

Affected products

  • tripleo-heat-templates (PyPI) ECOSYSTEM:introduced=0,fixed=0.8.7

Identifiers

  • CVE-2015-5271
  • GHSA-8936-44gw-7664
  • PYSEC-2016-34

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.