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

Do you want an email whenever new security vulnerabilities are reported in Caddy Server Caddy Web Server?

@caddyserver Tweets

RT @itstelesphoreo: The three magical lines you need to get a basic website running with HTTPS on @caddyserver. Gone are the days of spendi…
Mon May 17 19:56:31 +0000 2021

RT @baakeydow: Inspect @caddyserver logs with @goaccess full simple #tutorial step by step guide => https://t.co/FnXixDQorC | #buildinpubli…
Sat May 15 23:37:13 +0000 2021

See how @QueryCal is using Caddy load balancing to do A/B testing... with just 3 lines of config. https://t.co/KPD2aYCG9l
Sat May 15 03:31:57 +0000 2021

RT @letsencrypt: How do you know that you need HTTPS? Here’s a handy guide! https://t.co/kKSF8TZSmj
Tue May 11 21:14:11 +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 in the stats or in the list of recent security vulnerabilties. Additionally vulnerabilities may be tagged under a different product or component name.

Recent 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 Disclosure

Stay on top of Security Vulnerabilities

Want an email whenever new vulnerabilities are published for Caddy Server Caddy Web Server or by Caddy Server? Click the Watch button to subscribe.

Caddy Server Caddy Web Server
HTTP / HTTPS Server

subscribe