Important: Node.js 12 Security Update

nodejs-nodemon Updated 02 Oct 2025

Summary

07/07/2020
N/A
Yes i
Unrated
Not published

ALSA-2020:2852: Important: nodejs:12 security update. Affects nodejs-nodemon across 2 version ranges.

< 1.18.3-1.module_el8.3.0+2023+d2377ea3 < 1.18.3-1.module_el8.3.0+2047+b07ac28e

Fixed in 1.18.3-1.module_el8.3.0+2023+d2377ea3 or 1.18.3-1.module_el8.3.0+2047+b07ac28e, depending on the release line you run. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Node.js is a software development platform for building fast and scalable network applications in the JavaScript programming language. It is widely used for server-side and networking applications. The vulnerability affects the Node.js package in version 12.18.2.

Vulnerability Detail

The vulnerability includes the following security issues:

  1. CVE-2020-11080: nghttp2 - Overly large SETTINGS frames can lead to Denial of Service (DoS) attacks.
  2. CVE-2020-7598: nodejs-minimist - Prototype pollution allows adding or modifying properties of Object.prototype using a constructor or proto payload.
  3. CVE-2020-8172: nodejs - TLS session reuse can lead to hostname verification bypass.
  4. CVE-2020-8174: nodejs - Memory corruption in napi_get_value_string_* functions.

These vulnerabilities can have various impacts, including DoS attacks, unauthorized access, and memory corruption.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

sudo dnf update nodejs-nodemon
  • < 1.18.3-1.module_el8.3.0+2023+d2377ea3 1.18.3-1.module_el8.3.0+2023+d2377ea3
  • < 1.18.3-1.module_el8.3.0+2047+b07ac28e 1.18.3-1.module_el8.3.0+2047+b07ac28e

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Conclusion

It is important to update the Node.js package to version 12.18.2 or later to address these security vulnerabilities. For further support on vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for nodejs-nodemon →

Share this vulnerability

FAQ

Node.js is a software development platform for building fast and scalable network applications in the JavaScript programming language.

These vulnerabilities can lead to DoS attacks, unauthorized access, and memory corruption.

To fix the vulnerabilities, update the Node.js package to version 12.18.2 or later.

No specific workarounds have been provided for these vulnerabilities.

You can find more information about these vulnerabilities on the CVE pages listed in the References section.

Related vulnerabilities

Recent vulnerabilities recorded for nodejs-nodemon.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

sudo dnf update nodejs-nodemon
  • < 1.18.3-1.module_el8.3.0+2023+d2377ea3 1.18.3-1.module_el8.3.0+2023+d2377ea3
  • < 1.18.3-1.module_el8.3.0+2047+b07ac28e 1.18.3-1.module_el8.3.0+2047+b07ac28e

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback