public.js vulnerabilities and fixes

Q: How do I fix public.js 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.

Q: Is public.js being exploited right now?

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

Q: Which public.js CVE should I patch first?

CVE-2018-3731 currently ranks highest (56/100): public node module suffers from a Path Traversal vulnerability due to lack of validation of filePath, which al.

Recent CVEs affecting public.js, with upgrade or downgrade steps. 2 tracked.

Also searched as: public js, publicjs.

public.js has 2 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 1. Most recent: 2018-07-03. Highest priority: CVE-2018-3731 (score 56/100).

CVE-2018-3747 MEDIUM 6.1 UPGRADE The public node module versions <= 1.0.3 allows to embed HTML in file names, which (in certain conditions) mig
CVE-2018-3731 HIGH 7.5 DOWNGRADE public node module suffers from a Path Traversal vulnerability due to lack of validation of filePath, which al

FAQ

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

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

Which public.js CVE should I patch first?

CVE-2018-3731 currently ranks highest (56/100): public node module suffers from a Path Traversal vulnerability due to lack of validation of filePath, which al.

← Back to latest CVEs