Description

TREK is a collaborative travel planner. Prior to 3.0.18, early return on missing user during login flow allowed an attacker to enumerate valid user accounts via response timing discrepancy. When an email address existed in the database, the backend performed a bcrypt password comparison before returning a 401 Unauthorized, adding ~370 ms of latency. When the email did not exist, the backend returned immediately (~10 ms). This ~14× timing difference could be detected without any difference in HTTP status codes or response bodies. This vulnerability is fixed in 3.0.18.

Weaknesses 2

References 2

• gist.github.com https://gist.github.com/jubnl/c2402adf85d946c1730867aeecc794de
• github.com https://github.com/mauriceboe/TREK/security/advisories/GHSA-3552-3c98-x79r

Remediation