Security advisory
Revive Adserver before 3.2.3 suffers from Improper Restriction of Excessive Authentication Attempts. The login page of Revive Adserver is vulnerable to password-guessing attacks. An account lockdown feature was considered, but rejected to avoid introducing service disruptions to regular users during such attacks. A random delay has instead been introduced as a countermeasure in case of password failures, along with a system to discourage parallel brute forcing. These systems will effectively allow the valid users to log in to the adserver, even while an attack is in progress.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2016-9124
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 31 Oct 2026, 09:49 UTC · Revision 1
Source evidence
Revive Adserver before 3.2.3 suffers from Improper Restriction of Excessive Authentication Attempts. The login page of Revive Adserver is vulnerable to password-guessing attacks. An account lockdown feature was considered, but rejected to avoid introducing service disruptions to regular users during such attacks. A random delay has instead been introduced as a countermeasure in case of password failures, along with a system to discourage parallel brute forcing. These systems will effectively allow the valid users to log in to the adserver, even while an attack is in progress.
osv:CVE-2016-9124
Complete source record
{
"id": "3c68eae82c345c65f4013384634f690551ebd1f3750f9cbddb32e49443786185",
"url": "https://osv.dev/vulnerability/CVE-2016-9124",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "CVE-2016-9124",
"summary": "Revive Adserver before 3.2.3 suffers from Improper Restriction of Excessive Authentication Attempts. The login page of Revive Adserver is vulnerable to password-guessing attacks. An account lockdown feature was considered, but rejected to avoid introducing service disruptions to regular users during such attacks. A random delay has instead been introduced as a countermeasure in case of password failures, along with a system to discourage parallel brute forcing. These systems will effectively allow the valid users to log in to the adserver, even while an attack is in progress.",
"evidence": "osv:CVE-2016-9124",
"products": [],
"severity": "critical",
"structured": {
"id": "CVE-2016-9124",
"aliases": [
"CVE-2016-9124"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/revive-adserver/revive-adserver",
"type": "GIT",
"events": [
{
"introduced": "0"
},
{
"last_affected": "e1fc268218ef914dc3c37d98b9721759f051f74f"
},
{
"fixed": "847941390f5b3310d51b07c92ec91cc1f4cc82c9"
}
],
"database_specific": {
"extracted_events": [
{
"cpe": "cpe:2.3:a:revive-adserver:revive_adserver:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "0"
},
{
"last_affected": "3.2.2"
}
],
"source": "CPE_RANGE"
},
{
"range": [
{
"fixed": "847941390f5b3310d51b07c92ec91cc1f4cc82c9"
}
],
"source": "REFERENCES_COMMIT"
}
]
}
}
],
"versions": [
"v3.2.2",
"v3.2.1",
"v3.2.1-rc1",
"v3.2.0",
"v3.2.0-beta",
"v3.1.0",
"v3.1.0-beta",
"v3.0.3",
"v3.0.2",
"v3.0.1",
"v3.0.0"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2016-9124.json"
}
}
],
"modified": "2026-10-20T10:48:04.727393753Z",
"provider": "osv",
"references": [
"https://hackerone.com/reports/96115",
"https://github.com/revive-adserver/revive-adserver/commit/847941390f5b3310d51b07c92ec91cc1f4cc82c9",
"https://www.revive-adserver.com/security/revive-sa-2016-001/"
],
"provider_metadata": {}
},
"related_cves": [
{
"value": "CVE-2016-9124",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 380013,
"published_at": "2017-03-28T02:59:00.323+00:00"
}