URL prefix handling permits API key read-scope bypass in Psono Server
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| esaqa GmbH | Psono | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Esaqa | Psono |
|
Vendor Solution
Upgrade to Psono Server 7.2.4 or later.
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.323% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Esaqa
Esaqa psono |
|
| Vendors & Products |
Esaqa
Esaqa psono |
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | URL prefix handling permits API key read-scope bypass in Psono Server | |
| Weaknesses | CWE-863 | |
| References |
|
|
| Metrics |
cvssV3_1
|