LiveActive security incident?Get immediate response
CVE Record

CVE-2016-9125: Revive Adserver before 3.2.3 suffers from session fixation, by allowing arbitrary session identifiers to be...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Revive Adserver before 3.2.3 could let an attacker force a known session identifier and keep it after a victim logs in. If the conditions lined up, the attacker could take over that authenticated session. This is most concerning for organizations still running old Revive Adserver instances.

Executive priority

Treat this as a targeted remediation item for any legacy Revive Adserver deployment. It is not documented here as actively exploited, but the possible impact is account session theft, which can affect advertising operations and administrative control.

Technical view

CVE-2016-9125 is a session fixation issue in Revive Adserver before 3.2.3, mapped to CWE-384. The product allowed arbitrary session identifiers and did not invalidate the existing session after successful authentication. The sources indicate possible authenticated session theft under some circumstances, but do not provide CVSS scoring.

Likely exposure

Exposure is limited to Revive Adserver deployments running versions before 3.2.3. Internet-facing admin or operator access paths would be the main concern. The source bundle does not identify affected hosted services, downstream packages, or specific configurations beyond the version boundary.

Exploitation context

The provided sources do not show active exploitation, and this CVE is not marked KEV. Public references include HackerOne reports and a vendor advisory, so defenders should assume technical details have been available since disclosure, without claiming known in-the-wild use.

Researcher notes

The evidence supports session fixation through attacker-controlled session identifiers plus lack of post-authentication session invalidation. Public data in the bundle lacks CVSS metrics, environmental prerequisites, and confirmed exploitation. Avoid broad product assumptions beyond Revive Adserver before 3.2.3.

Mitigation direction

  • Upgrade Revive Adserver to version 3.2.3 or later.
  • Review the Revive SA-2016-001 advisory for vendor-specific guidance.
  • Invalidate active sessions after upgrading vulnerable instances.
  • Restrict administrative access to trusted networks where operationally possible.
  • Monitor for suspicious session reuse around authentication events.

Validation and detection

  • Inventory all Revive Adserver instances and record exact versions.
  • Flag any instance running below version 3.2.3 as affected.
  • Confirm authentication invalidates old sessions after successful login.
  • Review access logs for unusual shared or repeated session identifiers.
  • Verify exposed admin paths are access-controlled.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-384: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2016-9125 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aRevive Adserver All versions before 3.2.3Revive Adserver All versions before 3.2.3Listed
Weakness

CWE details

CWE-384

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-384 · source CWE mapping

Session Fixation

Session Fixation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs