search

rubymonsters / fiftypercent

50 percent, that's half of it. Women make up roughly half of the world's population. But they rarely make up half the participant on discussion panels, on the microphone, in talk show or conferences. "50 Prozent" documents, how many women* there are.
https://50prozent.speakerinnen.org/en/
9 stars 2 forks source link

[Security] Bump puma from 3.12.0 to 3.12.4 #67

Closed dependabot-preview[bot] closed 4 years ago

dependabot-preview[bot] commented 4 years ago

Bumps puma from 3.12.0 to 3.12.4. This update includes security fixes.

Vulnerabilities fixed

Sourced from The Ruby Advisory Database.

HTTP Response Splitting vulnerability in puma If an application using Puma allows untrusted input in a response header, an attacker can use newline characters (i.e. CR, LF) to end the header and inject malicious content, such as additional headers or an entirely new response body. This vulnerability is known as HTTP Response Splitting.

While not an attack in itself, response splitting is a vector for several other attacks, such as cross-site scripting (XSS).

Patched versions: ~> 3.12.4; >= 4.3.3 Unaffected versions: none

Sourced from The GitHub Security Advisory Database.

Moderate severity vulnerability that affects puma In Puma (RubyGem) before 4.3.2 and 3.12.2, if an application using Puma allows untrusted input in a response header, an attacker can use newline characters (i.e. CR, LF or/r, /n) to end the header and inject malicious content, such as additional headers or an entirely new response body. This vulnerability is known as HTTP Response Splitting.

While not an attack in itself, response splitting is a vector for several other attacks, such as cross-site scripting (XSS).

This is related to CVE-2019-16254, which fixed this vulnerability for the WEBrick Ruby web server.

This has been fixed in versions 4.3.2 and 3.12.3 by checking all headers for line endings and rejecting headers with those characters.

Affected versions: < 3.12.3

Sourced from The Ruby Advisory Database.

Keepalive thread overload/DoS in puma A poorly-behaved client could use keepalive requests to monopolize Puma's reactor and create a denial of service attack.

If more keepalive connections to Puma are opened than there are threads available, additional connections will wait permanently if the attacker sends requests frequently enough.

Patched versions: ~> 3.12.2; >= 4.3.1 Unaffected versions: none

Sourced from The GitHub Security Advisory Database.

Moderate severity vulnerability that affects puma

Keepalive thread overload/DoS

Impact

A poorly-behaved client could use keepalive requests to monopolize Puma's reactor and create a denial of service attack.

If more keepalive connections to Puma are opened than there are threads available, additional connections will wait permanently if the attacker sends requests frequently enough.

Patches

This vulnerability is patched in Puma 4.3.1 and 3.12.2.

Workarounds

Reverse proxies in front of Puma could be configured to always allow less than X keepalive connections to a Puma cluster or process, where X is the number of threads configured in Puma's thread pool.

For more information

If you have any questions or comments about this advisory:

... (truncated)

Affected versions: < 3.12.2

Release notes

Sourced from puma's releases.

v3.12.1

Changelog

Sourced from puma's changelog.

4.3.3 and 3.12.4 / 2020-02-28

  • Bugfixes
    • Fix: Fixes a problem where we weren't splitting headers correctly on newlines (#2132)
  • Security
    • Fix: Prevent HTTP Response splitting via CR in early hints.

4.3.2 and 3.12.3 / 2020-02-27

  • Security
    • Fix: Prevent HTTP Response splitting via CR/LF in header values. CVE-2020-5247.

4.3.1 and 3.12.2 / 2019-12-05

  • Security
    • Fix: a poorly-behaved client could use keepalive requests to monopolize Puma's reactor and create a denial of service attack. CVE-2019-16770.

4.3.0 / 2019-11-07

  • Features

    • Strip whitespace at end of HTTP headers (#2010)
    • Optimize HTTP parser for JRuby (#2012)
    • Add SSL support for the control app and cli (#2046, #2052)

  • Bugfixes

    • Fix Errno::EINVAL when SSL is enabled and browser rejects cert (#1564)
    • Fix pumactl defaulting puma to development if an environment was not specified (#2035)
    • Fix closing file stream when reading pid from pidfile (#2048)
    • Fix a typo in configuration option --extra_runtime_dependencies (#2050)

4.2.1 / 2019-10-07

  • 3 bugfixes
    • Fix socket activation of systemd (pre-existing) unix binder files (#1842, #1988)
    • Deal with multiple calls to bind correctly (#1986, #1994, #2006)
    • Accepts symbols for verify_mode (#1222)

4.2.0 / 2019-09-23

  • 6 features
    • Pumactl has a new -e environment option and reads config/puma/<environment>.rb config files (#1885)
    • Semicolons are now allowed in URL paths (MRI only), useful for Angular or Redmine (#1934)
    • Allow extra dependencies to be defined when using prune_bundler (#1105)
    • Puma now reports the correct port when binding to port 0, also reports other listeners when binding to localhost (#1786)
    • Sending SIGINFO to any Puma worker now prints currently active threads and their backtraces (#1320)
    • Puma threads all now have their name set on Ruby 2.3+ (#1968)
  • 4 bugfixes
    • Fix some misbehavior with phased restart and externally SIGTERMed workers (#1908, #1952)
    • Fix socket closing on error (#1941)
    • Removed unnecessary SIGINT trap for JRuby that caused some race conditions (#1961)
    • Fix socket files being left around after process stopped (#1970)
... (truncated)
Commits


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Pull request limits (per update run and/or open at any time) - Automerge options (never/patch/minor, and dev/runtime dependencies) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired)
dependabot-preview[bot] commented 4 years ago

Superseded by #70.