Loading vulnerability…
CVE-2023-3932 is an incorrect user management vulnerability in GitLab Enterprise Edition that affects all versions from 13.12 before 16.0.8, 16.1 before 16.1.3, and 16.2 before 16.2.2. The flaw allows an attacker to cause pipeline jobs to run as an arbitrary user through scheduled security scan policies. The issue stems from improper handling of user context or authorization in the scheduled security scan policy workflow, enabling pipeline execution under another user’s identity rather than the attacker’s own effective permissions.
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.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An incorrect user management vulnerability in GitLab EE that allows an attacker to run pipeline jobs as an arbitrary user via scheduled security scan policies.
A previously addressed GitLab vulnerability that CVE-2023-5009 bypasses, resulting in additional impact.
A high-severity GitLab EE vulnerability that allows attackers to run pipeline jobs as an arbitrary user via scheduled security scan policies.
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.