Ten security advisories for Faye

Today the Faye project is publishing ten security advisories affecting the Faye pub/sub server as a whole, as well as the libraries that make up its WebSocket stack. Patches for all these vulnerabilities have already been published. Since historically there has been some confusion caused by security audit tools mixing up different versions of the software, I’d like to make it clear here which versions you should be upgrading to.

If you are using the Node.js versions of any of these packages, the patched releases are:

  • faye: v1.5.0
  • faye-websocket: v0.12.0
  • websocket-driver: v0.8.0
  • websocket-extensions: v0.2.0
  • permessage-deflate: v0.2.0

If you are using the Ruby versions of these packages the patched releases are:

  • faye: v1.5.0
  • faye-websocket: v0.13.0
  • websocket-driver: v0.9.0
  • websocket-extensions: v0.2.0
  • permessage_deflate: v0.2.0

The advisories cover seven distinct flaws, all of which affect the Node.js versions, and only some of which affect Ruby. I will list these flaws below, with a link to the relevant advisory for each version:

  1. Server crash triggered by GET request with a specific path
  2. Memory exhaustion caused by uncapped POST request bodies
  3. Memory leak in static file server may lead to resource exhaustion
  4. Denial of service triggered by malformed Sec-WebSocket-Key1 header
  5. Message corruption and denial of service triggered by crafted client message
  6. Denial of service triggered by client sending a single pong frame
  7. Memory exhaustion triggered by message decompression

Details of all the vulnerabilities can be found on the specific advisories, but they all essentially result in denial or degradation of service, caused either by an uncaught error or unbounded memory use.

The new releases are all minor rather than patch releases because fixing some of these issues required adding new options to the API of all affected packages. All releases should be backwards compatible and straightforward to upgrade; if they are not then we would consider that a bug and you should report it as such.

My thanks to GitHub users samuel871211, eliteaja11-dev and zachariah-mithani for reporting these vulnerabilities.