PatchTheCVEgopivotal vulnerabilities
Recent CVEs affecting gopivotal products. 4 tracked.
gopivotal has 4 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 1. Most recent: 2017-01-23. Highest priority: CVE-2016-6521 (score 50/100).
- CVE-2016-6521 HIGH 8.8 UPGRADE Cross-site request forgery (CSRF) vulnerability in Grails console (aka Grails Debug Console and Grails Web Con
- CVE-2014-2858 MEDIUM 5.0 DOWNGRADE DOWNGRADE Directory traversal vulnerability in the Resources plugin 1.0.0 before 1.2.6 for Pivotal Grails 2.0.0 through
- CVE-2014-2857 MEDIUM 5.0 DOWNGRADE DOWNGRADE The default configuration of the Resources plugin 1.0.0 before 1.2.6 for Pivotal Grails 2.0.0 through 2.3.6 do
- CVE-2014-0053 MEDIUM 5.0 DOWNGRADE DOWNGRADE The default configuration of the Resources plugin 1.0.0 before 1.2.6 for Pivotal Grails 2.0.0 before 2.3.6 doe
FAQ
How do I fix gopivotal 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 gopivotal being exploited right now?
None of the tracked gopivotal CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which gopivotal CVE should I patch first?
CVE-2016-6521 currently ranks highest (50/100): Cross-site request forgery (CSRF) vulnerability in Grails console (aka Grails Debug Console and Grails Web Con.