CVE-2017-16548

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: 5%CVSS: 9.8Exploit: NoneExposed: 0

A fix is available — apply it.

The receive_xattr function in xattrs.c in rsync 3.1.2 and 3.1.3-development does not check for a trailing '\0' character in an xattr name, which allows remote attackers to cause a denial of service (heap-based buffer over-read and application crash) or possibly have unspecified other impact by sending crafted data to the daemon.

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

Published

November 6, 2017

Last Modified

May 13, 2026

Advisory Details (3)

Auto-updated May 17, 2026
Patch available.
generic Patch Available

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

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

13112 – receive_xattr heap overread with non null terminated name

https://bugzilla.samba.org/show_bug.cgi?id=13112
generic

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

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

Patch Availability(2)

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2017-16548?
CVE-2017-16548 is a critical vulnerability published on November 6, 2017. The receive_xattr function in xattrs.c in rsync 3.1.2 and 3.1.3-development does not check for a trailing '\0' character in an xattr name, which allows remote attackers to cause a denial of service (heap-based buffer over-read and application crash) or possibly have unspecified other impact by…
When was CVE-2017-16548 disclosed?
CVE-2017-16548 was first published in the National Vulnerability Database on November 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-16548 actively exploited?
CVE-2017-16548 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 91.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2017-16548?
CVE-2017-16548 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2017-16548?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-16548, 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-16548

Explore →

Is Your Infrastructure Affected by CVE-2017-16548?

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

Start Free Scan →Browse All CVEs