Update guzzle to 7.4.5 due to security vulnerabilities #461
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I updated browscap to work with guzzle 7.4.5 which is the next safe version for guzzle. Guzzle had some troubles with security lately. See https://packagist.org/packages/guzzlehttp/guzzle#7.4.5 and https://github.com/FriendsOfPHP/security-advisories/blob/master/guzzlehttp/guzzle/CVE-2022-29248.yaml for more information about it.
We are using "^7.4.3" as version constraint for guzzle which is fine in most cases. I updated the version anyway, because there can be situations, where people still receive a problematic guzzle version.
I found this while playing with security scanners in my company :).