CVE-2016-9125
Last modified
CVE-2016-9125 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 2.66% chance of exploitation in the next 30 days.
Description
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Revive-Adserver | Revive Adserver | <= 3.2.2 |
References
- https://github.com/revive-adserver/revive-adserver/commit/4910365631eabbb208961c36149f41cc8159fb39Issue Tracking, Patch, Third Party Advisory
- https://hackerone.com/reports/93809Permissions Required
- https://hackerone.com/reports/93813Permissions Required
- https://www.revive-adserver.com/security/revive-sa-2016-001/Patch, Vendor Advisory
- https://github.com/revive-adserver/revive-adserver/commit/4910365631eabbb208961c36149f41cc8159fb39Issue Tracking, Patch, Third Party Advisory
- https://hackerone.com/reports/93809Permissions Required
- https://hackerone.com/reports/93813Permissions Required
- https://www.revive-adserver.com/security/revive-sa-2016-001/Patch, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2016-9125?
How severe is CVE-2016-9125?
How do I fix CVE-2016-9125?
Are you affected by CVE-2016-9125?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
