CVE-2020-35370: A RCE vulnerability exists in Raysync below 3.3.3.8

Q: How do I fix CVE-2020-35370?

raysync: upgrade to 3.3.3.8. Exact commands for each OS are on this page.

Q: Is CVE-2020-35370 being exploited?

CVE-2020-35370 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2020-35370 affect?

CVE-2020-35370 affects raysync. Severity is high (CVSS 8.8). A RCE vulnerability exists in Raysync below 3.3.3.8. An unauthenticated unauthorized attacker sending a specifically crafted request to override the specific file in server with malicious content can login as "admin", then to modify specifi

Q: How urgent is CVE-2020-35370?

Priority 59/100. High severity; EPSS top 5%: very likely to be exploited; Public exploit reference

This month

HIGH 8.8UPGRADE

CVE-2020-35370 is a high-severity flaw (CVSS 8.8) affecting raysync. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A RCE vulnerability exists in Raysync below 3.3.3.8. An unauthenticated unauthorized attacker sending a specifically crafted request to override the specific file in server with malicious content can login as "admin", then to modify specific shell file to achieve remote code execution(RCE) on the hosting server.

Why this priority

High severity
EPSS top 5%: very likely to be exploited
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	7.8% (top 5%)
CISA exploited list	No
Weakness	CWE-22
Published	2020-12-23
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: raysync

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2020-12-23 19:15 UTCPublished CVE record published
2026-06-17 03:13 UTCUpdated Record last modified

raysync raysync UPGRADE

Affected: < 3.3.3.8

Fixed in: 3.3.3.8

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy raysync || rpm -q raysync || raysync --version

2. UPGRADE to 3.3.3.8 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade raysync

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade raysync

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
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-2020-35370?

raysync: upgrade to 3.3.3.8. Exact commands for each OS are on this page.

Is CVE-2020-35370 being exploited?

CVE-2020-35370 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-2020-35370 affect?

CVE-2020-35370 affects raysync. Severity is high (CVSS 8.8). A RCE vulnerability exists in Raysync below 3.3.3.8. An unauthenticated unauthorized attacker sending a specifically crafted request to override the specific file in server with malicious content can login as "admin", then to modify specifi

How urgent is CVE-2020-35370?

Priority 59/100. High severity; EPSS top 5%: very likely to be exploited; Public exploit reference

References

← Back to latest CVEs