Device-code claim permits restricted token escalation in Psono Server
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 7.2.4
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Psono Server, the backend component of the Psono password manager, is affected. An authenticated attacker with a restricted API key session can exploit a flaw in device-code claiming to obtain a full read-write session that lasts up to a year, bypassing the original token's scope and lifetime limits.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
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.
Timeline
- CVE published
- First seen by cve.now
- Record last updated
Affected versions
- esaqa GmbH Psono
From 5.3.5 · fixed in 7.2.4