URL prefix handling permits API key read-scope bypass 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 (Community and Enterprise editions) is affected when deployed with a URL prefix configured. An authenticated attacker holding an API key that has write but not read permission could use it to retrieve encrypted secret data through the bulk-secret-read endpoint, bypassing the intended read restriction.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
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.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- esaqa GmbH Psono
From 4.0.33 · fixed in 7.2.4