lsh vulnerabilities and fixes
Recent CVEs affecting lsh, with upgrade or downgrade steps. 3 tracked.
lsh has 3 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2006-01-22. Highest priority: CVE-2003-0826 (score 55/100).
- CVE-2006-0353 LOW 3.6 DOWNGRADE unix_random.c in lshd for lsh 2.0.1 leaks file descriptors related to the randomness generator, which allows l
- CVE-2005-0814 MEDIUM 5.0 DOWNGRADE Unknown vulnerability in lshd in Lysator LSH 1.x and 2.x before 2.0.1 allows remote attackers to cause a denia
- CVE-2003-0826 HIGH 7.5 DOWNGRADE lsh daemon (lshd) does not properly return from certain functions in (1) read_line.c, (2) channel_commands.c,
FAQ
How do I fix lsh 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 lsh being exploited right now?
None of the tracked lsh CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which lsh CVE should I patch first?
CVE-2003-0826 currently ranks highest (55/100): lsh daemon (lshd) does not properly return from certain functions in (1) read_line.c, (2) channel_commands.c, .