sfpagent vulnerabilities and fixes
Recent CVEs affecting sfpagent, with upgrade or downgrade steps. 1 tracked.
sfpagent has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 1. Most recent: 2014-04-23. Highest priority: CVE-2014-2888 (score 52/100).
- CVE-2014-2888 HIGH 7.5 UPGRADE lib/sfpagent/bsig.rb in the sfpagent gem before 0.4.15 for Ruby allows remote attackers to execute arbitrary c
FAQ
How do I fix sfpagent 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 sfpagent being exploited right now?
None of the tracked sfpagent CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which sfpagent CVE should I patch first?
CVE-2014-2888 currently ranks highest (52/100): lib/sfpagent/bsig.rb in the sfpagent gem before 0.4.15 for Ruby allows remote attackers to execute arbitrary c.