A vulnerability has been found in Revive Adserver up to 3.2.2 (Advertising Software) and classified as critical. Affected by this vulnerability is an unknown function of the component Session Identifier. The manipulation with an unknown input leads to a session fixiation vulnerability. The CWE definition for the vulnerability is CWE-384. Authenticating a user, or otherwise establishing a new user session, without invalidating any existing session identifier gives an attacker the opportunity to steal authenticated sessions. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

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.

The bug was discovered 03/02/2016. The weakness was shared 03/28/2017 (GitHub Repository). It is possible to read the advisory at github.com. This vulnerability is known as CVE-2016-9125 since 10/31/2016. The attack can be launched remotely. The exploitation doesn't need any form of authentication. The technical details are unknown and an exploit is not publicly available.

The vulnerability was handled as a non-public zero-day exploit for at least 390 days. During that time the estimated underground price was around $0-$5k.

Upgrading to version 3.2.3 eliminates this vulnerability.

Productinfo

Type

• Advertising Software

Vendor

• Revive

Name

• Adserver

Version

• 3.2.0
• 3.2.1
• 3.2.2

License

• free

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Discussion