Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

log4sh vulnerabilities and fixes

Recent CVEs affecting log4sh, with upgrade or downgrade steps. 1 tracked.

log4sh has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2005-09-02. Highest priority: CVE-2005-1915 (score 14/100).

FAQ

How do I fix log4sh 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 log4sh being exploited right now?

None of the tracked log4sh CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.

Which log4sh CVE should I patch first?

CVE-2005-1915 currently ranks highest (14/100): The log4sh_readProperties function in log4sh 1.2.5 and earlier allows local users to overwrite arbitrary files.

← Back to latest CVEs