Psono Server versions 5.3.5 through 7.2.3 used a permission class that did not enforce token write scope when claiming a device code. An authenticated remote attacker holding a restricted API key-derived session could claim an attacker-controlled device code and obtain a full read-write session valid for up to 365 days, bypassing the original token's scope and lifetime restrictions. This did not bypass two-factor authentication or directly disclose plaintext secrets.
Attack Parameters
Attack Vector
Network
Can be exploited remotely
Attack Complexity
Low
Easy to exploit
Privileges Required
Low
Basic privileges needed
User Interaction
None
No user interaction needed
Impact Assessment
Confidentiality
None
No data leak
Integrity
High
Complete data modification
Availability
None
No disruption
CVSS Vector v3.1
Weakness Type (CWE)
Vulnerable Products
esaqa gmbh:psono
References 5
https://gitlab.com/esaqa/esaqa/security-advisories/-/blob/master/advisories/CVE…
fdf66990-8419-4c8c-8848-ec15d75773b4
https://gitlab.com/esaqa/psono/psono-server
fdf66990-8419-4c8c-8848-ec15d75773b4
https://gitlab.com/esaqa/psono/psono-server/-/blob/v7.2.3/psono/restapi/views/d…
fdf66990-8419-4c8c-8848-ec15d75773b4
https://gitlab.com/esaqa/psono/psono-server/-/commit/19ed5a192c704fece1645d946b…
fdf66990-8419-4c8c-8848-ec15d75773b4
https://gitlab.com/esaqa/psono/psono-server/-/releases/v7.2.4
fdf66990-8419-4c8c-8848-ec15d75773b4