drago vulnerabilities and fixes
Recent CVEs affecting drago, with upgrade or downgrade steps. 1 tracked.
drago has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 1. Most recent: 2022-02-18. Highest priority: CVE-2022-25335 (score 54/100).
- CVE-2022-25335 HIGH 7.5 UPGRADE RigoBlock Dragos through 2022-02-17 lacks the onlyOwner modifier for setMultipleAllowances
FAQ
How do I fix drago 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 drago being exploited right now?
None of the tracked drago CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which drago CVE should I patch first?
CVE-2022-25335 currently ranks highest (54/100): RigoBlock Dragos through 2022-02-17 lacks the onlyOwner modifier for setMultipleAllowances.