ID CVE-2020-8252
Summary The implementation of realpath in libuv < 10.22.1, < 12.18.4, and < 14.9.0 used within Node.js incorrectly determined the buffer size which can result in a buffer overflow if the resolved path is longer than 256 bytes.
References
Vulnerable Configurations
  • cpe:2.3:a:nodejs:node.js:10.0.0:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:10.0.0:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:10.1.0:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:10.1.0:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:10.2.0:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:10.2.0:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:10.2.1:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:10.2.1:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:10.3.0:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:10.3.0:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:10.4.0:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:10.4.0:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:10.4.1:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:10.4.1:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:10.5.0:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:10.5.0:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:10.6.0:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:10.6.0:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:10.7.0:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:10.7.0:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:10.8.0:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:10.8.0:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:10.9.0:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:10.9.0:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:10.10.0:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:10.10.0:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:10.11.0:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:10.11.0:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:10.12.0:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:10.12.0:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:10.13.0:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:10.13.0:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:10.14.0:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:10.14.0:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:10.14.1:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:10.14.1:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:10.14.2:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:10.14.2:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:10.15.0:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:10.15.0:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:10.15.1:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:10.15.1:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:10.15.2:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:10.15.2:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:10.15.3:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:10.15.3:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:10.16.0:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:10.16.0:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:10.16.1:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:10.16.1:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:10.16.2:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:10.16.2:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:10.16.3:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:10.16.3:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:10.17.0:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:10.17.0:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:10.18.0:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:10.18.0:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:10.18.1:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:10.18.1:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:10.19.0:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:10.19.0:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:10.20.0:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:10.20.0:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:10.20.1:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:10.20.1:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:10.21.0:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:10.21.0:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:10.22.0:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:10.22.0:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:12.0.0:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:12.0.0:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:12.1.0:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:12.1.0:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:12.2.0:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:12.2.0:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:12.3.0:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:12.3.0:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:12.3.1:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:12.3.1:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:12.4.0:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:12.4.0:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:12.5.0:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:12.5.0:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:12.6.0:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:12.6.0:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:12.7.0:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:12.7.0:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:12.8.0:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:12.8.0:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:12.8.1:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:12.8.1:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:12.9.0:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:12.9.0:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:12.9.1:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:12.9.1:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:12.10.0:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:12.10.0:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:12.11.0:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:12.11.0:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:12.11.1:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:12.11.1:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:12.12.0:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:12.12.0:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:12.13.0:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:12.13.0:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:12.13.1:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:12.13.1:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:12.14.0:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:12.14.0:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:12.14.1:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:12.14.1:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:12.15.0:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:12.15.0:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:12.16.0:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:12.16.0:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:12.16.1:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:12.16.1:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:12.16.2:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:12.16.2:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:12.16.3:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:12.16.3:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:12.17.0:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:12.17.0:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:12.18.0:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:12.18.0:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:12.18.1:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:12.18.1:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:12.18.2:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:12.18.2:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:12.18.3:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:12.18.3:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:12.18.4:*:*:*:lts:*:*:*
    cpe:2.3:a:nodejs:node.js:12.18.4:*:*:*:lts:*:*:*
  • cpe:2.3:a:nodejs:node.js:*:*:*:*:-:*:*:*
    cpe:2.3:a:nodejs:node.js:*:*:*:*:-:*:*:*
  • cpe:2.3:o:opensuse:leap:15.2:*:*:*:*:*:*:*
    cpe:2.3:o:opensuse:leap:15.2:*:*:*:*:*:*:*
