How many CVEs have patched assertConfigsCompatible?

2 published CVEs changed assertConfigsCompatible in caddyserver/caddy, in 2 distinct patches totalling 65 changed lines, between 2018 and 2020.

What is the latest CVE that changed assertConfigsCompatible?

CVE-2018-21246 (Caddy vulnerable to Authentication Bypass due to mishandling of TLS client authentication), published 2020-06-15, changed lines 516 to 523 of caddytls/config.go.

How does assertConfigsCompatible compare to the rest of caddyserver/caddy?

caddyserver/caddy has 13 CVEs with a located fix in total; 2 of them changed assertConfigsCompatible.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Log in Create an account

caddyserver/caddy

Function

assertConfigsCompatible

Name: assertConfigsCompatible in caddyserver/caddy: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

caddytls/config.go

Last patched June 15, 2020

2

CVEs

That changed this function

2

Distinct patches

Backports counted once

65

Lines changed

Added plus removed

2018–2020

Years

By CVE publication date

Overview

assertConfigsCompatible in caddyserver/caddy was changed by 2 published CVE fixes between 2018 and 2020, in 2 distinct patches that added or removed 65 lines in total.

caddyserver/caddy has 13 CVEs with a located fix in total, so 15% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed assertConfigsCompatible, newest first, with the lines each fix touched.

Caddy vulnerable to Authentication Bypass due to mishandling of TLS client authentication
CVE-2018-21246 · lines 516–523 · +8 −0
Critical · CVSS 9.8
EPSS 2.7%2020-06-15
Caddy allows enumeration of Certificates and Hostnames
CVE-2018-19148 · lines 426–482 · +57 −0
Low · CVSS 3.7
EPSS 0.9%2018-11-10

Get an alert when the next CVE fix lands in caddyserver/caddy, with the patched functions.

Monitor caddy CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

Other hotspots in the repository

Functions in caddyserver/caddy changed by the most CVE fixes.

Rewrite2 CVEs · modules/caddyhttp/rewrite/rewrite.go trapSignalsPosix2 CVEs · sigtrap_posix.go serveHTTP2 CVEs · caddyhttp/httpserver/server.go parseCaddyfile1 CVEs · modules/caddyhttp/reverseproxy/forwardauth/caddyfile.go getCertificate1 CVEs · caddytls/handshake.go getConfig1 CVEs · caddytls/handshake.go

All patched functions in caddyserver/caddy

Frequently asked questions

Common questions about CVE fixes to assertConfigsCompatible.

How many CVEs have patched assertConfigsCompatible?: 2 published CVEs changed assertConfigsCompatible in caddyserver/caddy, in 2 distinct patches totalling 65 changed lines, between 2018 and 2020.
What is the latest CVE that changed assertConfigsCompatible?: CVE-2018-21246 (Caddy vulnerable to Authentication Bypass due to mishandling of TLS client authentication), published 2020-06-15, changed lines 516 to 523 of caddytls/config.go.
How does assertConfigsCompatible compare to the rest of caddyserver/caddy?: caddyserver/caddy has 13 CVEs with a located fix in total; 2 of them changed assertConfigsCompatible.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track caddyserver/caddy CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing