CVE-2017-17434

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-05-13. 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: 3%CVSS: 9.8Exploit: NoneExposed: 0

A fix is available — apply it.

The daemon in rsync 3.1.2, and 3.1.3-development before 2017-12-03, does not check for fnamecmp filenames in the daemon_filter_list data structure (in the recv_files function in receiver.c) and also does not apply the sanitize_paths protection mechanism to pathnames found in "xname follows" strings (in the read_ndx_and_attrs function in rsync.c), which allows remote attackers to bypass intended access restrictions.

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

Published

December 6, 2017

Last Modified

May 13, 2026

Advisory Details (2)

Auto-updated May 18, 2026
Patch available.
generic

[SECURITY] [DSA 4068-1] rsync security update

https://www.debian.org/security/2017/dsa-4068
generic Patch Available

[SECURITY] [DLA 1218-1] rsync security update

https://lists.debian.org/debian-lts-announce/2017/12/msg00020.html

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntursync (3.0.9-1ubuntu1.2) @ precise2026-05-20ubuntu
ubuntursync (3.1.1-3ubuntu1.1) @ xenial2026-05-20ubuntu

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.

All Vendor Advisories

(2)

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

Frequently asked(5)

What is CVE-2017-17434?
CVE-2017-17434 is a critical vulnerability published on December 6, 2017. The daemon in rsync 3.1.2, and 3.1.3-development before 2017-12-03, does not check for fnamecmp filenames in the daemonfilterlist data structure (in the recvfiles function in receiver.c) and also does not apply the sanitizepaths protection mechanism to pathnames found in "xname follows" strings (in…
When was CVE-2017-17434 disclosed?
CVE-2017-17434 was first published in the National Vulnerability Database on December 6, 2017, with the most recent update on May 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-17434 actively exploited?
CVE-2017-17434 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 87.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2017-17434?
CVE-2017-17434 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2017-17434?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-17434, 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-2017-17434

Explore →

Is Your Infrastructure Affected by CVE-2017-17434?

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