github.com/labstack/echo/v4 vulnerabilities
- Registry
- Go
- Latest
- 4.16.5
34 known advisories
The latest version, 4.16.5, is affected by 2 of them.
Is your project on an affected github.com/labstack/echo/v4?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for github.com/labstack/echo/v4
Rate Limiter Bypass via Spoofed X-Forwarded-For Header in Default Configuration in github.com/labstack/echo
- Affected
- >=4.0.0
- Fixed in
- No fix released
URL-encoded path bypasses route/group middleware guarding a statically-served path in github.com/labstack/echo
- Affected
- <4.16.0
- Fixed in
- 4.16.0
Reverse Proxy Forwards Attacker-Supplied X-Real-IP to Upstream by Default in github.com/labstack/echo
- Affected
- >=4.0.0
- Fixed in
- No fix released
Cross-Site Scripting (XSS) via unsanitized JSONP callback in github.com/labstack/echo
- Affected
- <4.16.0
- Fixed in
- 4.16.0
Echo has CSRF Protection Bypass via MethodOverride Rewriting POST to Safe Method in github.com/labstack/echo
- Affected
- <4.16.0
- Fixed in
- 4.16.0
Arbitrary Scheme Injection in WWWRedirect/NonWWWRedirect Middlewares via X-Forwarded-Proto in github.com/labstack/echo
- Affected
- <4.15.2
- Fixed in
- 4.15.2
Echo: HTTPS Redirect and HSTS Bypass via Unconditional Trust of Forwarded Scheme Headers in github.com/labstack/echo
- Affected
- <4.16.0
- Fixed in
- 4.16.0
Echo static file middleware route protection bypass via encoded dot-dot traversal in github.com/labstack/echo
- Affected
- <4.16.0
- Fixed in
- 4.16.0
Echo has Open Redirect via Control-Character Prefix Defeating sanitizeURI in github.com/labstack/echo
- Affected
- <4.16.0
- Fixed in
- 4.16.0
Echo has a Static Middleware Double-Unescape Path Traversal in github.com/labstack/echo
- Affected
- <4.15.3
- Fixed in
- 4.15.3
Echo: WebSocket proxy can retain connections and handlers after client disconnect in github.com/labstack/echo
- Affected
- >=4.15.0 <4.16.1
- Fixed in
- 4.16.1
Echo: Rejected WebSocket upgrades can bypass Echo route-level access controls in github.com/labstack/echo
- Affected
- >=4.0.0 <4.16.1
- Fixed in
- 4.16.1
Echo: BodyDump captures request and response bodies without size limits in v4 in github.com/labstack/echo
- Affected
- >=4.0.0 <4.16.1
- Fixed in
- 4.16.1
Echo: Decompress permits unbounded gzip expansion in v4 in github.com/labstack/echo
- Affected
- >=4.0.0 <4.16.1
- Fixed in
- 4.16.1
Echo: HTTPS Redirect and HSTS Bypass via Unconditional Trust of Forwarded Scheme Headers
- Affected
- <4.16.0
- Fixed in
- 4.16.0
Echo static file middleware route protection bypass via encoded dot-dot traversal
- Affected
- <4.16.0
- Fixed in
- 4.16.0
Echo has a Static Middleware Double-Unescape Path Traversal
- Affected
- <4.15.3
- Fixed in
- 4.15.3
Echo has Open Redirect via Control-Character Prefix Defeating sanitizeURI
- Affected
- <4.16.0
- Fixed in
- 4.16.0
Echo has Arbitrary Scheme Injection in WWWRedirect/NonWWWRedirect Middlewares via X-Forwarded-Proto
- Affected
- <4.15.2
- Fixed in
- 4.15.2
Echo's middleware.Static: `%2F`-encoded path bypasses route/group middleware guarding a statically-served path
- Affected
- <4.16.0
- Fixed in
- 4.16.0
Echo vulnerable to Reflected Cross-Site Scripting (XSS) via unsanitized JSONP callback in Context.JSONP / Context.JSONPBlob
- Affected
- <4.16.0
- Fixed in
- 4.16.0
Echo has Rate Limiter Bypass via Spoofed X-Forwarded-For Header in Default Configuration
- Affected
- >=4.0.0 <=4.16.2
- Fixed in
- No fix released
Echo has CSRF Protection Bypass via MethodOverride Rewriting POST to Safe Method
- Affected
- <4.16.0
- Fixed in
- 4.16.0
Echo: Reverse Proxy Forwards Attacker-Supplied X-Real-IP to Upstream by Default
- Affected
- >=4.0.0 <=4.16.2
- Fixed in
- No fix released
Echo: WebSocket proxy can retain connections and handlers after client disconnect
- Affected
- >=4.15.0 <4.16.1
- Fixed in
- 4.16.1
Echo: Decompress permits unbounded gzip expansion in v4
- Affected
- >=4.0.0 <4.16.1
- Fixed in
- 4.16.1
Echo: Rejected WebSocket upgrades can bypass Echo route-level access controls
- Affected
- >=4.0.0 <4.16.1
- Fixed in
- 4.16.1
Echo: BodyDump captures request and response bodies without size limits in v4
- Affected
- >=4.0.0 <4.16.1
- Fixed in
- 4.16.1
Encoded slash (%2F) bypasses route-level protection and exposes static files in github.com/labstack/echo/v4 and github.com/labstack/echo/v5
- Affected
- <4.15.3
- Fixed in
- 4.15.3
Echo: Encoded slash (%2F) bypasses route-level protection and exposes static files
- Affected
- <4.15.3
- Fixed in
- 4.15.3
Echo vulnerable to directory traversal
- Affected
- <4.2.0
- Fixed in
- 4.2.0
Open redirect in github.com/labstack/echo/v4
- Affected
- <4.9.0
- Fixed in
- 4.9.0
Labstack Echo Open Redirect vulnerability
- Affected
- <4.9.0
- Fixed in
- 4.9.0
Directory traversal on Windows in github.com/labstack/echo/v4
- Affected
- <4.1.18-0.20201215153152-4422e3b66b9f
- Fixed in
- 4.1.18-0.20201215153152-4422e3b66b9f
Is your github.com/labstack/echo/v4 version vulnerable?
- github.com/labstack/echo/v4 4.162 advisories in 4.16.5
- github.com/labstack/echo/v4 4.1524 advisories in 4.15.4
- github.com/labstack/echo/v4 4.1428 advisories in 4.14.0
- github.com/labstack/echo/v4 4.1328 advisories in 4.13.4
- github.com/labstack/echo/v4 4.1228 advisories in 4.12.0
- github.com/labstack/echo/v4 4.1128 advisories in 4.11.4
Which of your client projects still run an old github.com/labstack/echo/v4?
NPMscan reads the go.mod in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other Go packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Go registry.