Skip to content
Fencer Intel
medium 5.3

CVE-2020-36565 json

Directory traversal on Windows in github.com/labstack/echo/v4

published 5y ago modified 4mo ago also GHSA-j453-hm5x-c46w , GO-2021-0051 , EUVD-2022-7655

cvss
5.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.4%
EPSS 1.4% chance of exploitation in 30 days, percentile 72%
public exploits
0
none known

Summary

Due to improper sanitization of user input on Windows, the static file handler allows for directory traversal, allowing an attacker to read files outside of the target directory that the server has permission to read.

Patch / fix

  • go github.com/labstack/echo/v4 4.1.18-0.20201215153152-4422e3b66b9f, 4.2.0
  • github.com/labstack/echo/v4 github.com/labstack/echo/v4 4.1.18-0.20201215153152-4422e3b66b9f

Is CVE-2020-36565 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
Proof of concept is public
Automatable
yes
Technical impact
partial
Assessed
last yr.

Exploit prediction

1.41% chance of exploitation in the next 30 days, higher than 72% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/labstack/echo/pull/1718 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CISA ADP 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
NVD 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
CNA 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
GitHub 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
go github.com/labstack/echo/v4
<4.2.0
<4.1.18-0.20201215153152-4422e3b66b9f
4.2.0
4.1.18-0.20201215153152-4422e3b66b9f

Affected products

  • github.com/labstack/echo/v4 github.com/labstack/echo/v4

Classification

Weakness
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.