CVE-2016-9127
Revive Adserver before 3.2.3 suffers from Cross-Site Request Forgery (CSRF).
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (0.76%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
Description
Revive Adserver before 3.2.3 suffers from Cross-Site Request Forgery (CSRF). The password recovery form in Revive Adserver is vulnerable to CSRF attacks. This vulnerability could be exploited to send a large number of password recovery emails to the registered users, especially in conjunction with a bug that caused recovery emails to be sent to all the users at once. Both issues have been fixed.
- CVSS 3.0
- 8.8 HIGHCVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
- EPSS
- 0.76% probability · 53th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-352
- Affected
- revive-adserver/revive adserver
- Source
- support@hackerone.com
References
- https://github.com/revive-adserver/revive-adserver/commit/3aaebcc765797d2c684e031f2836e0a69d6b7bc2Issue Tracking, Patch, Third Party Advisory
- https://hackerone.com/reports/99452Permissions Required
- https://www.revive-adserver.com/security/revive-sa-2016-001/Patch, Vendor Advisory
- https://github.com/revive-adserver/revive-adserver/commit/3aaebcc765797d2c684e031f2836e0a69d6b7bc2Issue Tracking, Patch, Third Party Advisory
- https://hackerone.com/reports/99452Permissions Required
- https://www.revive-adserver.com/security/revive-sa-2016-001/Patch, Vendor Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.