Bug 1316267 - (CVE-2016-2149) CVE-2016-2149 OpenShift Enterprise 3: logs from a deleted namespace can be revealed if a new namespace with the same name is created
CVE-2016-2149 OpenShift Enterprise 3: logs from a deleted namespace can be re...
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Red Hat Product Security
: Security
Depends On: 1316216 1316271 1316272 1316273
Blocks: OSOPS_V3 1316274 1326106 1326107
  Show dependency treegraph
Reported: 2016-03-09 15:09 EST by Kurt Seifried
Modified: 2016-05-12 12:45 EDT (History)
10 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
It was found that OpenShift Enterprise would disclose log file contents from reclaimed namespaces. An attacker could create a new namespace to access log files present in a previously deleted namespace using the same name.
Story Points: ---
Clone Of:
Last Closed: 2016-05-12 12:45:32 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Kurt Seifried 2016-03-09 15:09:56 EST
Wesley Hearn of Red Hat reports:

Description of problem:
Users are able to access logs of a deleted namespace if recreated with the same name regardless if they were the previous owner.

Steps to Reproduce:
1. User A creates a namespace and populates logs
2. User A deletes namespace
3. User B creates a new namespace with the same name

Actual results:
User B can access logs from User A's namespace

Expected results:
User B should be restricted to logs generated from the pods he created in his new namespace.
Comment 1 Kurt Seifried 2016-03-09 15:10:07 EST

Name: Wesley Hearn (Red Hat)
Comment 4 errata-xmlrpc 2016-05-12 12:32:20 EDT
This issue has been addressed in the following products:

  Red Hat OpenShift Enterprise 3.2

Via RHSA-2016:1064 https://access.redhat.com/errata/RHSA-2016:1064

Note You need to log in before you can comment on or make changes to this bug.