PatchTheCVEdavid bagley vulnerabilities
Recent CVEs affecting david bagley products. 1 tracked.
david bagley has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 1. Most recent: 2014-05-30. Highest priority: CVE-2013-4143 (score 16/100).
- CVE-2013-4143 LOW 2.1 UPGRADE The (1) checkPasswd and (2) checkGroupXlockPasswds functions in xlockmore before 5.43 do not properly handle w
FAQ
How do I fix david bagley 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 david bagley being exploited right now?
None of the tracked david bagley CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which david bagley CVE should I patch first?
CVE-2013-4143 currently ranks highest (16/100): The (1) checkPasswd and (2) checkGroupXlockPasswds functions in xlockmore before 5.43 do not properly handle w.