More information about this security flaw is available in the following bug:
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.
Use the following template to for the 'fedpkg update' request to submit an
update for this issue as it contains the top-level parent bug(s) as well as
this tracking bug. This will ensure that all associated bugs get updated
when new packages are pushed to stable.
# bugfix, security, enhancement, newpackage (required)
# low, medium, high, urgent (required)
# testing, stable
# Bug numbers: 1234,9876
# Description of your update
notes=Security fix for [PUT CVEs HERE]
# Enable request automation based on the stable/unstable karma thresholds
# Automatically close bugs when this marked as stable
# Suggest that users restart after update
Additionally, you may opt to use the bodhi web interface to submit updates:
The parent bug and upstream report indicate that the vulnerability exists prior to version 2.2.4.
epel9 has caddy 2.4.6, which vendors yaml 2.4.0, so it's not affected.
epel8 doesn't have caddy, so it's not affected.
epel7 has caddy 1.0.3, which vendors yaml 2.2.2, so it is affected.
FEDORA-EPEL-2023-284c34a6cc has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-284c34a6cc
FEDORA-EPEL-2023-284c34a6cc has been pushed to the Fedora EPEL 7 testing repository.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-284c34a6cc
See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2023-284c34a6cc has been pushed to the Fedora EPEL 7 stable repository.
If problem still persists, please make note of it in this bug report.
For posterity, this update ended up being broken and nobody (myself included) caught it while it was in the testing repo. It's no longer possible to build caddy v1 with the golang that is in EPEL 7. The choice was between an incompatible update to caddy v2 (major breaking changes with a new config file format) or retiring the package. With only 10 months left until EPEL 7 is retired, I decided to go with the latter. See this email for more details.