Psono Server CE && EE versions 4.0.33 through 7.2.3 compared the request path for the bulk-secret-read endpoint with a hard-coded unprefixed path. In deployments configured with URL_PREFIX, the comparison failed and the POST request was authorized using write scope instead of read scope. An authenticated remote attacker with an unusual read-disabled, write-enabled API key could therefore retrieve encrypted secret data and nonces through the prefixed bulk-secret-read endpoint despite lacking read permission.
The default configuration without URL_PREFIX was not affected.
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
Low
Partial data leak
Integrity
None
No 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/permiss…
fdf66990-8419-4c8c-8848-ec15d75773b4
https://gitlab.com/esaqa/psono/psono-server/-/commit/5638d4be806af7d1dea03f7cad…
fdf66990-8419-4c8c-8848-ec15d75773b4
https://gitlab.com/esaqa/psono/psono-server/-/releases/v7.2.4
fdf66990-8419-4c8c-8848-ec15d75773b4