PatchTheCVEvegadns vulnerabilities
Recent CVEs affecting vegadns products. 2 tracked.
vegadns has 2 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2005-08-17. Highest priority: CVE-2005-2609 (score 41/100).
- CVE-2005-2610 MEDIUM 4.3 DOWNGRADE Cross-site scripting (XSS) vulnerability in index.php in VegaDNS 0.8.1, 0.9.8, and possibly other versions, al
- CVE-2005-2609 MEDIUM 5.0 DOWNGRADE index.php in VegaDNS 0.8.1, 0.9.8, and possibly other versions, allows remote attackers to obtain the full ser
FAQ
How do I fix vegadns 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 vegadns being exploited right now?
None of the tracked vegadns CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which vegadns CVE should I patch first?
CVE-2005-2609 currently ranks highest (41/100): index.php in VegaDNS 0.8.1, 0.9.8, and possibly other versions, allows remote attackers to obtain the full ser.