CVE-2021-25745: Ingress-nginx path can be pointed to service account token file

Published May 6, 2022
·
Updated

A security issue was discovered in ingress-nginx where a user that can create or update ingress objects can use the spec.rules[].http.paths[].path field of an Ingress object (in the networking.k8s.io or extensions API group) to obtain the credentials of the ingress-nginx controller. In the default configuration, that credential has access to all secrets in the cluster.

Affected Software

1 affected component
Kubernetes ingress-nginx<1.2.0

Event History

May 6, 2022
CVE Published
via MITRE·12:50 AM
Data Sourced
via MITRE·12:50 AM
DescriptionSeverityWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the vulnerability ID for this security issue?

The vulnerability ID for this security issue is CVE-2021-25745.

2

What is the severity of CVE-2021-25745?

The severity of CVE-2021-25745 is high with a CVSS score of 8.1.

3

How does the vulnerability in ingress-nginx affect me?

If you can create or update ingress objects and are using a version of ingress-nginx up to 1.2.0, you may be affected by this vulnerability.

4

How can an attacker exploit CVE-2021-25745?

An attacker can exploit CVE-2021-25745 by using the spec.rules[].http.paths[].path field of an Ingress object to obtain the credentials of the ingress-nginx controller.

5

How can I fix CVE-2021-25745?

To fix CVE-2021-25745, update your ingress-nginx installation to a version higher than 1.2.0.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203