smb4k vulnerabilities
Recent CVEs affecting smb4k products. 5 tracked.
smb4k has 5 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2007-02-03. Highest priority: CVE-2007-0475 (score 24/100).
- CVE-2007-0475 MEDIUM 4.4 DOWNGRADE Multiple stack-based buffer overflows in utilities/smb4k_*.cpp in Smb4K before 0.8.0 allow local users, when p
- CVE-2007-0474 LOW 3.3 DOWNGRADE Smb4K before 0.8.0 allow local users, when present on the Smb4K sudoers list, to kill arbitrary processes, rel
- CVE-2007-0473 LOW 1.9 DOWNGRADE The writeFile function in core/smb4kfileio.cpp in Smb4K before 0.8.0 does not preserve /etc/sudoers permission
- CVE-2007-0472 LOW 3.7 DOWNGRADE Multiple race conditions in Smb4K before 0.8.0 allow local users to (1) modify arbitrary files via unspecified
- CVE-2005-2851 LOW 2.1 DOWNGRADE smb4k 0.4 and other versions before 0.6.3 allows local users to read sensitive files via a symlink attack on t
FAQ
How do I fix smb4k 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 smb4k being exploited right now?
None of the tracked smb4k CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which smb4k CVE should I patch first?
CVE-2007-0475 currently ranks highest (24/100): Multiple stack-based buffer overflows in utilities/smb4k_*.cpp in Smb4K before 0.8.0 allow local users, when p.