CVE-2019-15522: An issue was discovered in LINBIT csync2 through 2.0
CVE-2019-15522 is a critical-severity flaw (CVSS 9.8) affecting csync2. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
An issue was discovered in LINBIT csync2 through 2.0. csync_daemon_session in daemon.c neglects to force a failure of a hello command when the configuration requires use of SSL.
Why this priority
- Critical severity
- Remotely exploitable, no login, no user action
A fixed release or distro patch exists.
Risk facts
| CVSS score | 9.8 (Critical) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 1.9% (top 20%) |
| CISA exploited list | No |
| Published | 2020-03-20 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2019-15522?
csync2: upgrade to newer than 2.0. Exact commands for each OS are on this page.
Is CVE-2019-15522 being exploited?
CVE-2019-15522 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2019-15522 affect?
CVE-2019-15522 affects csync2. Severity is critical (CVSS 9.8). An issue was discovered in LINBIT csync2 through 2.0. csync_daemon_session in daemon.c neglects to force a failure of a hello command when the configuration requires use of SSL.
How urgent is CVE-2019-15522?
Priority 59/100. Critical severity; Remotely exploitable, no login, no user action
Related CVEs
- CVE-2019-15523 MEDIUM 5.3 UPGRADE MITIGATE An issue was discovered in LINBIT csync2 through 2.0