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.
References
Link | Resource |
---|---|
https://github.com/mholt/caddy/issues/1303 | Issue Tracking Patch Third Party Advisory |
https://github.com/mholt/caddy/issues/2334 | Issue Tracking Patch Third Party Advisory |
https://github.com/mholt/caddy/pull/2015 | Issue Tracking Patch Third Party Advisory |
https://securitytrails.com/blog/caddy-web-server-ssl-bug | Exploit Patch Third Party Advisory |
Configurations
History
No history.
Information
Published : 2018-11-10 19:29
Updated : 2024-02-04 20:03
NVD link : CVE-2018-19148
Mitre link : CVE-2018-19148
CVE.ORG link : CVE-2018-19148
JSON object : View
Products Affected
caddyserver
- caddy
CWE
CWE-200
Exposure of Sensitive Information to an Unauthorized Actor