Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

nmap4j vulnerabilities and fixes

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

nmap4j has 1 tracked vulnerability, 1 critical. A fixed release or vendor patch exists for 0. Most recent: 2018-09-19. Highest priority: CVE-2018-17228 (score 63/100).

FAQ

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

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

Which nmap4j CVE should I patch first?

CVE-2018-17228 currently ranks highest (63/100): nmap4j 1.1.0 allows attackers to execute arbitrary commands via shell metacharacters in an includeHosts call..

← Back to latest CVEs