Loading vulnerability…
CVE-2022-3573 is a cross-site scripting vulnerability in GitLab CE and EE affecting all versions from 15.4 before 15.5.7, from 15.6 before 15.6.4, and from 15.7 before 15.7.2. The issue is caused by improper filtering of query parameters in the wiki changes page. Under affected conditions, an attacker can inject and execute arbitrary JavaScript in a victim’s browser when the crafted request is processed by a self-hosted GitLab instance that is not protected by a strict Content Security Policy. The flaw is client-side but can affect authenticated GitLab users interacting with the maliciously crafted page or link.
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.
A specific vulnerability listed by the article as one of the vulnerabilities exploited by AIRASHI.
Unknown (listed as exploited by AIRASHI; no additional details provided in the content).
A specific vulnerability listed among those used by AIRASHI; the content does not provide technical detail beyond inclusion in the propagation list.
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.