Skip to content
Fencer Intel
low —

GHSA-7fjp-g4m7-fx23 json

User (Encrypted) Password Field Being Serialised

published 5y ago modified last yr.

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

### Impact Leaking Password field during serialisation of the User model. Password is in the encrypted form but if User model is requested in json or array form the value is printed.

### Patches Issue has been patched in version 0.3.7-beta and onwards.

### Workarounds Add the 'password' field to the Users model file in the hidden array:

```php

/** * The attributes that should be hidden for arrays. * * @var array */ protected $hidden = [ 'remember_token', 'password', ]; ```

### For more information If you have any questions or comments about this advisory: * Open an issue in [pwweb/laravel-core](https://github.com/pwweb/laravel-core) * Email us at [security@pw-websolutions.com](mailto:security@pw-websolutions.com)

Patch / fix

  • packagist pwweb/laravel-core 0.3.7-beta

Is GHSA-7fjp-g4m7-fx23 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
packagist pwweb/laravel-core
<0.3.7-beta
0.3.7-beta

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.