CVE-2018-20683

HIGHNVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2022-05-14. NVD baseline CVSS 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 2%CVSS: 8.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

commands/rsync in Gitolite before 3.6.11, if .gitolite.rc enables rsync, mishandles the rsync command line, which allows attackers to have a "bad" impact by triggering use of an option other than -v, -n, -q, or -P.

CVSS v3
8.1
EG Score
8.1(medium)
EG Risk
42(Track)
EG Risk 42/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity81% × 45%
Exploitation2% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
2%
EPSS %ILE
79%
KEV
Not listed

Published

January 10, 2019

Last Modified

November 21, 2024

References (8)

Affected Packages

(23 across 23 ecosystems)
Alpine:v3.10(1)
PackageVulnerable rangeFixed inDependents
gitolite—3.6.11-r0—
Alpine:v3.11(1)
PackageVulnerable rangeFixed inDependents
gitolite—3.6.11-r0—
Alpine:v3.12(1)
PackageVulnerable rangeFixed inDependents
gitolite—3.6.11-r0—
Alpine:v3.13(1)
PackageVulnerable rangeFixed inDependents
gitolite—3.6.11-r0—
Alpine:v3.14(1)
PackageVulnerable rangeFixed inDependents
gitolite—3.6.11-r0—
Alpine:v3.15(1)
PackageVulnerable rangeFixed inDependents
gitolite—3.6.11-r0—
Alpine:v3.16(1)
PackageVulnerable rangeFixed inDependents
gitolite—3.6.11-r0—
Alpine:v3.17(1)
PackageVulnerable rangeFixed inDependents
gitolite—3.6.11-r0—
Alpine:v3.18(1)
PackageVulnerable rangeFixed inDependents
gitolite—3.6.11-r0—
Alpine:v3.19(1)
PackageVulnerable rangeFixed inDependents
gitolite—3.6.11-r0—
Alpine:v3.20(1)
PackageVulnerable rangeFixed inDependents
gitolite—3.6.11-r0—
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
gitolite—3.6.11-r0—
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
gitolite—3.6.11-r0—
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
gitolite—3.6.11-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
gitolite—3.6.11-r0—
Alpine:v3.6(1)
PackageVulnerable rangeFixed inDependents
gitolite—3.6.11-r0—
Alpine:v3.7(1)
PackageVulnerable rangeFixed inDependents
gitolite—3.6.11-r0—
Alpine:v3.8(1)
PackageVulnerable rangeFixed inDependents
gitolite—3.6.11-r0—
Alpine:v3.9(1)
PackageVulnerable rangeFixed inDependents
gitolite—3.6.11-r0—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
gitolite3—3.6.11-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
gitolite3—3.6.11-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
gitolite3—3.6.11-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
gitolite3—3.6.11-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 28× 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.

Showing the most recent 100 of 126 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2018-20683?
CVE-2018-20683 is a high vulnerability published on January 10, 2019. commands/rsync in Gitolite before 3.6.11, if .gitolite.rc enables rsync, mishandles the rsync command line, which allows attackers to have a "bad" impact by triggering use of an option other than -v, -n, -q, or -P.
When was CVE-2018-20683 disclosed?
CVE-2018-20683 was first published in the National Vulnerability Database on January 10, 2019, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2018-20683 actively exploited?
CVE-2018-20683 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2% probability of exploitation in the next 30 days, which ranks it in the top 20.7% of all scored CVEs.
What is the CVSS score of CVE-2018-20683?
CVE-2018-20683 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2018-20683?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2018-20683, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2018-20683

Explore →

Is Your Infrastructure Affected by CVE-2018-20683?

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

Start Free Scan →Browse All CVEs