Описание
Security update for nodejs
nodejs was updated to LTS release 4.7.3 to fix the following issues:
- deps: upgrade embedded openssl sources to 1.0.2k (CVE-2017-3731, CVE-2017-3732, CVE-2016-7055, boo#1022085, boo#1022086, boo#1009528)
Changes in LTS release 4.7.1:
- build: shared library support is now working for AIX builds
- repl: passing options to the repl will no longer overwrite defaults
- timers: recanceling a cancelled timers will no longer throw
Changes in LTS release 4.7.0:
- build: introduce the configure --shared option for embedders
- debugger: make listen address configurable in debugger server
- dgram: generalized send queue to handle close, fixing a potential throw when dgram socket is closed in the listening event handler
- http: introduce the 451 status code 'Unavailable For Legal Reasons'
- gtest: the test reporter now outputs tap comments as yamlish
- tls: introduce secureContext for tls.connect (useful for caching client certificates, key, and CA certificates)
- tls: fix memory leak when writing data to TLSWrap instance during handshake
- src: node no longer aborts when c-ares initialization fails
Changes in LTS release 4.6.2:
- build: it is now possible to build the documentation from the release tarball
- buffer: Buffer.alloc() will no longer incorrectly return a zero filled buffer when an encoding is passed
- deps/npm: upgrade npm in LTS to 2.15.11
- repl: enable tab completion for global properties
- url: url.format() will now encode all '#' in search
Список пакетов
openSUSE Leap 42.1
Ссылки
- E-Mail link for openSUSE-SU-2017:0527-1
- SUSE Security Ratings
Описание
There is a carry propagating bug in the Broadwell-specific Montgomery multiplication procedure in OpenSSL 1.0.2 and 1.1.0 before 1.1.0c that handles input lengths divisible by, but longer than 256 bits. Analysis suggests that attacks against RSA, DSA and DH private keys are impossible. This is because the subroutine in question is not used in operations with the private key itself and an input of the attacker's direct choice. Otherwise the bug can manifest itself as transient authentication and key negotiation failures or reproducible erroneous outcome of public-key operations with specially crafted input. Among EC algorithms only Brainpool P-512 curves are affected and one presumably can attack ECDH key negotiation. Impact was not analyzed in detail, because pre-requisites for attack are considered unlikely. Namely multiple clients have to choose the curve in question and the server has to share the private key among them, neither of which is default behaviour. Even then only clients that chose the curve will be affected.
Затронутые продукты
Ссылки
- CVE-2016-7055
- SUSE Bug 1009528
- SUSE Bug 1021641
- SUSE Bug 1025354
Описание
If an SSL/TLS server or client is running on a 32-bit host, and a specific cipher is being used, then a truncated packet can cause that server or client to perform an out-of-bounds read, usually resulting in a crash. For OpenSSL 1.1.0, the crash can be triggered when using CHACHA20/POLY1305; users should upgrade to 1.1.0d. For Openssl 1.0.2, the crash can be triggered when using RC4-MD5; users who have not disabled that algorithm should update to 1.0.2k.
Затронутые продукты
Ссылки
- CVE-2017-3731
- SUSE Bug 1021641
- SUSE Bug 1022085
- SUSE Bug 1025354
- SUSE Bug 1064118
- SUSE Bug 1064119
Описание
There is a carry propagating bug in the x86_64 Montgomery squaring procedure in OpenSSL 1.0.2 before 1.0.2k and 1.1.0 before 1.1.0d. No EC algorithms are affected. Analysis suggests that attacks against RSA and DSA as a result of this defect would be very difficult to perform and are not believed likely. Attacks against DH are considered just feasible (although very difficult) because most of the work necessary to deduce information about a private key may be performed offline. The amount of resources required for such an attack would be very significant and likely only accessible to a limited number of attackers. An attacker would additionally need online access to an unpatched system using the target private key in a scenario with persistent DH parameters and a private key that is shared between multiple clients. For example this can occur by default in OpenSSL DHE based SSL/TLS ciphersuites. Note: This issue is very similar to CVE-2015-3193 but must be treated as a separate problem.
Затронутые продукты
Ссылки
- CVE-2017-3732
- SUSE Bug 1021641
- SUSE Bug 1022086
- SUSE Bug 1025354
- SUSE Bug 1049418
- SUSE Bug 1049421
- SUSE Bug 1049422
- SUSE Bug 1066242
- SUSE Bug 1071906
- SUSE Bug 957814