CVE-2020-15117
published 2020-07-15CVE-2020-15117: In Synergy before version 1.12.0, a Synergy server can be crashed by receiving a kMsgHelloBack packet with a client name length set to 0xffffffff (4294967295)…
PriorityP433medium6.5CVSS 3.1
AVNACLPRLUINSUCNINAH
EPSS
2.49%
83.1th percentile
In Synergy before version 1.12.0, a Synergy server can be crashed by receiving a kMsgHelloBack packet with a client name length set to 0xffffffff (4294967295) if the servers memory is less than 4 GB. It was verified that this issue does not cause a crash through the exception handler if the available memory of the Server is more than 4GB.
Affected
4 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| fedoraproject | fedora | — | — |
| fedoraproject | fedora | — | — |
| symless | synergy | < 1.12.0 | 1.12.0 |
| symless | synergy-core | < 1.12.0 | 1.12.0 |
CVSS provenance
nvdv3.16.5MEDIUMCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvdv2.04.0MEDIUMAV:N/AC:L/Au:S/C:N/I:N/A:P
osv6.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2020-15117 synergy: kMsgHelloBack packet with client name length of 0xffffffff causing DoS [fedora-all]
bugzilla·2020-07-17·CVSS 6.5
CVE-2020-15117 [MEDIUM] CVE-2020-15117 synergy: kMsgHelloBack packet with client name length of 0xffffffff causing DoS [fedora-all]
CVE-2020-15117 synergy: kMsgHelloBack packet with client name length of 0xffffffff causing DoS [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affec
Bugzilla
CVE-2020-15117 synergy: kMsgHelloBack packet with client name length of 0xffffffff causing DoS
bugzilla·2020-07-17·CVSS 6.5
CVE-2020-15117 [MEDIUM] CVE-2020-15117 synergy: kMsgHelloBack packet with client name length of 0xffffffff causing DoS
CVE-2020-15117 synergy: kMsgHelloBack packet with client name length of 0xffffffff causing DoS
In Synergy before version 1.12.0, a Synergy server can be crashed by receiving a kMsgHelloBack packet with a client name length set to 0xffffffff (4294967295) if the servers memory is less than 4 GB. It was verified that this issue does not cause a crash through the exception handler if the available memory of the Server is more than 4GB.
References:
https://github.com/symless/synergy-core/commit/0a97c2be0da2d0df25cb86dfd642429e7a8bea39
https://github.com/symless/synergy-core/security/advisories/GHSA-chfm-333q-gfpp
Discussion:
Created synergy tracking bugs for this issue:
Affects: epel-all [bug 1858255]
Affects: fedora-all [bug 1858254]
---
This CVE Bugzilla entry is for community support
Bugzilla
CVE-2020-15117 synergy: kMsgHelloBack packet with client name length of 0xffffffff causing DoS [epel-all]
bugzilla·2020-07-17·CVSS 6.5
CVE-2020-15117 [MEDIUM] CVE-2020-15117 synergy: kMsgHelloBack packet with client name length of 0xffffffff causing DoS [epel-all]
CVE-2020-15117 synergy: kMsgHelloBack packet with client name length of 0xffffffff causing DoS [epel-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of epel-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects m
https://github.com/symless/synergy-core/commit/0a97c2be0da2d0df25cb86dfd642429e7a8bea39https://github.com/symless/synergy-core/security/advisories/GHSA-chfm-333q-gfpphttps://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/VFDEQED64YLWQK2TF73EMXZDYX7YT2DD/https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/WAQYCMBWNVCIEM27NPIKK3DGJCNBYLAK/https://github.com/symless/synergy-core/commit/0a97c2be0da2d0df25cb86dfd642429e7a8bea39https://github.com/symless/synergy-core/security/advisories/GHSA-chfm-333q-gfpphttps://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/VFDEQED64YLWQK2TF73EMXZDYX7YT2DD/https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/WAQYCMBWNVCIEM27NPIKK3DGJCNBYLAK/
2020-07-15
Published