CVE-2016-9125

moderate-risk
Published 2017-03-28

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.

Do I need to act?

~
1.1% chance of exploitation in next 30 days
EPSS score — moderate exploit probability
-
Not on CISA KEV list
No confirmed active exploitation reported to CISA
?
Patch status unknown
Check vendor advisories for fix availability and mitigation guidance
9
CVSS 9.8/10 Critical
NETWORK / LOW complexity

Affected Products (1)

Affected Vendors

Revive-Adserver

References (8)

Issue Tracking https://github.com/revive-adserver/revive-adserver/commit/4910365631eabbb208961c...
Permissions Required https://hackerone.com/reports/93809
Permissions Required https://hackerone.com/reports/93813
Patch https://www.revive-adserver.com/security/revive-sa-2016-001/
Issue Tracking https://github.com/revive-adserver/revive-adserver/commit/4910365631eabbb208961c...
Permissions Required https://hackerone.com/reports/93809
Permissions Required https://hackerone.com/reports/93813
Patch https://www.revive-adserver.com/security/revive-sa-2016-001/
40
/ 100
moderate-risk
Severity 32/34 · Critical
Exploitability 3/34 · Minimal
Exposure 5/34 · Minimal