PatchTheCVEsecurenetterm vulnerabilities and fixes
Recent CVEs affecting securenetterm, with upgrade or downgrade steps. 4 tracked.
securenetterm has 4 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2002-12-23. Highest priority: CVE-2002-1359 (score 65/100).
- CVE-2002-1360 HIGH 10.0 MITIGATE DOWNGRADE Multiple SSH2 servers and clients do not properly handle strings with null characters in them when the string
- CVE-2002-1359 HIGH 10.0 MITIGATE DOWNGRADE Multiple SSH2 servers and clients do not properly handle large packets or large fields, which may allow remote
- CVE-2002-1358 HIGH 10.0 MITIGATE DOWNGRADE Multiple SSH2 servers and clients do not properly handle lists with empty elements or strings, which may allow
- CVE-2002-1357 HIGH 10.0 MITIGATE DOWNGRADE Multiple SSH2 servers and clients do not properly handle packets or data elements with incorrect length specif
FAQ
How do I fix securenetterm 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 securenetterm being exploited right now?
None of the tracked securenetterm CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which securenetterm CVE should I patch first?
CVE-2002-1359 currently ranks highest (65/100): Multiple SSH2 servers and clients do not properly handle large packets or large fields, which may allow remote.