CVE-2018-19148
Last modified
CVE-2018-19148 is a vulnerability of currently unknown severity. 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. EPSS estimates a 0.86% chance of exploitation in the next 30 days.
Description
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Caddyserver | Caddy | <= 0.11.0 |
References
- https://github.com/mholt/caddy/issues/1303Issue Tracking, Patch, Third Party Advisory
- https://github.com/mholt/caddy/issues/2334Issue Tracking, Patch, Third Party Advisory
- https://github.com/mholt/caddy/pull/2015Issue Tracking, Patch, Third Party Advisory
- https://securitytrails.com/blog/caddy-web-server-ssl-bugExploit, Patch, Third Party Advisory
- https://github.com/mholt/caddy/issues/1303Issue Tracking, Patch, Third Party Advisory
- https://github.com/mholt/caddy/issues/2334Issue Tracking, Patch, Third Party Advisory
- https://github.com/mholt/caddy/pull/2015Issue Tracking, Patch, Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2018-19148?
How severe is CVE-2018-19148?
How do I fix CVE-2018-19148?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2018
- CVE-2018-1914IBM Rational Engineering Lifecycle Manager 5.0 through 6.0.6…5.4
- CVE-2018-19141Open Ticket Request System (OTRS) 4.0.x before 4.0.33 and 5.…
- CVE-2018-19142Open Ticket Request System (OTRS) 6.0.x before 6.0.13 allows…
- CVE-2018-19143Open Ticket Request System (OTRS) 4.0.x before 4.0.33, 5.0.x…
- CVE-2018-19145An issue was discovered in S-CMS v1.5. There is an XSS vulne…
- CVE-2018-19146Concrete5 8.4.3 has XSS because config/concrete.php allows u…
- CVE-2018-19149Poppler before 0.70.0 has a NULL pointer dereference in _pop…
- CVE-2018-19150Memory corruption in PDMODELProvidePDModelHFT in pdmodel.dll…
- CVE-2018-19151qtum through 0.16 (a chain-based proof-of-stake cryptocurren…7.5
- CVE-2018-19152emercoin through 0.7 (a chain-based proof-of-stake cryptocur…7.5
- CVE-2018-19153particl through 0.17 (a chain-based proof-of-stake cryptocur…7.5
- CVE-2018-19154HTMLCOIN through 2.12 (a chain-based proof-of-stake cryptocu…7.5
Are you affected by CVE-2018-19148?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
