CVE-2018-7159

The HTTP parser in all current versions of Node.js ignores spaces in the Content-Length header, allowing input such as Content-Length: 1 2 to be interpreted as having a value of 12. The HTTP specification does not allow for spaces in the Content-Length value and the Node.js HTTP parser has been brought into line on this particular difference. The security risk of this flaw to Node.js users is considered to be VERY LOW as it is difficult, and may be impossible, to craft an attack that makes use of this flaw in a way that could not already be achieved by supplying an incorrect value for Content-Length. Vulnerabilities may exist in user-code that make incorrect assumptions about the potential accuracy of this value compared to the actual length of the data supplied. Node.js users crafting lower-level HTTP utilities are advised to re-check the length of any input supplied after parsing is complete.

The HTTP parser in all current versions of Node.js ignores spaces in the Content-Length header, allowing input such as Content-Length: 1 2 to be interpreted as having a value of 12. The HTTP specification does not allow for spaces in the Content-Length value and the Node.js HTTP parser has been brought into line on this particular difference. The security risk of this flaw to Node.js users is considered to be VERY LOW as it is difficult, and may be impossible, to craft an attack that makes use of this flaw in a way that could not already be achieved by supplying an incorrect value for Content-Length. Vulnerabilities may exist in user-code that make incorrect assumptions about the potential accuracy of this value compared to the actual length of the data supplied. Node.js users crafting lower-level HTTP utilities are advised to re-check the length of any input supplied after parsing is complete.

The HTTP parser in all current versions of Node.js ignores spaces in the Content-Length header, allowing input such as Content-Length: 1 2 to be interpreted as having a value of 12. The HTTP specification does not allow for spaces in the Content-Length value and the Node.js HTTP parser has been brought into line on this particular difference. The security risk of this flaw to Node.js users is considered to be VERY LOW as it is difficult, and may be impossible, to craft an attack that makes use of this flaw in a way that could not already be achieved by supplying an incorrect value for Content-Length. Vulnerabilities may exist in user-code that make incorrect assumptions about the potential accuracy of this value compared to the actual length of the data supplied. Node.js users crafting lower-level HTTP utilities are advised to re-check the length of any input supplied after parsing is complete.

This update provides nodejs v6.17.1 fixing at least the following security issues:

The c-ares function ares_parse_naptr_reply(), which is used for parsing NAPTR responses, could be triggered to read memory outside of the given input buffer (CVE-2017-1000381)

Fix for 'path' module regular expression denial of service (CVE-2018-7158)

Reject spaces in HTTP Content-Length header values (CVE-2018-7159)

Fix for inspector DNS rebinding vulnerability (CVE-2018-7160)

buffer: Fixes Denial of Service vulnerability where calling Buffer.fill() could hang (CVE-2018-7167)

buffer: Fix out-of-bounds (OOB) write in Buffer.write() for UCS-2 encoding (CVE-2018-12115)

Node.js: HTTP request splitting (CVE-2018-12116)

Node.js: Debugger port 5858 listens on any interface by default (CVE-2018-12120)

Node.js: Denial of Service with large HTTP headers (CVE-2018-12121)

Node.js: Slowloris HTTP Denial of Service (CVE-2018-12122)

Node.js: Hostname spoofing in URL parser for javascript protocol (CVE-2018-12123)

Node.js: Slowloris HTTP Denial of Service with keep-alive (CVE-2019-5737)

Node.js: Denial of Service with keep-alive HTTP connections (CVE-2019-5739)

For other fixes in this update, see the referenced release logs.

This update for nodejs4 fixes the following issues:

• Fix some node-gyp permissions

• New upstream maintenance 4.9.1:

  • Security fixes:
    • CVE-2018-7158: Fix for 'path' module regular expression denial of service (bsc#1087459)
    • CVE-2018-7159: Reject spaces in HTTP Content-Length header values (bsc#1087453)
  • Upgrade to OpenSSL 1.0.2o
  • deps: reject interior blanks in Content-Length
  • deps: upgrade http-parser to v2.8.0

• remove any old manpage files in %pre from before update-alternatives were used to manage symlinks to these manpages.

• Add Recommends and BuildRequire on python2 for npm. node-gyp requires this old version of python for now. This is only needed for binary modules.

• even on recent codestreams there is no binutils gold on s390 only on s390x

• Enable CI tests in %check target

This update for nodejs6 fixes the following issues:

• Fix some node-gyp permissions

• New upstream LTS release 6.14.1:

  • Security fixes:
    • CVE-2018-7160: Fix for inspector DNS rebinding vulnerability (bsc#1087463)
    • CVE-2018-7158: Fix for 'path' module regular expression denial of service (bsc#1087459)
    • CVE-2018-7159: Reject spaces in HTTP Content-Length header values (bsc#1087453)

• New upstream LTS release 6.13.1:

  • http,tls: better support for IPv6 addresses
  • console: added console.count() and console.clear()
  • crypto:
    • expose ECDH class
    • added cypto.randomFill() and crypto.randomFillSync()
    • warn on invalid authentication tag length
  • deps: upgrade libuv to 1.16.1
  • dgram: added socket.setMulticastInterface()
  • http: add agent.keepSocketAlive and agent.reuseSocket as to allow overridable keep-alive behavior of Agent
  • lib: return this from net.Socket.end()
  • module: add builtinModules api that provides list of all builtin modules in Node
  • net: return this from getConnections()
  • promises: more robust stringification for unhandled rejections
  • repl: improve require() autocompletion
  • src:
    • add openssl-system-ca-path configure option
    • add --use-bundled-ca --use-openssl-ca check
    • add process.ppid
  • tls: accept lookup option for tls.connect()
  • tools,build: a new macOS installer!
  • url: WHATWG URL api support
  • util: add %i and %f formatting specifiers

• remove any old manpage files in %pre from before update-alternatives were used to manage symlinks to these manpages.

• Add Recommends and BuildRequire on python2 for npm. node-gyp requires this old version of python for now. This is only needed for binary modules.

• even on recent codestreams there is no binutils gold on s390 only on s390x

• New upstream LTS release 6.12.3:

  • v8: profiler-related fixes
  • mostly documentation and test related changes

• Enable CI tests in %check target

This update contains the Mozilla Firefox ESR 68.2 release.

Mozilla Firefox was updated to ESR 68.2 release:

• Enterprise: New administrative policies were added. More information and templates are available at the Policy Templates page.

• Various security fixes: MFSA 2019-33 (bsc#1154738)

  • CVE-2019-15903: Heap overflow in expat library in XML_GetCurrentLineNumber
  • CVE-2019-11757: Use-after-free when creating index updates in IndexedDB
  • CVE-2019-11758: Potentially exploitable crash due to 360 Total Security
  • CVE-2019-11759: Stack buffer overflow in HKDF output
  • CVE-2019-11760: Stack buffer overflow in WebRTC networking
  • CVE-2019-11761: Unintended access to a privileged JSONView object
  • CVE-2019-11762: document.domain-based origin isolation has same-origin- property violation
  • CVE-2019-11763: Incorrect HTML parsing results in XSS bypass technique
  • CVE-2019-11764: Memory safety bugs fixed in Firefox 70 and Firefox ESR 68.2

Other Issues resolved:

• [bsc#1104841] Newer versions of firefox have a dependency on GLIBCXX_3.4.20
• [bsc#1074235] MozillaFirefox: background tab crash reports sent inadvertently without user opt-in
• [bsc#1043008] Firefox hangs randomly when browsing and scrolling
• [bsc#1025108] Firefox stops loading page until mouse is moved
• [bsc#905528] Firefox malfunctions due to broken omni.ja archives