pgAdmin 4 did not invalidate a user's existing sessions when their password changed, either through the user's own change password dialog or through…
pgAdmin 4 did not invalidate a user's existing sessions when their password changed, either through the user's own change password dialog or through an administrator resetting it in User Management. A session established before the change, for example on another device or by someone who had obtained the old password or a session cookie, therefore stayed logged in after the change, which is the step a user or administrator takes precisely to cut such access off. It remained usable until it expired. The fix rotates the user's session identifier (fs_uniquifier) whenever the password is changed, so every other session of that user is logged out. The session that made the change is logged in agai
Read at NIST National Vulnerability Database (CVE API 2.0)
- Vendor
- Pgadmin.Org
- Product
- pgAdmin 4
- CVSS v3.1
- 4.2 AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N
- Weakness
- CWE-613
- NVD status
- Received
Why it ranks 9 (Routine)
- CVSS v3.1 4.2 medium
- Recency: items published within 24 hours gain 15, within 72 hours 6, within 7 days 2.