Title: EGI SVG 'ADVISORY' [TLP:WHITE] HIGH risk CVE-2021-25742 Kubernetes
NGinx Ingress Controller Vulnerability [EGI-SVG-CVE-2021-25742]
Date: 2021-11-03
Updated:
Affected software and risk
==========================
HIGH risk vulnerability concerning Kubernetes
Package : Kubernetes ingress-nginx
CVE ID : CVE-2021-25742
A security issue was discovered in ingress-nginx where a user that can create
or update ingress objects can use the custom snippets feature to obtain all
secrets in the cluster. [R 1], [R 2]
RedHat OpenShift versions are not affected. [R 3]
Actions required/recommended
============================
Sites running Kubernetes should upgrade any affected instances to a version
which allows mitigation and then carry out appropriate mitigation.
Component installation information
==================================
A full resolution of this vulnerability is not available at present, but
sites who run affected packages should upgrade to v1.0.1 or v0.49.1 or
higher and carry out mitigation.
Mitigation
==========
Mitigation is described in [R 1]
More information
================
See [R 1] and links therein.
TLP and URL
===========
** WHITE information - Unlimited distribution
- see https://go.egi.eu/tlp for
distribution restrictions **
URL: https://advisories.egi.eu/Advisory-SVG-CVE-2021-25742
Minor updates may be made without re-distribution to the sites
Comments
========
Comments or questions should be sent to svg-rat at mailman.egi.eu
If you find or become aware of another vulnerability which is relevant to
EGI you may report it by e-mail to
report-vulnerability at egi.eu
the EGI Software Vulnerability Group will take a look according to the
procedure defined in [R 99].
References
==========
[R 1] https://groups.google.com/g/kubernetes-security-announce/c/mT4JJxi9tQY/m/9nC_o87FBgAJ
[R 2] https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-25742
[R 3] Red Hat https://access.redhat.com/security/cve/CVE-2021-25742
[R 4] https://documents.egi.eu/public/ShowDocument?docid=3145
Credit
======
SVG was alerted to this vulnerability by Alexander Dibbo
Timeline
========
Yyyy-mm-dd [EGI-SVG-2021-CVE-2021-25742]
2021-10-22 SVG alerted to this issue by Alexander Dibbo
2021-10-22 Acknowledgement from the EGI SVG to the reporter
2021-10--- Investigation of vulnerability and relevance to EGI carried out
2021-10-28 EGI SVG Risk Assessment completed
2021-11-17 Advisory sent to sites
Context
=======
This advisory has been prepared as part of the effort to fulfil EGI SVG's
purpose "To minimize the risk to the EGI infrastructure arising from software
vulnerabilities"
The risk is that assessed by the group, according to the EGI SVG issue handling
procedure [R 99] in the context of how the software is used in the EGI
infrastructure. It is the opinion of the group, we do not guarantee it to be
correct. The risk may also be higher or lower in other deployments depending on
how the software is used.
-----------------------------
This advisory is subject to the Creative commons licence
https://creativecommons.org/licenses/by/4.0/ and
the EGI https://www.egi.eu/ Software Vulnerability Group must be credited.
------------------------------
Note that the SVG issue handling procedure has recently been modified, to
take account of the increasing inhomogeneity of the EGI infrastructure and
speed up the procedure for publicly announced vulnerabilities.
Changes are in the process of being implemented.
On behalf of the EGI SVG,