CSRF token exfiltration in GitLab CE/EE Kubernetes Agent Server integration
CVE-2023-7045 is a cross-site request forgery vulnerability in GitLab Community Edition and Enterprise Edition affecting versions 13.11 before 16.10.6, 16.11 before 16.11.3, and 17.0 before 17.0.1. The flaw is associated with Kubernetes cluster integration and can be leveraged through the Kubernetes Agent Server (KAS) to exfiltrate anti-CSRF tokens. The issue allows a forged cross-site request in an authenticated user context to cause disclosure of CSRF protection material, weakening request integrity protections for subsequent actions.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Successful exploitation can expose anti-CSRF tokens from an authenticated GitLab user via KAS. Disclosure of these tokens can undermine GitLab's CSRF defenses and enable follow-on unauthorized actions performed in the victim's authenticated session context, with potential confidentiality and integrity impact depending on the victim's privileges and reachable application functionality.
If you can’t patch tonight, do this now.
If immediate patching is not possible, reduce exposure by limiting or disabling vulnerable Kubernetes integration paths involving KAS where operationally feasible, restricting access to GitLab to trusted origins and users, and minimizing opportunities for authenticated users to be induced to visit attacker-controlled content. Additional defensive measures include enforcing strong session hygiene and monitoring for suspicious cross-origin interactions involving Kubernetes integration features. Complete mitigation requires upgrading to a fixed version.
Patch, then assume compromise.
Upgrade GitLab CE/EE to a fixed release. Patched versions include 16.10.6, 16.11.3, and 17.0.1 or later. Self-managed deployments should update to one of these releases or a newer maintained version that includes the fix.
No public exploits tracked yet. Mallory keeps watching.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.