PatchTheCVEyukihiro matsumoto vulnerabilities
Recent CVEs affecting yukihiro matsumoto products. 7 tracked.
yukihiro matsumoto has 7 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2006-12-06. Highest priority: CVE-2005-1992 (score 50/100).
- CVE-2006-6303 MEDIUM 5.0 DOWNGRADE The read_multipart function in cgi.rb in Ruby before 1.8.5-p2 does not properly detect boundaries in MIME mult
- CVE-2006-5467 MEDIUM 5.0 DOWNGRADE The cgi.rb CGI library for Ruby 1.8 allows remote attackers to cause a denial of service (infinite loop and CP
- CVE-2006-3694 MEDIUM 6.4 DOWNGRADE Multiple unspecified vulnerabilities in Ruby before 1.8.5 allow remote attackers to bypass "safe level" checks
- CVE-2005-2337 HIGH 7.5 DOWNGRADE Ruby 1.6.x up to 1.6.8, 1.8.x up to 1.8.2, and 1.9.0 development up to 2005-09-01 allows attackers to bypass s
- CVE-2005-1992 HIGH 7.5 DOWNGRADE The XMLRPC server in utils.rb for the ruby library (libruby) 1.8 sets an invalid default value that prevents "
- CVE-2004-0983 MEDIUM 5.0 DOWNGRADE MITIGATE The CGI module in Ruby 1.6 before 1.6.8, and 1.8 before 1.8.2, allows remote attackers to cause a denial of se
- CVE-2004-0755 LOW 2.1 DOWNGRADE The FileStore capability in CGI::Session for Ruby before 1.8.1, and possibly PStore, creates files with insecu
FAQ
How do I fix yukihiro matsumoto 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 yukihiro matsumoto being exploited right now?
None of the tracked yukihiro matsumoto CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which yukihiro matsumoto CVE should I patch first?
CVE-2005-1992 currently ranks highest (50/100): The XMLRPC server in utils.rb for the ruby library (libruby) 1.8 sets an invalid default value that prevents ".