CVE-2020-13264: Infoleak

Published Jun 19, 2020
·
Updated

Kubernetes cluster token disclosure in GitLab CE/EE 10.3 and later through 13.0.1 allows other group maintainers to view Kubernetes cluster token

Affected Software

6 affected components
GitLab GitLab>=10.3.0<12.9.8
GitLab GitLab>=10.3.0<12.9.8
GitLab GitLab>=12.10.0<12.10.7
GitLab GitLab>=12.10.0<12.10.7
GitLab GitLab=13.0.0
GitLab GitLab=13.0.0

Event History

Jun 19, 2020
CVE Published
via MITRE·10:13 PM
Data Sourced
via MITRE·10:13 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

What is the severity of CVE-2020-13264?

CVE-2020-13264 has a medium severity rating due to the potential for Kubernetes cluster token disclosure.

2

How do I fix CVE-2020-13264?

To fix CVE-2020-13264, upgrade your GitLab instance to version 12.10.8 or later, or 13.0.2 or later.

3

Which GitLab versions are affected by CVE-2020-13264?

CVE-2020-13264 affects GitLab CE/EE version 10.3.0 through 12.9.8 and version 12.10.0 through 12.10.7, as well as version 13.0.0.

4

What are the implications of CVE-2020-13264?

The implications of CVE-2020-13264 include unauthorized access to Kubernetes cluster tokens, which can lead to further security risks in the cluster.

5

Who is impacted by CVE-2020-13264?

Group maintainers in GitLab can be impacted by CVE-2020-13264 as they may have visibility into Kubernetes cluster tokens that they shouldn't access.

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