CVE-2016-9124

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-05-13. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
9.8EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 2.2%CVSS: 9.8Exploit: None knownExposed services: Not assessed

An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.

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.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
49
EG Risk 49/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation2% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track* or Attend at high (mission-essential systems).
Action: An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high until it ships, then apply the release.
EPSS PROB
2.2%
EPSS %ILE
82nd
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* or Attend at high (mission-essential systems).

An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high until it ships, then apply the release.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact total (CVSS ≥ 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

March 28, 2017

Last Modified

June 17, 2026

Advisory Details (3)

Auto-updated Sep 29, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
generic

HackerOne

https://hackerone.com/reports/96115
github_commit

commit 847941390f5b (revive-adserver/revive-adserver)

Fix landed in revive-adserver/revive-adserver commit 847941390f5b — awaiting tagged release

https://github.com/revive-adserver/revive-adserver/commit/847941390f5b3310d51b07c92ec91cc1f4cc82c9
generic

Revive Adserver Security Advisory SA-2016-001

https://www.revive-adserver.com/security/revive-sa-2016-001/

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 24× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 161 total refreshes for this CVE.

  1. 2026-10-05 17:38 UTCEPSS rescore
  2. 2026-10-04 23:17 UTCEPSS rescore
  3. 2026-10-04 08:37 UTCOSV refresh
  4. 2026-10-03 14:21 UTCEPSS rescore
  5. 2026-10-03 14:21 UTCEPSS rescore
  6. 2026-09-30 14:58 UTCEPSS rescore
  7. 2026-09-30 09:17 UTCEG score recompute
  8. 2026-09-28 13:45 UTCEPSS rescore
  9. 2026-09-27 13:40 UTCEPSS rescore
  10. 2026-09-26 15:53 UTCEPSS rescore
  11. 2026-09-26 15:53 UTCEPSS rescore
  12. 2026-09-24 13:59 UTCEPSS rescore
  13. 2026-09-23 13:41 UTCEPSS rescore
  14. 2026-09-19 15:35 UTCEPSS rescore
  15. 2026-09-18 19:22 UTCEPSS rescore
  16. 2026-09-17 19:22 UTCEPSS rescore
  17. 2026-09-16 05:05 UTCEPSS rescore
  18. 2026-09-15 03:05 UTCEPSS rescore
  19. 2026-09-14 22:44 UTCOSV refresh
  20. 2026-09-12 14:55 UTCEPSS rescore
  21. 2026-09-11 14:46 UTCEPSS rescore
  22. 2026-09-11 09:31 UTCEPSS rescore
  23. 2026-09-10 09:26 UTCEPSS rescore
  24. 2026-09-07 15:56 UTCEPSS rescore
  25. 2026-09-04 13:56 UTCEPSS rescore
Show 75 more
  1. 2026-09-02 14:07 UTCEPSS rescore
  2. 2026-09-01 13:48 UTCEPSS rescore
  3. 2026-09-01 03:31 UTCEPSS rescore
  4. 2026-08-28 21:35 UTCEPSS rescore
  5. 2026-08-27 14:20 UTCEPSS rescore
  6. 2026-08-26 22:16 UTCOSV refresh
  7. 2026-08-26 14:41 UTCEPSS rescore
  8. 2026-08-25 13:44 UTCEPSS rescore
  9. 2026-08-21 23:44 UTCEPSS rescore
  10. 2026-08-19 16:59 UTCEPSS rescore
  11. 2026-08-18 13:43 UTCEPSS rescore
  12. 2026-08-17 13:42 UTCEPSS rescore
  13. 2026-08-16 14:51 UTCEPSS rescore
  14. 2026-08-16 02:10 UTCEPSS rescore
  15. 2026-08-15 01:25 UTCEPSS rescore
  16. 2026-08-12 13:46 UTCEPSS rescore
  17. 2026-08-11 13:36 UTCEPSS rescore
  18. 2026-08-10 12:39 UTCOSV refresh
  19. 2026-08-09 13:42 UTCEPSS rescore
  20. 2026-08-08 16:32 UTCEPSS rescore
  21. 2026-08-07 16:22 UTCEPSS rescore
  22. 2026-08-06 13:42 UTCEPSS rescore
  23. 2026-08-05 19:12 UTCEPSS rescore
  24. 2026-08-04 15:05 UTCEPSS rescore
  25. 2026-08-02 02:22 UTCEPSS rescore
  26. 2026-08-01 04:11 UTCEPSS rescore
  27. 2026-07-30 16:24 UTCEPSS rescore
  28. 2026-07-30 01:26 UTCEPSS rescore
  29. 2026-07-30 01:26 UTCEPSS rescore
  30. 2026-07-28 15:31 UTCEPSS rescore
  31. 2026-07-26 14:50 UTCEPSS rescore
  32. 2026-07-25 14:13 UTCEPSS rescore
  33. 2026-07-25 13:11 UTCOSV refresh
  34. 2026-07-24 14:13 UTCEPSS rescore
  35. 2026-07-23 14:15 UTCEPSS rescore
  36. 2026-07-23 01:24 UTCEG score recompute
  37. 2026-07-22 22:04 UTCEG score recompute
  38. 2026-07-22 14:04 UTCEPSS rescore
  39. 2026-07-21 15:21 UTCEPSS rescore
  40. 2026-07-21 15:21 UTCEPSS rescore
  41. 2026-07-20 17:04 UTCEPSS rescore
  42. 2026-07-19 14:28 UTCEPSS rescore
  43. 2026-07-19 14:28 UTCEPSS rescore
  44. 2026-07-19 02:26 UTCEPSS rescore
  45. 2026-07-19 02:26 UTCEPSS rescore
  46. 2026-07-18 10:00 UTCEPSS rescore
  47. 2026-07-18 10:00 UTCEPSS rescore
  48. 2026-07-16 16:59 UTCEPSS rescore
  49. 2026-07-16 16:59 UTCEPSS rescore
  50. 2026-07-15 16:54 UTCEPSS rescore
  51. 2026-07-15 16:54 UTCEPSS rescore
  52. 2026-07-15 01:56 UTCEPSS rescore
  53. 2026-07-13 22:26 UTCEPSS rescore
  54. 2026-07-13 06:09 UTCEPSS rescore
  55. 2026-07-12 05:43 UTCEPSS rescore
  56. 2026-07-12 05:43 UTCEPSS rescore
  57. 2026-07-11 08:24 UTCEPSS rescore
  58. 2026-07-09 19:06 UTCEPSS rescore
  59. 2026-07-08 15:10 UTCEPSS rescore
  60. 2026-07-08 07:35 UTCOSV refresh
  61. 2026-07-07 13:42 UTCEPSS rescore
  62. 2026-07-06 16:24 UTCEPSS rescore
  63. 2026-07-06 16:24 UTCEPSS rescore
  64. 2026-07-06 02:20 UTCEPSS rescore
  65. 2026-07-06 02:20 UTCEPSS rescore
  66. 2026-07-05 02:27 UTCEPSS rescore
  67. 2026-07-04 06:28 UTCEPSS rescore
  68. 2026-07-01 15:02 UTCEPSS rescore
  69. 2026-06-30 23:19 UTCEPSS rescore
  70. 2026-06-30 23:19 UTCEPSS rescore
  71. 2026-06-29 14:03 UTCEPSS rescore
  72. 2026-06-28 14:04 UTCEPSS rescore
  73. 2026-06-28 04:53 UTCEPSS rescore
  74. 2026-06-27 03:05 UTCEPSS rescore
  75. 2026-06-25 13:47 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2016-9124?
CVE-2016-9124 is a critical vulnerability published on March 28, 2017. 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…
When was CVE-2016-9124 disclosed?
CVE-2016-9124 was first published on March 28, 2017, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2016-9124 actively exploited?
CVE-2016-9124 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.2% probability of exploitation in the next 30 days (82nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2016-9124?
CVE-2016-9124 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2016-9124?
An upstream fix for CVE-2016-9124 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2016-9124

Explore →

Is Your Infrastructure Affected by CVE-2016-9124?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs