CVE-2019-8978

HIGHNVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2022-05-24. NVD baseline CVSS 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
8.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 6%CVSS: 8.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

An improper authentication vulnerability can be exploited through a race condition that occurs in Ellucian Banner Web Tailor 8.8.3, 8.8.4, and 8.9 and Banner Enterprise Identity Services 8.3, 8.3.1, 8.3.2, and 8.4, in conjunction with SSO Manager. This vulnerability allows remote attackers to steal a victim's session (and cause a denial of service) by repeatedly requesting the initial Banner Web Tailor main page with the IDMSESSID cookie set to the victim's UDCID, which in the case tested is the institutional ID. During a login attempt by a victim, the attacker can leverage the race condition and will be issued the SESSID that was meant for this victim.

CVSS v3
8.1
EG Score
8.1(medium)
EG Risk
57(Track)
EG Risk 57/100SSVC: Track

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
Severity81% × 45%
Exploitation40% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
92.4%
KEV
Not listed

Published

May 14, 2019

Last Modified

November 21, 2024

References (12)

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 43× 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.

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

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCSecKatie/CVE-2019-8978
    First seen May 10, 2019

    Banner Web Tailor and Banner Enterprise Identity Services Vulnerability Disclosure

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2019-8978?
CVE-2019-8978 is a high vulnerability published on May 14, 2019. An improper authentication vulnerability can be exploited through a race condition that occurs in Ellucian Banner Web Tailor 8.8.3, 8.8.4, and 8.9 and Banner Enterprise Identity Services 8.3, 8.3.1, 8.3.2, and 8.4, in conjunction with SSO Manager. This vulnerability allows remote attackers to steal…
When was CVE-2019-8978 disclosed?
CVE-2019-8978 was first published in the National Vulnerability Database on May 14, 2019, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-8978 actively exploited?
CVE-2019-8978 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 92.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2019-8978?
CVE-2019-8978 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2019-8978?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-8978, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2019-8978

Explore →

Is Your Infrastructure Affected by CVE-2019-8978?

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

Start Free Scan →Browse All CVEs