NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · Composer (PHP)

GHSA-44pg-c29v-hp6r: Laravel Guard bypass in Eloquent models

medium

In laravel releases before 6.18.34 and 7.23.2. It was possible to mass assign Eloquent attributes that included the model's table name: When doing so, Eloquent would remove the table name from the attribute for you. This was a "convenience" feature of Eloquent and was not documented. However, when paired with validation, this can lead to unexpected and unvalidated values being saved to the database.

Published May 15, 2024

Affected packages

laravel/framework

Ecosystem
Composer (PHP)
Affected
>= 5.5.0, <= 5.5.49
Fixed in
No patched version yet
Check
composer show laravel/framework

laravel/framework

Ecosystem
Composer (PHP)
Affected
>= 6.0.0, < 6.18.34
Fixed in
6.18.34
Check
composer show laravel/framework

laravel/framework

Ecosystem
Composer (PHP)
Affected
>= 7.0.0, < 7.23.2
Fixed in
7.23.2
Check
composer show laravel/framework

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

In laravel releases before 6.18.34 and 7.23.2. It was possible to mass assign Eloquent attributes that included the model's table name:

$model->fill(['users.name' => 'Taylor']);

When doing so, Eloquent would remove the table name from the attribute for you. This was a "convenience" feature of Eloquent and was not documented.

However, when paired with validation, this can lead to unexpected and unvalidated values being saved to the database. For this reason, we have removed the automatic stripping of table names from mass-asignment operations so that the attributes go through the typical "fillable" / "guarded" logic. Any attributes containing table names that are not explicitly declared as fillable will be discarded.

This security release will be a breaking change for applications that were relying on the undocumented table name stripping during mass assignment. Since this feature was relatively unknown and undocumented, we expect the vast majority of Laravel applications to be able to upgrade without issues.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More Composer (PHP) vulnerabilities

All Composer (PHP) entries