CVE-2016-9125

Revive Adserver before 3.2.3 suffers from session fixation, by allowing arbitrary session identifiers to be forced and, at the same time, by not invalidating the existing session upon a successful authentication. Under some circumstances, that could have been an opportunity for an attacker to steal an authenticated session.
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/4910365631eabbb208961c36149f41cc8159fb39 - Issue Tracking, Patch, Third Party Advisory () https://github.com/revive-adserver/revive-adserver/commit/4910365631eabbb208961c36149f41cc8159fb39 - Issue Tracking, Patch, Third Party Advisory
References () https://hackerone.com/reports/93809 - Permissions Required () https://hackerone.com/reports/93809 - Permissions Required
References () https://hackerone.com/reports/93813 - Permissions Required () https://hackerone.com/reports/93813 - 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-9125

Mitre link : CVE-2016-9125

CVE.ORG link : CVE-2016-9125


JSON object : View

Products Affected

revive-adserver

  • revive_adserver
CWE
CWE-384

Session Fixation