CVSS
Base: 4.6 (as of 13-12-2020 - 04:15)
Impact:
Exploitability:
CWE CWE-120
CAPEC
  • Overflow Variables and Tags
    This type of attack leverages the use of tags or variables from a formatted configuration data to cause buffer overflow. The attacker crafts a malicious HTML page or configuration file that includes oversized strings, thus causing an overflow.
  • Buffer Overflow in an API Call
    This attack targets libraries or shared code modules which are vulnerable to buffer overflow attacks. An attacker who has access to an API may try to embed malicious code in the API function call and exploit a buffer overflow vulnerability in the function's implementation. All clients that make use of the code library thus become vulnerable by association. This has a very broad effect on security across a system, usually affecting more than one software process.
  • String Format Overflow in syslog()
    This attack targets the format string vulnerabilities in the syslog() function. An attacker would typically inject malicious input in the format string parameter of the syslog function. This is a common problem, and many public vulnerabilities and associated exploits have been posted.
  • Buffer Overflow via Environment Variables
    This attack pattern involves causing a buffer overflow through manipulation of environment variables. Once the attacker finds that they can modify an environment variable, they may try to overflow associated buffers. This attack leverages implicit trust often placed in environment variables.
  • Filter Failure through Buffer Overflow
    In this attack, the idea is to cause an active filter to fail by causing an oversized transaction. An attacker may try to feed overly long input strings to the program in an attempt to overwhelm the filter (by causing a buffer overflow) and hoping that the filter does not fail securely (i.e. the user input is let into the system unfiltered).
  • Buffer Overflow via Parameter Expansion
    In this attack, the target software is given input that the attacker knows will be modified and expanded in size during processing. This attack relies on the target software failing to anticipate that the expanded data may exceed some internal limit, thereby creating a buffer overflow.
  • Buffer Overflow in Local Command-Line Utilities
    This attack targets command-line utilities available in a number of shells. An attacker can leverage a vulnerability found in a command-line utility to escalate privilege to root.
  • Client-side Injection-induced Buffer Overflow
    This type of attack exploits a buffer overflow vulnerability in targeted client software through injection of malicious content from a custom-built hostile service.
  • Overflow Binary Resource File
    An attack of this type exploits a buffer overflow vulnerability in the handling of binary resources. Binary resources may include music files like MP3, image files like JPEG files, and any other binary file. These attacks may pass unnoticed to the client machine through normal usage of files, such as a browser loading a seemingly innocent JPEG file. This can allow the attacker access to the execution stack and execute arbitrary code in the target process. This attack pattern is a variant of standard buffer overflow attacks using an unexpected vector (binary files) to wrap its attack and open up a new attack vector. The attacker is required to either directly serve the binary content to the victim, or place it in a locale like a MP3 sharing application, for the victim to download. The attacker then is notified upon the download or otherwise locates the vulnerability opened up by the buffer overflow.
  • MIME Conversion
    An attacker exploits a weakness in the MIME conversion routine to cause a buffer overflow and gain control over the mail server machine. The MIME system is designed to allow various different information formats to be interpreted and sent via e-mail. Attack points exist when data are converted to MIME compatible format and back.
  • Buffer Overflow via Symbolic Links
    This type of attack leverages the use of symbolic links to cause buffer overflows. An attacker can try to create or manipulate a symbolic link file such that its contents result in out of bounds data. When the target software processes the symbolic link file, it could potentially overflow internal buffers with insufficient bounds checking.
  • Overflow Buffers
    Buffer Overflow attacks target improper or missing bounds checking on buffer operations, typically triggered by input injected by an adversary. As a consequence, an adversary is able to write past the boundaries of allocated buffer regions in memory, causing a program crash or potentially redirection of execution as per the adversaries' choice.
  • Forced Integer Overflow
    This attack forces an integer variable to go out of range. The integer variable is often used as an offset such as size of memory allocation or similarly. The attacker would typically control the value of such variable and try to get it out of range. For instance the integer in question is incremented past the maximum possible value, it may wrap to become a very small, or negative number, therefore providing a very incorrect value which can lead to unexpected behavior. At worst the attacker can execute arbitrary code.
