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] [server] Update symfony/http-kernel: 4.2.2 → 4.4.50 (minor) #17

Open
wants to merge 1 commit into
base: dev
Choose a base branch
from

Conversation

depfu[bot]
Copy link

@depfu depfu bot commented Feb 1, 2023


Welcome to Depfu 👋

This is one of the first three pull requests with dependency updates we've sent your way. We tried to start with a few easy patch-level updates. Hopefully your tests will pass and you can merge this pull request without too much risk. This should give you an idea how Depfu works in general.

After you merge your first pull request, we'll send you a few more. We'll never open more than seven PRs at the same time so you're not getting overwhelmed with updates.

Let us know if you have any questions. Thanks so much for giving Depfu a try!



🚨 Your current dependencies have known security vulnerabilities 🚨

This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!


Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

↗️ symfony/http-kernel (indirect, 4.2.2 → 4.4.50) · Repo · Changelog

Security Advisories 🚨

🚨 Symfony storing cookie headers in HttpCache

Description

The Symfony HTTP cache system acts as a reverse proxy: it caches HTTP responses (including headers) and returns them to clients.

In a recent AbstractSessionListener change, the response might now contain a Set-Cookie header. If the Symfony HTTP cache system is enabled, this header might be stored and returned to some other clients. An attacker can use this vulnerability to retrieve the victim's session.

Resolution

The HttpStore constructor now takes a parameter containing a list of private headers that are removed from the HTTP response headers.
The default value for this parameter is Set-Cookie, but it can be overridden or extended by the application.

The patch for this issue is available here for branch 4.4.

Credits

We would like to thank Soner Sayakci for reporting the issue and Nicolas Grekas for fixing it.

🚨 Non-constant time comparison in UriSigner

When checking the signature of an URI (an ESI fragment URL for instance), the URISigner did not used a constant time string comparison function, resulting in a potential remote timing attack vulnerability.

🚨 Non-constant time comparison in UriSigner

When checking the signature of an URI (an ESI fragment URL for instance), the URISigner did not used a constant time string comparison function, resulting in a potential remote timing attack vulnerability.

🚨 RCE in Symfony

Description

The CachingHttpClient class from the HttpClient Symfony component relies on the HttpCache class to handle requests. HttpCache uses internal headers like X-Body-Eval and X-Body-File to control the restoration of cached responses. The class was initially written with surrogate caching and ESI support in mind (all HTTP calls come from a trusted backend in that scenario). But when used by CachingHttpClient and if an attacker can control the response for a request being made by the CachingHttpClient, remote code execution is possible.

Resolution

HTTP headers designed for internal use in HttpCache are now stripped from remote responses before being passed to HttpCache.

The patch for this issue is available here for the 4.4 branch.

Credits

I would like to thank Matthias Pigulla (webfactory GmbH) for reporting and fixing the issue.

Release Notes

Too many releases to show here. View the full release notes.

↗️ phpdocumentor/reflection-common (indirect, 1.0.1 → 2.1.0) · Repo

Commits

See the full diff on Github. The new version differs by 75 commits:

↗️ phpdocumentor/reflection-docblock (indirect, 4.3.0 → 4.3.4) · Repo

Commits

See the full diff on Github. The new version differs by 33 commits:

↗️ phpdocumentor/type-resolver (indirect, 0.4.0 → 1.0.1) · Repo

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ psr/log (indirect, 1.1.0 → 1.1.4) · Repo

Release Notes

1.1.4

  • Fixed type annotations on AbstractLogger and LoggerAwareTrait

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 23 commits:

↗️ symfony/debug (indirect, 4.2.2 → 4.4.44) · Repo · Changelog

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ symfony/event-dispatcher (indirect, 4.2.2 → 4.4.44) · Repo · Changelog

Commits

See the full diff on Github. The new version differs by 2 commits:

↗️ symfony/http-foundation (indirect, 4.2.2 → 4.4.49) · Repo · Changelog

↗️ symfony/polyfill-ctype (indirect, 1.10.0 → 1.27.0) · Repo

Commits

See the full diff on Github. The new version differs by 24 commits:

↗️ symfony/polyfill-mbstring (indirect, 1.10.0 → 1.27.0) · Repo

Commits

See the full diff on Github. The new version differs by 47 commits:

↗️ symfony/polyfill-php72 (indirect, 1.10.0 → 1.27.0) · Repo

Commits

See the full diff on Github. The new version differs by 30 commits:

↗️ symfony/var-dumper (indirect, 4.2.2 → 4.4.47) · Repo · Changelog

↗️ webmozart/assert (indirect, 1.4.0 → 1.9.1) · Repo · Changelog

Commits

See the full diff on Github. The new version differs by 75 commits:

🆕 symfony/error-handler (added, 4.4.44)

🆕 symfony/event-dispatcher-contracts (added, 1.1.13)

🆕 symfony/http-client-contracts (added, 1.1.13)

🆕 symfony/mime (added, 4.4.47)

🆕 symfony/polyfill-intl-idn (added, 1.27.0)

🆕 symfony/polyfill-intl-normalizer (added, 1.27.0)

🆕 symfony/polyfill-php73 (added, 1.27.0)

🆕 symfony/polyfill-php80 (added, 1.27.0)

🗑️ laravel/envoy (removed)

🗑️ nategood/httpful (removed)


👉 No CI detected

You don't seem to have any Continuous Integration service set up!

Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.

This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:

  • Circle CI, Semaphore and Travis-CI are all excellent options.
  • If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github.
  • If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with depfu/.

Depfu Status

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands
@​depfu rebase
Rebases against your default branch and redoes this update
@​depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@​depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@​depfu close
Closes this PR and deletes the branch
@​depfu reopen
Restores the branch and reopens this PR (if it's closed)
@​depfu pause
Ignores all future updates for this dependency and closes this PR
@​depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@​depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants