Bug 1486337 - CVE-2017-1000056 kubernetes: Privilege escalation in the PodSecurityPolicy admission plugin [fedora-25]
Summary: CVE-2017-1000056 kubernetes: Privilege escalation in the PodSecurityPolicy ad...
Alias: None
Product: Fedora
Classification: Fedora
Component: kubernetes
Version: 27
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Jan Chaloupka
QA Contact: Fedora Extras Quality Assurance
: 1516612 1516613 (view as bug list)
Depends On:
Blocks: CVE-2017-1000056
TreeView+ depends on / blocked
Reported: 2017-08-29 13:51 UTC by Andrej Nemec
Modified: 2018-06-18 12:07 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Release Note
Doc Text:
Clone Of:
Last Closed: 2018-06-18 12:07:16 UTC
Type: ---

Attachments (Terms of Use)

Description Andrej Nemec 2017-08-29 13:51:32 UTC
This is an automatically created tracking bug!  It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-25.

For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.

For more information see:

When submitting as an update, use the fedpkg template provided in the next
comment(s).  This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.

Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.

Comment 1 Andrej Nemec 2017-08-29 13:51:39 UTC
Use the following template to for the 'fedpkg update' request to submit an
update for this issue as it contains the top-level parent bug(s) as well as
this tracking bug.  This will ensure that all associated bugs get updated
when new packages are pushed to stable.


# bugfix, security, enhancement, newpackage (required)

# testing, stable

# Bug numbers: 1234,9876

# Description of your update
notes=Security fix for [PUT CVEs HERE]

# Enable request automation based on the stable/unstable karma thresholds

# Automatically close bugs when this marked as stable

# Suggest that users restart after update


Additionally, you may opt to use the bodhi web interface to submit updates:


Comment 2 Fedora End Of Life 2017-11-16 19:18:55 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 3 Mark Knowles 2017-11-23 05:26:53 UTC
*** Bug 1516612 has been marked as a duplicate of this bug. ***

Comment 4 Mark Knowles 2017-11-23 05:28:35 UTC
*** Bug 1516613 has been marked as a duplicate of this bug. ***

Comment 5 Jan Kurik 2018-05-31 08:00:17 UTC
This bug has been reported against a Fedora version which is already unsuported.
In compliance with FESCo decision how to handle EOL of Security issues [1],
I am changing the version to '27', the latest supported release.

Please check whether this bug is still an issue on the '27' release.
If you find this bug not being applicable on this release, please close it.

[1] https://pagure.io/fesco/issue/1736

Comment 6 Jan Chaloupka 2018-06-18 12:07:16 UTC
The current f27 build corresponds to v1.10.1. The patch already applied there with the underlying code refactored many times after that.

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