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.
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.324% probability within 30 days)
Key SSVC decision points have not yet been added.
| Link | Providers |
|---|---|
| https://hackerone.com/reports/4116433 |
|
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Stored XSS in Revive Adserver Report Date Selection Controls |
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Revive
Revive adserver |
|
| Vendors & Products |
Revive
Revive adserver |
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Stored XSS in Revive Adserver Report Date Selection Controls |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | A stored cross-site scripting vulnerability in the report date-selection controls of Revive Adserver 6.0.8 and earlier allows an unauthenticated attacker to execute JavaScript in a victim's browser by persuading them to follow a crafted report URL and complete normal reauthentication. An attacker-controlled period_preset value can be saved in the victim's session and inserted into JavaScript without appropriate encoding. The payload can execute on the initial report view and subsequent report views using the stored defaults. The issue is fixed in Revive Adserver 6.0.9 by applying JSON encoding appropriate for the JavaScript context to date-selection values. | |
| Weaknesses | CWE-79 | |
| References |
| |
| Metrics |
cvssV3_0
|