CVE-2024-8635 is a server-side request forgery vulnerability in GitLab Enterprise Edition affecting versions starting from 16.8 before 17.1.7, from 17.2 before 17.2.5, and from 17.3 before 17.3.2. The flaw exists in handling of a custom Maven Dependency Proxy URL, which could be abused to cause the GitLab server to issue requests to internal resources. This allows an attacker to leverage the GitLab instance as a proxy to reach network locations that may not be directly accessible from the attacker’s environment.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
High-severity GitLab EE SSRF vulnerability that allows requests to internal resources via Maven Dependency Proxy.
A high-severity GitLab EE server-side request forgery vulnerability in Dependency Proxy that allows requests to internal resources via a custom Maven Dependency Proxy URL.
GitLab EE Dependency Proxy SSRF allowing access to internal resources via a crafted custom Maven Dependency Proxy URL.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.