CVE-2016-9125
First published: Tue Mar 28 2017(Updated: )
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.
Credit: support@hackerone.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Revive Adserver | <=3.2.2 |
Remedy
https://github.com/revive-adserver/revive-adserver/commit/4910365631eabbb208961c36149f41cc8159fb39
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2016-9125?
CVE-2016-9125 is considered a medium severity vulnerability due to its potential to allow session fixation attacks.
How do I fix CVE-2016-9125?
To fix CVE-2016-9125, upgrade Revive Adserver to version 3.2.3 or later.
What software is affected by CVE-2016-9125?
CVE-2016-9125 affects Revive Adserver versions prior to 3.2.3.
What type of vulnerability is CVE-2016-9125?
CVE-2016-9125 is a session fixation vulnerability that allows attackers to force arbitrary session identifiers.
Can CVE-2016-9125 lead to unauthorized access?
Yes, CVE-2016-9125 can potentially allow attackers to steal session tokens and gain unauthorized access.
- agent/references
- agent/type
- agent/remedy
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/author
- agent/severity
- agent/weakness
- agent/softwarecombine
- agent/first-publish-date
- agent/event
- agent/description
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/revive-adserver
- canonical/revive adserver
- version/revive adserver/3.2.2