json-bigint vulnerabilities and fixes

Q: How do I fix json-bigint 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 json-bigint being exploited right now?

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

Q: Which json-bigint CVE should I patch first?

CVE-2020-8237 currently ranks highest (56/100): Prototype pollution in json-bigint npm package < 1.0.0 may lead to a denial-of-service (DoS) attack..

Recent CVEs affecting json-bigint, with upgrade or downgrade steps. 1 tracked.

Also searched as: json bigint.

json-bigint has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 1. Most recent: 2020-09-18. Highest priority: CVE-2020-8237 (score 56/100).

CVE-2020-8237 HIGH 7.5 UPGRADE Prototype pollution in json-bigint npm package < 1.0.0 may lead to a denial-of-service (DoS) attack.

FAQ

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

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

Which json-bigint CVE should I patch first?

CVE-2020-8237 currently ranks highest (56/100): Prototype pollution in json-bigint npm package < 1.0.0 may lead to a denial-of-service (DoS) attack..

← Back to latest CVEs