Arch Linux Security Advisory ASA-202111-7
========================================
Severity: High
Date    : 2021-11-18
CVE-ID  : CVE-2021-25742
Package : kubectl-ingress-nginx
Type    : information disclosure
Remote  : Yes
Link    : https://security.archlinux.org/AVG-2490

Summary
======
The package kubectl-ingress-nginx before version 1.0.4-1 is vulnerable
to information disclosure.

Resolution
=========
Upgrade to 1.0.4-1.

# pacman -Syu "kubectl-ingress-nginx>=1.0.4-1"

The problem has been fixed upstream in version 1.0.4.

Workaround
=========
This issue cannot be fixed solely by upgrading kubectl-ingress-nginx.
To mitigate, set allow-snippet-annotations to false in your ingress-
nginx ConfigMap based on how you deploy ingress-nginx, see the
references for more information.

Description
==========
A security issue was discovered in ingress-nginx before versions 1.0.1
and 0.49.1 where a user that can create or update ingress objects can
use the custom snippets feature to obtain all secrets in the cluster.

This issue cannot be fixed solely by upgrading ingress-nginx. To
mitigate, set allow-snippet-annotations to false in your ingress-nginx
ConfigMap based on how you deploy ingress-nginx, see the references for
more information.

Impact
=====
An authenticated remote attacker could disclose all secrets in the
cluster.

References
=========
https://github.com/kubernetes/ingress-nginx/issues/7837
https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/configmap/#allow-snippet-annotations
https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/configmap/
https://github.com/kubernetes/ingress-nginx/pull/7670
https://github.com/kubernetes/ingress-nginx/commit/4fc57dcc4969cd907c6eeadffbba2d14949db39e
https://security.archlinux.org/CVE-2021-25742

ArchLinux: 202111-7: kubectl-ingress-nginx: information disclosure

November 19, 2021

Summary

A security issue was discovered in ingress-nginx before versions 1.0.1 and 0.49.1 where a user that can create or update ingress objects can use the custom snippets feature to obtain all secrets in the cluster. This issue cannot be fixed solely by upgrading ingress-nginx. To mitigate, set allow-snippet-annotations to false in your ingress-nginx ConfigMap based on how you deploy ingress-nginx, see the references for more information.

Resolution

Upgrade to 1.0.4-1. # pacman -Syu "kubectl-ingress-nginx>=1.0.4-1"
The problem has been fixed upstream in version 1.0.4.

References

https://github.com/kubernetes/ingress-nginx/issues/7837 https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/configmap/#allow-snippet-annotations https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/configmap/ https://github.com/kubernetes/ingress-nginx/pull/7670 https://github.com/kubernetes/ingress-nginx/commit/4fc57dcc4969cd907c6eeadffbba2d14949db39e https://security.archlinux.org/CVE-2021-25742

Severity
Package : kubectl-ingress-nginx
Type : information disclosure
Remote : Yes
Link : https://security.archlinux.org/AVG-2490

Workaround

This issue cannot be fixed solely by upgrading kubectl-ingress-nginx.To mitigate, set allow-snippet-annotations to false in your ingress-nginx ConfigMap based on how you deploy ingress-nginx, see thereferences for more information.

Related News