immuta vulnerabilities and fixes
Recent CVEs affecting immuta, with upgrade or downgrade steps. 4 tracked.
immuta has 4 tracked vulnerabilities, 1 critical. A fixed release or vendor patch exists for 0. Most recent: 2020-11-05. Highest priority: CVE-2020-15952 (score 57/100).
- CVE-2020-15952 CRITICAL 9.0 DOWNGRADE Immuta v2.8.2 is affected by stored XSS that allows a low-privileged user to escalate privileges to administra
- CVE-2020-15951 MEDIUM 6.1 DOWNGRADE Immuta v2.8.2 accepts user-supplied project names without properly sanitizing the input, allowing attackers to
- CVE-2020-15950 HIGH 8.8 DOWNGRADE Immuta v2.8.2 is affected by improper session management: user sessions are not revoked upon logout.
- CVE-2020-15949 HIGH 7.5 DOWNGRADE Immuta v2.8.2 is affected by one instance of insecure permissions that can lead to user account takeover.
FAQ
How do I fix immuta vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is immuta being exploited right now?
None of the tracked immuta CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which immuta CVE should I patch first?
CVE-2020-15952 currently ranks highest (57/100): Immuta v2.8.2 is affected by stored XSS that allows a low-privileged user to escalate privileges to administra.