search

asahasrabuddhe / laravel-mjml

Easily use MJML in your Laravel Blade templates!
MIT License
123 stars 51 forks source link

[Security] Bump laravel/framework from 6.18.13 to 6.20.27 #106

Closed dependabot-preview[bot] closed 3 years ago

dependabot-preview[bot] commented 3 years ago

Bumps laravel/framework from 6.18.13 to 6.20.27. This update includes security fixes.

Vulnerabilities fixed

Sourced from The PHP Security Advisories Database.

Guard bypass in Eloquent models

Affected versions: >=5.5.0, =7.0.0, <7.23.2

Sourced from The PHP Security Advisories Database.

RCE vulnerability in "cookie" session driver

Affected versions: >=5.5.0, =7.0.0, <7.22.4

Sourced from The PHP Security Advisories Database.

RCE vulnerability in "cookie" session driver

Affected versions: >=4.1.0, =7.0.0, <7.22.4

Sourced from The PHP Security Advisories Database.

SQL Server LIMIT / OFFSET SQL Injection

Affected versions: >=6.0.0, =8.0.0, <8.40.0

Sourced from The PHP Security Advisories Database.

Unexpected bindings in QueryBuilder

Affected versions: >=6.0.0, =8.0.0, <8.24.0

Sourced from The PHP Security Advisories Database.

Unexpected bindings in QueryBuilder

Affected versions: >=6.0.0, =8.0.0, <8.22.1

Sourced from The GitHub Security Advisory Database.

Unexpected database bindings This is a follow-up to the previous security advisory (GHSA-3p32-j457-pg5x) which addresses a few additional edge cases.

If a request is crafted where a field that is normally a non-array value is an array, and that input is not validated or cast to its expected type before being passed to the query builder, an unexpected number of query bindings can be added to the query. In some situations, this will simply lead to no results being returned by the query builder; however, it is possible certain queries could be affected in a way that causes the query to return unexpected results.

Affected versions: < 6.20.14

Sourced from The GitHub Security Advisory Database.

Query Binding Exploitation

Description

Laravel versions <6.20.12, <7.30.3 & <8.22.1 contain a query binding exploitation.

If a request is crafted where a field that is normally a non-array value is an array, and that input is not validated or cast to its expected type before being passed to the query builder, an unexpected number of query bindings can be added to the query. In some situations, this will simply lead to no results being returned by the query builder; however, it is possible certain queries could be affected in a way that causes the query to return unexpected results.

Affected versions: < 6.20.12

Sourced from The GitHub Security Advisory Database.

Improper Input Validation in Laravel An issue was discovered in Laravel before 6.18.35 and 7.x before 7.24.0. The $guarded property is mishandled in some situations involving requests with JSON column nesting expressions.

Affected versions: < 6.18.35

Sourced from The GitHub Security Advisory Database.

SQL Server LIMIT / OFFSET SQL Injection in laravel/framework and illuminate/database

Impact

Those using SQL Server with Laravel and allowing user input to be passed directly to the limit and offset functions are vulnerable to SQL injection. Other database drivers such as MySQL and Postgres are not affected by this vulnerability.

Patches

This problem has been patched on Laravel versions 6.20.26 and 8.40.0.

Workarounds

You may workaround this vulnerability by ensuring that only integers are passed to the limit and offset functions, as well as the skip and take functions.

Affected versions: < 6.20.26

Release notes

Sourced from laravel/framework's releases.

v6.20.27

Added

  • Support mass assignment to SQL Server views (#37307)

Fixed

  • Fixed Illuminate\Database\Query\Builder::offset() with non numbers $value (#37164)
  • Fixed unless rules (#37291)

Changed

  • Allow reporting reportable exceptions with the default logger (#37235)

v6.20.26

Fixed

  • Fixed Cache store with a name other than 'dynamodb' (#37145)

Changed

  • Some cast to int in Illuminate\Database\Query\Grammars\SqlServerGrammar (09bf145)

v6.20.25

Fixed

v6.20.24

Fixed

  • Fixed required_if boolean validation (#36969)

v6.20.23

Added

  • Added strings to the DetectsLostConnections.php (4210258)

v6.20.22

Fixed

  • Fixed setting DynamoDB credentials (#36822)

v6.20.21

Added

  • Added support of DynamoDB in CI suite (#36749)
  • Support username parameter for predis (#36762)

Changed

  • Use qualified column names in pivot query (#36720)

v6.20.20

Added

  • Added WSREP communication link failure for lost connection detection (#36668)

Fixed

... (truncated)

Changelog

Sourced from laravel/framework's changelog.

v6.20.27 (2021-05-11)

Added

  • Support mass assignment to SQL Server views (#37307)

Fixed

  • Fixed Illuminate\Database\Query\Builder::offset() with non numbers $value (#37164)
  • Fixed unless rules (#37291)

Changed

  • Allow reporting reportable exceptions with the default logger (#37235)

v6.20.26 (2021-04-28)

Fixed

  • Fixed Cache store with a name other than 'dynamodb' (#37145)

Changed

  • Some cast to int in Illuminate\Database\Query\Grammars\SqlServerGrammar (09bf145)

v6.20.25 (2021-04-27)

Fixed

v6.20.24 (2021-04-20)

Fixed

  • Fixed required_if boolean validation (#36969)

v6.20.23 (2021-04-13)

Added

  • Added strings to the DetectsLostConnections.php (4210258)

v6.20.22 (2021-03-31)

Fixed

  • Fixed setting DynamoDB credentials (#36822)

v6.20.21 (2021-03-30)

Added

  • Added support of DynamoDB in CI suite (#36749)

... (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) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired)
dependabot-preview[bot] commented 3 years ago

Superseded by #109.