Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[security] build(deps): bump puma from 3.12.0 to 4.1.1 #159

Closed

Conversation

dependabot-preview[bot]
Copy link
Contributor

Bumps puma from 3.12.0 to 4.1.1.

Release notes

Sourced from puma's releases.

4.1.1

3 bugfixes

  • Revert our attempt to not dup STDOUT/STDERR (#1946)
  • Fix socket close on error (#1941)
  • Fix workers not shutting down correctly (#1908)

4.1.0 - Fourth and One

  • 4 features

    • Add REQUEST_PATH on parse error message (#1831)
    • You can now easily add custom log formatters with the log_formatter config option (#1816)
    • Puma.stats now provides process start times (#1844)
    • Add support for disabling TLSv1.1 (#1836)
  • 7 bugfixes

    • Fix issue where Puma was creating zombie process entries (#1887)
    • Fix bugs with line-endings and chunked encoding (#1812)
    • RACK_URL_SCHEME is now set correctly in all conditions (#1491)
    • We no longer mutate global STDOUT/STDERR, particularly the sync setting (#1837)
    • SSL read_nonblock no longer blocks (#1857)
    • Swallow connection errors when sending early hints (#1822)
    • Backtrace no longer dumped when invalid pumactl commands are run (#1863)
  • 5 other

  • 1 known issue

    • Some users are still experiencing issues surrounding socket activation and Unix sockets (#1842)

Codename: Fourth and One

why-dont-coaches-go-for-it-on-4th-down

v4.0.1

  • 2 bugfixes
    • Fix socket removed after reload - should fix problems with systemd socket activation. (#1829)
    • Add extconf tests for DTLS_method & TLS_server_method, use in minissl.rb. Should fix "undefined symbol: DTLS_method" when compiling against old OpenSSL versions. (#1832)
  • 1 other
    • Removed unnecessary RUBY_VERSION checks. (#1827)

v4.0.0 - 4 Fast 4 Furious

9 feature

  • Add support for disabling TLSv1.0 (#1562)
  • Request body read time metric (#1569)
  • Add out_of_band hook (#1648)
  • Re-implement (native) IOBuffer for JRuby (#1691)
... (truncated)
Changelog

Sourced from puma's changelog.

4.1.1 / 2019-09-05

  • 3 bugfixes
    • Revert our attempt to not dup STDOUT/STDERR (#1946)
    • Fix socket close on error (#1941)
    • Fix workers not shutting down correctly (#1908)

4.1.0 / 2019-08-08

  • 4 features

    • Add REQUEST_PATH on parse error message (#1831)
    • You can now easily add custom log formatters with the log_formatter config option (#1816)
    • Puma.stats now provides process start times (#1844)
    • Add support for disabling TLSv1.1 (#1836)
  • 7 bugfixes

    • Fix issue where Puma was creating zombie process entries (#1887)
    • Fix bugs with line-endings and chunked encoding (#1812)
    • RACK_URL_SCHEME is now set correctly in all conditions (#1491)
    • We no longer mutate global STDOUT/STDERR, particularly the sync setting (#1837)
    • SSL read_nonblock no longer blocks (#1857)
    • Swallow connection errors when sending early hints (#1822)
    • Backtrace no longer dumped when invalid pumactl commands are run (#1863)
  • 5 other

  • 1 known issue

    • Some users are still experiencing issues surrounding socket activation and Unix sockets (#1842)

4.0.1 / 2019-07-11

  • 2 bugfixes
    • Fix socket removed after reload - should fix problems with systemd socket activation. (#1829)
    • Add extconf tests for DTLS_method & TLS_server_method, use in minissl.rb. Should fix "undefined symbol: DTLS_method" when compiling against old OpenSSL versions. (#1832)
  • 1 other
    • Removed unnecessary RUBY_VERSION checks. (#1827)

4.0.0 / 2019-06-25

  • 9 features
    • Add support for disabling TLSv1.0 (#1562)
    • Request body read time metric (#1569)
    • Add out_of_band hook (#1648)
    • Re-implement (native) IOBuffer for JRuby (#1691)
    • Min worker timeout (#1716)
... (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:

  • Update frequency (including time of day and day of week)
  • Automerge options (never/patch/minor, and dev/runtime dependencies)
  • Pull request limits (per update run and/or open at any time)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

Finally, you can contact us by mentioning @dependabot.

Bumps [puma](https://github.com/puma/puma) from 3.12.0 to 4.1.1.
- [Release notes](https://github.com/puma/puma/releases)
- [Changelog](https://github.com/puma/puma/blob/master/History.md)
- [Commits](puma/puma@v3.12.0...v4.1.1)

Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
@dependabot-preview dependabot-preview bot added the dependencies Dependencies need updating label Sep 10, 2019
@coveralls
Copy link

coveralls commented Sep 10, 2019

Pull Request Test Coverage Report for Build 581

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 86.667%

Totals Coverage Status
Change from base Build 412: 0.0%
Covered Lines: 13
Relevant Lines: 15

💛 - Coveralls

@dependabot-preview
Copy link
Contributor Author

Superseded by #160.

@dependabot-preview dependabot-preview bot deleted the dependabot/bundler/develop/puma-4.1.1 branch September 23, 2019 10:19
@dependabot-preview
Copy link
Contributor Author

We've just been alerted that this update fixes a security vulnerability:

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"]

@dependabot-preview dependabot-preview bot changed the title build(deps): bump puma from 3.12.0 to 4.1.1 [security] build(deps): bump puma from 3.12.0 to 4.1.1 Feb 28, 2020
@dependabot-preview dependabot-preview bot added the security This is very important and could compromise security label Feb 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Dependencies need updating security This is very important and could compromise security
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant