CVE-2015-2320

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

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

A fix is available — apply it.

The TLS stack in Mono before 3.12.1 allows remote attackers to have unspecified impact via vectors related to client-side SSLv2 fallback.

CVSS v3
9.8
EG Score
9.8(medium)
EPSS
88.0%
KEV
Not listed

Published

January 8, 2018

Last Modified

November 21, 2024

Advisory Details (6)

Auto-updated May 23, 2026
Patch available. Sources: redhat.
generic

oss-security - Re: Mono TLS vulnerabilities

http://www.openwall.com/lists/oss-security/2015/03/17/9
generic

[SECURITY] [DSA 3202-1] mono security update

https://www.debian.org/security/2015/dsa-3202
generic

Remove the client-side SSLv2 fallback. · mono/mono@b371da6 · GitHub

https://github.com/mono/mono/commit/b371da6b2d68b4cdd0f21d6342af6c42794f998b
redhat Patch Available

1202869 – (CVE-2015-2318, CVE-2015-2319, CVE-2015-2320) CVE-2015-2318 CVE-2015-2319 CVE-2015-2320 mono: TLS implementation vulnerabilities

https://bugzilla.redhat.com/show_bug.cgi?id=1202869

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntumono-runtime (3.2.8+dfsg-4ubuntu2.1) @ utopic2026-05-28ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 7× in last 7d / 40× 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-15 16:54 UTCEPSS rescore
  2. 2026-07-15 16:54 UTCEPSS rescore
  3. 2026-07-15 01:56 UTCEPSS rescore
  4. 2026-07-13 22:26 UTCEPSS rescore
  5. 2026-07-12 05:42 UTCEPSS rescore
  6. 2026-07-11 08:23 UTCEPSS rescore
  7. 2026-07-09 19:05 UTCEPSS rescore
  8. 2026-07-08 15:10 UTCEPSS rescore
  9. 2026-07-06 16:24 UTCEPSS rescore
  10. 2026-07-06 02:20 UTCEPSS rescore
  11. 2026-07-05 02:26 UTCEPSS rescore
  12. 2026-07-04 15:26 UTCOSV refresh
  13. 2026-07-04 06:27 UTCEPSS rescore
  14. 2026-07-02 15:21 UTCEPSS rescore
  15. 2026-07-01 15:02 UTCEPSS rescore
  16. 2026-07-01 15:02 UTCEPSS rescore
  17. 2026-06-30 23:19 UTCEPSS rescore
  18. 2026-06-30 23:19 UTCEPSS rescore
  19. 2026-06-29 14:03 UTCEPSS rescore
  20. 2026-06-28 14:03 UTCEPSS rescore
  21. 2026-06-28 04:53 UTCEPSS rescore
  22. 2026-06-27 03:05 UTCEPSS rescore
  23. 2026-06-25 13:47 UTCEPSS rescore
  24. 2026-06-25 13:47 UTCEPSS rescore
  25. 2026-06-24 14:02 UTCEPSS rescore
Show 51 more
  1. 2026-06-24 14:02 UTCEPSS rescore
  2. 2026-06-23 21:30 UTCEPSS rescore
  3. 2026-06-22 14:23 UTCEPSS rescore
  4. 2026-06-22 14:22 UTCEPSS rescore
  5. 2026-06-21 14:54 UTCEPSS rescore
  6. 2026-06-21 01:57 UTCEPSS rescore
  7. 2026-06-21 01:57 UTCEPSS rescore
  8. 2026-06-19 19:23 UTCEPSS rescore
  9. 2026-06-19 19:23 UTCEPSS rescore
  10. 2026-06-18 17:50 UTCEPSS rescore
  11. 2026-06-18 17:49 UTCEPSS rescore
  12. 2026-06-17 17:49 UTCEPSS rescore
  13. 2026-06-16 17:50 UTCEPSS rescore
  14. 2026-06-16 17:49 UTCEPSS rescore
  15. 2026-06-16 03:09 UTCOSV refresh
  16. 2026-06-15 17:45 UTCEPSS rescore
  17. 2026-06-14 23:14 UTCEPSS rescore
  18. 2026-06-13 22:57 UTCEPSS rescore
  19. 2026-06-12 23:09 UTCEPSS rescore
  20. 2026-06-11 13:57 UTCEPSS rescore
  21. 2026-06-10 22:15 UTCEPSS rescore
  22. 2026-06-08 14:14 UTCEPSS rescore
  23. 2026-06-07 15:22 UTCEPSS rescore
  24. 2026-06-06 13:45 UTCEPSS rescore
  25. 2026-06-05 22:44 UTCEPSS rescore
  26. 2026-06-05 06:08 UTCEPSS rescore
  27. 2026-06-05 06:08 UTCEPSS rescore
  28. 2026-06-04 13:10 UTCEPSS rescore
  29. 2026-06-04 13:09 UTCEPSS rescore
  30. 2026-06-02 20:10 UTCEPSS rescore
  31. 2026-06-02 20:10 UTCEPSS rescore
  32. 2026-06-01 13:49 UTCEPSS rescore
  33. 2026-06-01 13:49 UTCEPSS rescore
  34. 2026-05-31 22:28 UTCEPSS rescore
  35. 2026-05-31 22:28 UTCEPSS rescore
  36. 2026-05-31 22:28 UTCEPSS rescore
  37. 2026-05-31 00:14 UTCEPSS rescore
  38. 2026-05-29 13:41 UTCEPSS rescore
  39. 2026-05-28 13:42 UTCEPSS rescore
  40. 2026-05-28 13:42 UTCEPSS rescore
  41. 2026-05-28 12:48 UTCEG score recompute
  42. 2026-05-28 12:48 UTCVendor advisory
  43. 2026-05-28 12:48 UTCGHSA enrichment
  44. 2026-05-27 13:38 UTCEPSS rescore
  45. 2026-05-27 13:38 UTCEPSS rescore
  46. 2026-05-26 13:41 UTCEPSS rescore
  47. 2026-05-26 13:41 UTCEPSS rescore
  48. 2026-05-26 07:16 UTCEPSS rescore
  49. 2026-05-26 07:16 UTCEPSS rescore
  50. 2026-05-24 16:43 UTCEPSS rescore
  51. 2026-05-23 15:10 UTCEPSS rescore

Frequently asked(5)

What is CVE-2015-2320?
CVE-2015-2320 is a critical vulnerability published on January 8, 2018. The TLS stack in Mono before 3.12.1 allows remote attackers to have unspecified impact via vectors related to client-side SSLv2 fallback.
When was CVE-2015-2320 disclosed?
CVE-2015-2320 was first published in the National Vulnerability Database on January 8, 2018, 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-2015-2320 actively exploited?
CVE-2015-2320 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 88.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2015-2320?
CVE-2015-2320 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2015-2320?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2015-2320, 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-2015-2320

Explore →

Is Your Infrastructure Affected by CVE-2015-2320?

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