Caddy Server Caddy Web Server HTTP / HTTPS Server

stack.watch can email 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

All the funny business going on with HTTP. https://t.co/AoJ4xZRFx6
Fri Mar 05 01:28:10 +0000 2021

How cool would it be if your web server used HTTPS by default, too! https://t.co/lpu8LN0AFO
Thu Mar 04 20:35:45 +0000 2021

RT @Fergydanny: oh my, just discovered @caddyserver so much simpler than nginx or apache!! its so nice for deploying a bunch of sites with…
Thu Mar 04 02:11:41 +0000 2021

RT @mholt6: Are there any companies using Caddy -- or which have customers using Caddy -- that are interested in an open source *distribute…
Wed Mar 03 21:01:12 +0000 2021

Caddy now available in the Arch Linux repositories: https://t.co/jXFc6QsKid
Wed Mar 03 00:44:58 +0000 2021

By the Year

In 2021 there have been 0 vulnerabilities in Caddy Server Caddy Web Server . Last year Caddy Web Server had 1 security vulnerability published. Right now, Caddy Web Server is on track to have less security vulnerabilities in 2021 than it did last year.

Year	Vulnerabilities	Average Score
2021	0	0.00
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