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

Our collaborators are what make the project. Thank you to all who contribute! https://t.co/U0RhWDTvWu
Tue Sep 29 15:14:35 +0000 2020

For simple reverse proxying, you don't even need a config file. You even get HTTPS! Caddy is the only web server to… https://t.co/bFWhIM1ETF
Mon Sep 28 05:49:12 +0000 2020

In our documentation, you can learn 4 different ways to get hassle-free, automatic HTTPS in less than 2 minutes: -… https://t.co/ZwEv5NCtlV
Mon Sep 28 05:46:19 +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.

CVE-2018-21246 is exploitable with network access, and does not require authorization privledges or user interaction. This vulnerability is considered to have a low attack complexity. It has the highest possible exploitability rating (3.9). The potential impact of an exploit of this vulnerability is considered to be critical as this vulneraility has a high impact to the confidentiality, integrity and availability of this component.

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.

CVE-2018-19148 is exploitable with network access, and does not require authorization privledges or user interaction. This vulnerability is consided to have a high level of attack complexity. It has an exploitability score of 2.2 out of four. The potential impact of an exploit of this vulnerability is considered to have a small impact on confidentiality, a small impact on integrity and availability.

Information Leak