Caddy Web Server Caddy Server Caddy Web Server HTTP / HTTPS Server

stack.watch can notify you when security vulnerabilities are reported in Caddy Server Caddy Web Server. You can add multiple products that you use with Caddy Web Server to create your own personal software stack watcher.

@caddyserver Tweets

RT @mholt6: Caddy does not have this problem. (via https://t.co/cZnyvOWKWq) https://t.co/m2VhrgIXeX
Tue Jul 07 15:41:36 +0000 2020

Why is it sometimes hard to reverse-proxy web apps constrained to a certain path? @ItsWhitestrake breaks down "the… https://t.co/47x8cQB1Kq
Tue Jul 07 13:26:29 +0000 2020

RT @bojan_zivanovic: Both Traefik and Caddy can generate TLS certificates automatically via LetsEncrypt integration, but Caddy's is one ste…
Mon Jul 06 19:47:47 +0000 2020

RT @AllenHWoods: R1/D002 #365DaysOfCode: Got familiar with the API in @CaddyServer. Definitely going to use JSON + API for my use case. R…
Mon Jul 06 19:47:36 +0000 2020

By the Year

In 2020 there have been 1 vulnerability in Caddy Server Caddy Web Server with an average score of 9.8 out of ten. Last year Caddy Web Server had 0 security vulnerabilities published. That is, 1 more vulnerability have already been reported in 2020 as compared to last year.

Year Vulnerabilities Average Score
2020 1 9.80
2019 0 0.00
2018 1 3.70

It may take a day or so for new Caddy Web Server vulnerabilities to show up. Additionally vulnerabilities may be tagged under a different product or component name.

Latest Caddy Server Caddy Web Server Security Vulnerabilities

Caddy before 0.10.13 mishandles TLS client authentication

CVE-2018-21246 9.8 - Critical - June 15, 2020

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

authentification

Caddy through 0.11.0 sends incorrect certificates for certain invalid requests, making it easier for attackers to enumerate hostnames

CVE-2018-19148 3.7 - Low - November 10, 2018

Caddy through 0.11.0 sends incorrect certificates for certain invalid requests, making it easier for attackers to enumerate hostnames. Specifically, when unable to match a Host header with a vhost in its configuration, it serves the X.509 certificate for a randomly selected vhost in its configuration. Repeated requests (with a nonexistent hostname in the Host header) permit full enumeration of all certificates on the server. This generally permits an attacker to easily and accurately discover the existence of and relationships among hostnames that weren't meant to be public, though this information could likely have been discovered via other methods with additional effort.

Information Leak