Description
Revive Adserver before 3.2.3 suffers from Improper Restriction of Excessive Authentication Attempts. The login page of Revive Adserver is vulnerable to password-guessing attacks. An account lockdown feature was considered, but rejected to avoid introducing service disruptions to regular users during such attacks. A random delay has instead been introduced as a countermeasure in case of password failures, along with a system to discourage parallel brute forcing. These systems will effectively allow the valid users to log in to the adserver, even while an attack is in progress.
Metrics
CVSS 3.0 9.8/10
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HWeakness enumeration
Affected software
| Vendor | Product | Versions |
|---|---|---|
| n/a | Revive Adserver All versions before 3.2.3 | Revive Adserver All versions before 3.2.3 |
References
- https://github.com/revive-adserver/revive-adserver/commit/847941390f5b3310d51b07c92ec91cc1f4cc82c9Issue Tracking, Patch, Third Party Advisory
- https://hackerone.com/reports/96115Permissions Required
- https://www.revive-adserver.com/security/revive-sa-2016-001/Patch, Vendor Advisory
- https://github.com/revive-adserver/revive-adserver/commit/847941390f5b3310d51b07c92ec91cc1f4cc82c9Issue Tracking, Patch, Third Party Advisory
- https://hackerone.com/reports/96115Permissions Required
- https://www.revive-adserver.com/security/revive-sa-2016-001/Patch, Vendor Advisory
Timeline
- Published
- Mar 28, 2017
- Last modified
- Jun 17, 2026
- NVD status
- Modified