Access
VectorComplexityAuthentication
LOCAL LOW NONE
Impact
ConfidentialityIntegrityAvailability
PARTIAL PARTIAL PARTIAL
cvss-vector via4 AV:L/AC:L/Au:N/C:P/I:P/A:P
redhat via4
advisories
bugzilla
id 1883966
title The nodejs:12/development module is not installable [rhel-8.2.0.z]
oval
OR
  • comment Red Hat Enterprise Linux must be installed
    oval oval:com.redhat.rhba:tst:20070304026
  • AND
    • comment Red Hat Enterprise Linux 8 is installed
      oval oval:com.redhat.rhba:tst:20193384074
    • comment Module nodejs:12 is enabled
      oval oval:com.redhat.rhea:tst:20200330015
    • OR
      • AND
        • comment nodejs is earlier than 1:12.18.4-2.module+el8.2.0+8361+192e434e
          oval oval:com.redhat.rhsa:tst:20204272001
        • comment nodejs is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhea:tst:20200330002
      • AND
        • comment nodejs-debugsource is earlier than 1:12.18.4-2.module+el8.2.0+8361+192e434e
          oval oval:com.redhat.rhsa:tst:20204272003
        • comment nodejs-debugsource is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhea:tst:20200330004
      • AND
        • comment nodejs-devel is earlier than 1:12.18.4-2.module+el8.2.0+8361+192e434e
          oval oval:com.redhat.rhsa:tst:20204272005
        • comment nodejs-devel is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhea:tst:20200330006
      • AND
        • comment nodejs-docs is earlier than 1:12.18.4-2.module+el8.2.0+8361+192e434e
          oval oval:com.redhat.rhsa:tst:20204272007
        • comment nodejs-docs is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhea:tst:20200330008
      • AND
        • comment nodejs-full-i18n is earlier than 1:12.18.4-2.module+el8.2.0+8361+192e434e
          oval oval:com.redhat.rhsa:tst:20204272009
        • comment nodejs-full-i18n is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20202848010
      • AND
        • comment nodejs-nodemon is earlier than 0:1.18.3-1.module+el8.1.0+3369+37ae6a45
          oval oval:com.redhat.rhea:tst:20200330009
        • comment nodejs-nodemon is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhea:tst:20200330010
      • AND
        • comment nodejs-packaging is earlier than 0:17-3.module+el8.1.0+3369+37ae6a45
          oval oval:com.redhat.rhea:tst:20200330011
        • comment nodejs-packaging is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhea:tst:20200330012
      • AND
        • comment npm is earlier than 1:6.14.6-1.12.18.4.2.module+el8.2.0+8361+192e434e
          oval oval:com.redhat.rhsa:tst:20204272015
        • comment npm is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhea:tst:20200330014
rhsa
id RHSA-2020:4272
released 2020-10-19
severity Moderate
title RHSA-2020:4272: nodejs:12 security and bug fix update (Moderate)
rpms
  • nodejs-1:12.18.4-2.module+el8.2.0+8361+192e434e
  • nodejs-debuginfo-1:12.18.4-2.module+el8.2.0+8361+192e434e
  • nodejs-debugsource-1:12.18.4-2.module+el8.2.0+8361+192e434e
  • nodejs-devel-1:12.18.4-2.module+el8.2.0+8361+192e434e
  • nodejs-docs-1:12.18.4-2.module+el8.2.0+8361+192e434e
  • nodejs-full-i18n-1:12.18.4-2.module+el8.2.0+8361+192e434e
  • nodejs-nodemon-0:1.18.3-1.module+el8.1.0+3369+37ae6a45
  • nodejs-packaging-0:17-3.module+el8.1.0+3369+37ae6a45
  • npm-1:6.14.6-1.12.18.4.2.module+el8.2.0+8361+192e434e
  • nodejs-1:12.18.4-2.module+el8.1.0+8360+14141500
  • nodejs-debuginfo-1:12.18.4-2.module+el8.1.0+8360+14141500
  • nodejs-debugsource-1:12.18.4-2.module+el8.1.0+8360+14141500
  • nodejs-devel-1:12.18.4-2.module+el8.1.0+8360+14141500
  • nodejs-docs-1:12.18.4-2.module+el8.1.0+8360+14141500
  • nodejs-full-i18n-1:12.18.4-2.module+el8.1.0+8360+14141500
  • nodejs-nodemon-0:1.18.3-1.module+el8.1.0+3369+37ae6a45
  • nodejs-packaging-0:17-3.module+el8.1.0+3369+37ae6a45
  • npm-1:6.14.6-1.12.18.4.2.module+el8.1.0+8360+14141500
  • rh-nodejs12-nodejs-0:12.18.4-3.el7
  • rh-nodejs12-nodejs-debuginfo-0:12.18.4-3.el7
  • rh-nodejs12-nodejs-devel-0:12.18.4-3.el7
  • rh-nodejs12-nodejs-docs-0:12.18.4-3.el7
  • rh-nodejs12-npm-0:6.14.6-12.18.4.3.el7
refmap via4
confirm https://security.netapp.com/advisory/ntap-20201009-0004/
fedora FEDORA-2020-43d5a372fc
gentoo GLSA-202009-15
misc
suse
  • openSUSE-SU-2020:1616
  • openSUSE-SU-2020:1660
ubuntu USN-4548-1
Last major update 13-12-2020 - 04:15
Published 18-09-2020 - 21:15
Last modified 13-12-2020 - 04:15
Back to Top