CriticalGHSA-gr7w-x2jp-3xgwCVE-2018-21246GO-2020-0043

Caddy vulnerable to Authentication Bypass due to mishandling of TLS client authentication

Published 6 Oct 2022 · Updated 8 Nov 2023

Is your project on an affected github.com/caddyserver/caddy?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

Affected
<0.10.13
Fixed in
0.10.13
Update to the fixed version for your release line, for example:go get github.com/caddyserver/caddy@v0.10.13

Details

Caddy before 0.10.13 mishandles TLS client authentication, as demonstrated by an authentication bypass caused by the lack of the StrictHostMatching mode.

Is GHSA-gr7w-x2jp-3xgw in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/caddyserver/caddy, and gives you the command that fixes it.

More advisories for github.com/caddyserver/caddy

  • MediumCVE-2026-52846Caddy: stripHTML template function bypass · 16 Jun 2026
  • HighCVE-2026-52845Caddy: FastCGI header normalization bypass in `forward_auth copy_headers` · 16 Jun 2026
  • HighCVE-2026-52844Caddy: Windows `file_server` path authorization bypass via encoded backslash · 16 Jun 2026
  • MediumCVE-2022-29718Open redirect in caddy · 3 Jun 2022
  • LowCVE-2018-19148Caddy allows enumeration of Certificates and Hostnames · 14 May 2022
github.com/caddyserver/caddy security overview

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.