🚨 [security] [server] Update symfony/http-foundation: 4.2.2 → 4.2.12 (patch)

[depfu]

---

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-foundation (indirect, 4.2.2 → 4.2.12) · Repo · Changelog

Security Advisories 🚨

🚨 Argument injection in a MimeTypeGuesser in Symfony

An issue was discovered in Symfony 2.8.0 through 2.8.50, 3.4.0 through 3.4.34, 4.2.0 through 4.2.11, and 4.3.0 through 4.3.7. If an application passes unvalidated user input as the file for which MIME type validation should occur, then arbitrary arguments are passed to the underlying file command. This is related to symfony/http-foundation (and symfony/mime in 4.3.x).

🚨 Invalid HTTP method overrides allow possible XSS or other attacks in Symfony

In Symfony before 2.7.51, 2.8.x before 2.8.50, 3.x before 3.4.26, 4.x before 4.1.12, and 4.2.x before 4.2.7, HTTP Methods provided as verbs or using the override header may be treated as trusted input, but they are not validated, possibly causing SQL injection or XSS. This is related to symfony/http-foundation.

Commits

See the full diff on Github. The new version differs by 1 commit:

• [HttpFoundation] fix guessing mime-types of files with leading dash

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

Commits

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

• Update to Unicode 13
• Various fixes
• [mbstring] add return value to mb_parse_str (#351)
• minor #349 Use fully-qualified iconv calls in the mbstring polyfill (stof)
• Use fully-qualified iconv calls in the mbstring polyfill
• Update CHANGELOG and branch-alias
• Always accept null values on PHP 8
• Add polyfill-php81
• Update and apply CS rules
• Adjust mbstring polyfill for PHP 8
• Verify the signature of polyfills on PHP >= 8
• Drop polyfills for PHP <= 7.1 from the metapackage
• Bump minimum PHP version to 7.1
• Fix the name of arguments for PHP 8
• Update branch-alias for main + v1.19
• Fix php8 error passing too many arguments to strrchr
• Update CHANGELOG and branch-alias
• Add missing "extra.thanks" entries in composer.json
• Bump unicode data
• Fix declaring extra constants when `intl` is loaded
• Bump for 1.17.0
• Add separate checks for all polyfilled functions and constants
• Bumped branch alias
• Fix support for preloading
• Bump branch-alias
• Add link in intl idn readme
• PHP 8.0 - add fdiv() function polyfill
• [Mbstring] fix `mb_str_split()` ignoring new-line characters
• minor #199 Optimization of mb_str_split (kamil-tekiela)
• Optimization of mb_str_split
• [Uuid] Added the polyfill
• [Mbstring] fix mb_strrpos with negative offset
• bump branch-alias and update changelog
• feature #181 add new PHP 7.4 functions (IonBazan)
• add new PHP 7.4 functions
• [Mbstring ] fix mb_substr return type
• Added missing polyfill for JsonException
• Update year in license file

🗑️ 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 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)