{"id":"CVE-2016-9129","aliases":["EUVD-2016-9946","GHSA-43m8-rg5f-9pr8"],"status":"published","title":"Revive Adserver before 3.2.3 suffers from Information Exposure Through Discrepancy. It is...","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.","severity":{"version":"3.0","score":5.3,"vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","level":"medium","assessor":"primary","from":"nvd"},"epss":{"day":"2026-11-07","score":0.0143,"percentile":0.73178,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":false},"cwes":["CWE-200","CWE-203"],"published":"2017-03-28T02:46:00Z","modified":"2026-10-20T10:48:04Z","products":[{"vendor":"revive-adserver","product":"revive_adserver"}],"references":[{"url":"https://hackerone.com/reports/98612","tags":["x_refsource_MISC","x_transferred","Permissions Required","report"]},{"url":"https://github.com/revive-adserver/revive-adserver/commit/38223a841190bebd7a137c7bed84fbbcb2b0c2a5","tags":["x_refsource_MISC","x_transferred","Issue Tracking","Patch","Third Party Advisory","fix"]},{"url":"https://www.revive-adserver.com/security/revive-sa-2016-001/","tags":["x_refsource_MISC","x_transferred","Patch","Vendor Advisory","fix"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2016-9129"},{"url":"https://www.revive-adserver.com/security/revive-sa-2016-001"},{"url":"https://github.com/advisories/GHSA-43m8-rg5f-9pr8"}],"sources":{"cve":[{"id":"CVE-2016-9129","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.","status":"published","published":"2017-03-28T02:46:00Z","modified":"2024-08-06T02:42:10.602Z","cwes":["CWE-203"],"updated_at":"2026-11-02T14:33:31.764001Z"}],"euvd":[{"id":"EUVD-2016-9946","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.","status":"published","published":"2017-03-28T02:46:00Z","modified":"2024-08-06T02:42:10Z","updated_at":"2026-11-03T02:22:28.196866Z"}],"ghsa":[{"id":"GHSA-43m8-rg5f-9pr8","title":"Revive Adserver before 3.2.3 suffers from Information Exposure Through Discrepancy. It is...","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.","status":"published","published":"2022-05-13T01:38:34Z","modified":"2025-04-20T03:35:59Z","cvss":[{"version":"3.0","score":5.3,"vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","level":"medium"}],"cwes":["CWE-200","CWE-203"],"updated_at":"2026-11-02T15:01:43.480751Z"}],"nvd":[{"id":"CVE-2016-9129","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.","status":"published","published":"2017-03-28T02:59:00.527Z","modified":"2026-06-17T00:55:34.04Z","cvss":[{"version":"3.0","score":5.3,"vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","level":"medium","assessor":"primary"},{"version":"2.0","score":5,"vector":"AV:N/AC:L/Au:N/C:P/I:N/A:N","level":"medium","assessor":"primary"}],"cwes":["CWE-203","CWE-200"],"updated_at":"2026-11-02T14:03:37.238712Z"}],"osv":[{"id":"CVE-2016-9129","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.","status":"published","published":"2017-03-28T02:59:00.527Z","modified":"2026-10-20T10:48:04.606838352Z","cvss":[{"version":"3.0","score":5.3,"vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","level":"medium"}],"updated_at":"2026-11-02T15:44:03.171316Z"}]}}