summaryrefslogtreecommitdiff
path: root/lib/console.js
diff options
context:
space:
mode:
authorjaekuk, lee <juku1999@samsung.com>2017-06-12 13:34:26 +0900
committerjaekuk, lee <juku1999@samsung.com>2017-06-12 14:20:13 +0900
commit44da52a1827bf05a010b12f4bccfb370fe4e59c2 (patch)
tree4ad770cdc91e61ba8a396a971ce8632bd5f7495f /lib/console.js
parenta05d5374516811b6680c54f2ed7cf4348baf82af (diff)
downloadnodejs-44da52a1827bf05a010b12f4bccfb370fe4e59c2.tar.gz
nodejs-44da52a1827bf05a010b12f4bccfb370fe4e59c2.tar.bz2
nodejs-44da52a1827bf05a010b12f4bccfb370fe4e59c2.zip
https://nvd.nist.gov/vuln/detail/CVE-2016-2105 https://git.openssl.org/?p=openssl.git;a=commit;h=5b814481f3573fa9677f3a31ee51322e2a22ee6a An overflow can occur in the EVP_EncodeUpdate function which is used for Base64 encoding of binary data. If an attacker is able to supply very large amounts of input data then a length check can overflow resulting in a heap corruption. Due to the very large amounts of data involved this will most likely result in a crash. Internally to OpenSSL the EVP_EncodeUpdate function is primarly used by the PEM_write_bio* family of functions. These are mainly used within the OpenSSL command line applications, so any application which processes data from an untrusted source and outputs it as a PEM file should be considered vulnerable to this issue. User applications that call these APIs directly with large amounts of untrusted data may also be vulnerable. Issue reported by Guido Vranken. CVE-2016-2105 Change-Id: Ie90201c3ac5c6203583620c5843d2cd896a69955 Signed-off-by: jaekuk, lee <juku1999@samsung.com>
Diffstat (limited to 'lib/console.js')
0 files changed, 0 insertions, 0 deletions