CVE-2016-9129

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

Configuration 1 (hide)

cpe:2.3:a:revive-adserver:revive_adserver:*:*:*:*:*:*:*:*

History

21 Nov 2024, 03:00

Type Values Removed Values Added
References () https://github.com/revive-adserver/revive-adserver/commit/38223a841190bebd7a137c7bed84fbbcb2b0c2a5 - Issue Tracking, Patch, Third Party Advisory () https://github.com/revive-adserver/revive-adserver/commit/38223a841190bebd7a137c7bed84fbbcb2b0c2a5 - Issue Tracking, Patch, Third Party Advisory
References () https://hackerone.com/reports/98612 - Permissions Required () https://hackerone.com/reports/98612 - Permissions Required
References () https://www.revive-adserver.com/security/revive-sa-2016-001/ - Patch, Vendor Advisory () https://www.revive-adserver.com/security/revive-sa-2016-001/ - Patch, Vendor Advisory

Information

Published : 2017-03-28 02:59

Updated : 2024-11-21 03:00


NVD link : CVE-2016-9129

Mitre link : CVE-2016-9129

CVE.ORG link : CVE-2016-9129


JSON object : View

Products Affected

revive-adserver

  • revive_adserver
CWE
CWE-203

Observable Discrepancy

CWE-200

Exposure of Sensitive Information to an Unauthorized Actor