yast2 vulnerabilities and fixes
Recent CVEs affecting yast2, with upgrade or downgrade steps. 2 tracked.
yast2 has 2 tracked vulnerabilities, 1 critical. A fixed release or vendor patch exists for 0. Most recent: 2017-09-08. Highest priority: CVE-2016-1601 (score 65/100).
- CVE-2016-1601 CRITICAL 9.8 MITIGATE yast2-users before 3.1.47, as used in SUSE Linux Enterprise 12 SP1, does not properly set empty password field
- CVE-2011-3177 HIGH 7.8 MITIGATE The YaST2 network created files with world readable permissions which could have allowed local users to read s
FAQ
How do I fix yast2 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 yast2 being exploited right now?
None of the tracked yast2 CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which yast2 CVE should I patch first?
CVE-2016-1601 currently ranks highest (65/100): yast2-users before 3.1.47, as used in SUSE Linux Enterprise 12 SP1, does not properly set empty password field.