Bypass Admin‑Only Restriction via Leaked XML‑RPC Session ID in Revive Adserver
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Revive | Adserver | unaffected |
|
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Revive | Adserver |
|
No CVSS v4.0
No CVSS v3.1
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.292% probability within 30 days)
| Link | Providers |
|---|---|
| https://hackerone.com/reports/3783738 |
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Revive
Revive adserver |
|
| Vendors & Products |
Revive
Revive adserver |
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Bypass Admin‑Only Restriction via Leaked XML‑RPC Session ID in Revive Adserver |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | A bypass to the admin‑only restriction of the XML‑RPC API in Revive Adserver 6.0.7. The API response for the ox.login method returned a session ID cookie in the HTTP headers, and although the method correctly returned an error, the associated session was not invalidated. As a result, the leaked session ID could be used to perform subsequent API calls without restrictions. | |
| Weaknesses | CWE-284 | |
| References |
| |
| Metrics |
cvssV3_0
|