PatchTheCVEinspircd vulnerabilities
Recent CVEs affecting inspircd products. 8 tracked.
inspircd has 8 tracked vulnerabilities, 2 critical. A fixed release or vendor patch exists for 8. Most recent: 2021-05-27. Highest priority: CVE-2015-8702 (score 66/100).
- CVE-2021-33586 MEDIUM 4.3 UPGRADE InspIRCd 3.8.0 through 3.9.x before 3.10.0 allows any user (able to connect to the server) to access recently
- CVE-2020-25269 MEDIUM 6.5 UPGRADE MITIGATE An issue was discovered in InspIRCd 2 before 2.0.29 and 3 before 3.6.0
- CVE-2019-20918 MEDIUM 6.5 UPGRADE An issue was discovered in InspIRCd 3 before 3.1.0
- CVE-2019-20917 MEDIUM 6.5 UPGRADE MITIGATE An issue was discovered in InspIRCd 2 before 2.0.28 and 3 before 3.3.0
- CVE-2016-7142 MEDIUM 5.9 UPGRADE MITIGATE The m_sasl module in InspIRCd before 2.0.23, when used with a service that supports SASL_EXTERNAL authenticati
- CVE-2015-8702 HIGH 8.6 MITIGATE UPGRADE The DNS::GetResult function in dns.cpp in InspIRCd before 2.0.19 allows remote DNS servers to cause a denial o
- CVE-2015-6674 CRITICAL 9.8 UPGRADE MITIGATE Buffer underflow vulnerability in the Debian inspircd package before 2.0.5-1+deb7u1 for wheezy and before 2.0.
- CVE-2012-6696 CRITICAL 9.8 UPGRADE inspircd in Debian before 2.0.7 does not properly handle unsigned integers
FAQ
How do I fix inspircd 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 inspircd being exploited right now?
None of the tracked inspircd CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which inspircd CVE should I patch first?
CVE-2015-8702 currently ranks highest (66/100): The DNS::GetResult function in dns.cpp in InspIRCd before 2.0.19 allows remote DNS servers to cause a denial o.