pacemaker\/corosync configuration system vulnerabilities and fixes
Recent CVEs affecting pacemaker\/corosync configuration system, with upgrade or downgrade steps. 2 tracked.
Also searched as: pacemaker\/corosyncconfigurationsystem.
pacemaker\/corosync configuration system has 2 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 2. Most recent: 2015-09-03. Highest priority: CVE-2015-5190 (score 51/100).
- CVE-2015-5190 HIGH 8.5 UPGRADE The pcsd web UI in PCS 0.9.139 and earlier allows remote authenticated users to execute arbitrary commands via
- CVE-2015-5189 MEDIUM 4.9 UPGRADE Race condition in pcsd in PCS 0.9.139 and earlier uses a global variable to validate usernames, which allows r
FAQ
How do I fix pacemaker\/corosync configuration system 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 pacemaker\/corosync configuration system being exploited right now?
None of the tracked pacemaker\/corosync configuration system CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which pacemaker\/corosync configuration system CVE should I patch first?
CVE-2015-5190 currently ranks highest (51/100): The pcsd web UI in PCS 0.9.139 and earlier allows remote authenticated users to execute arbitrary commands via.