Zenitel Connect pREST API adopts arbitrary PostgreSQL role from unvalidated JWT sub claim
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Zenitel | Zenitel Connect | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Zenitel | Zenitel Connect |
|
Vendor Solution
Upgrade to version 1.11.0
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.195% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Zenitel
Zenitel zenitel Connect |
|
| Vendors & Products |
Zenitel
Zenitel zenitel Connect |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | The pREST database REST API in Zenitel Connect firmware before 1.11.0 signs and verifies JWTs with the platform CA private key, which is stored on a data volume shared between containers, and sets the PostgreSQL session role from the unvalidated sub claim of each request while connected to the database as the "postgres" superuser, which allows local attackers who can read the platform CA private key from the container filesystem to execute database operations as the PostgreSQL superuser, including reading the master encryption key and password hashes, via a forged JWT with sub=postgres sent to the pREST API. | |
| Title | Zenitel Connect pREST API adopts arbitrary PostgreSQL role from unvalidated JWT sub claim | |
| Weaknesses | CWE-250 CWE-266 CWE-653 |
|
| References |
| |
| Metrics |
cvssV4_0
|