PatchTheCVEmirantis vulnerabilities
Recent CVEs affecting mirantis products. 5 tracked.
mirantis has 5 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 4. Most recent: 2022-02-04. Highest priority: CVE-2022-0270 (score 51/100).
- CVE-2022-0484 HIGH 8.8 UPGRADE Lack of validation of URLs causes Mirantis Container Cloud Lens Extension before v3.1.1 to open external progr
- CVE-2022-0270 HIGH 8.8 UPGRADE Prior to v0.6.1, bored-agent failed to sanitize incoming kubernetes impersonation headers allowing a user to o
- CVE-2021-44458 HIGH 8.3 UPGRADE Linux users running Lens 5.2.6 and earlier could be compromised by visiting a malicious website
- CVE-2021-23218 MEDIUM 5.3 DOWNGRADE When running with FIPS mode enabled, Mirantis Container Runtime 20.10.8 leaks memory during TLS Handshakes whi
- CVE-2021-23154 MEDIUM 6.3 UPGRADE In Lens prior to 5.3.4, custom helm chart configuration creates helm commands from string concatenation of pro
FAQ
How do I fix mirantis 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 mirantis being exploited right now?
None of the tracked mirantis CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which mirantis CVE should I patch first?
CVE-2022-0270 currently ranks highest (51/100): Prior to v0.6.1, bored-agent failed to sanitize incoming kubernetes impersonation headers allowing a user to o.