silverstripe/framework users inadvertently passing sensitive data to LoginAttempt

published 2024-05-27 2y ago modified 2024-12-02 last yr.

cvss: 6.5; version 3.1, GitHub
cisa kev: Not listed; not in CISA's catalog
epss: —; no score, EPSS covers CVEs only
public exploits: 0; none known

All user login attempts are logged in the database in the LoginAttempt table. However, this table contains information in plain text, and may possible contain sensitive information, such as user passwords mis-typed into the username field.

In order to address this a one-way hash is applied to the Email field before being stored.

Patch / fix

fixed in 1 links 3

packagist silverstripe/framework 3.5.6, 3.6.3, 4.0.1

Is GHSA-ph62-fv59-vf9h 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

CVSS scores

assigned by	version	score	vector
GitHub	3.1	6.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

Affected packages

ecosystem	package	affected	fixed in
packagist	silverstripe/framework	>=3.5.0-rc1, <3.5.6 >=3.6.0-rc1, <3.6.3 >=4.0.0-rc1, <4.0.1	3.5.6 3.6.3 4.0.1

Classification

Weakness

CWE-311 Missing Encryption of Sensitive Data

References

Sources

GitHub Advisory GHSA-ph62-fv59-vf9h

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.