More information about this security flaw is available in the following bug: https://bugzilla.redhat.com/show_bug.cgi?id=2333122 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.
I defer to Peter Hunt on this potential vulnerability as I do not know what use EPEL 8 has internally in RedHat. My analysis: A scan by govulcheck (see https://github.com/golang/vuln) on cri-o v1.21 indicates that cri-o does not appear to be vulnerable. GO-2024-3333 is the Go vulnerability database analog to CVE-2024-45338. Full results: cri-o [ release-1.21][✘?] ❯ govulncheck --show verbose ./... Scanning your code and 1370 packages across 218 dependent modules for known vulnerabilities... Fetching vulnerabilities from the database... Checking the code against the vulnerabilities... === Symbol Results === No vulnerabilities found. === Package Results === Vulnerability #1: GO-2024-3333 Non-linear parsing of case-insensitive content in golang.org/x/net/html More info: https://pkg.go.dev/vuln/GO-2024-3333 Module: golang.org/x/net Found in: golang.org/x/net.0 Fixed in: golang.org/x/net.0 Vulnerability #2: GO-2024-3321 Misuse of ServerConfig.PublicKeyCallback may cause authorization bypass in golang.org/x/crypto More info: https://pkg.go.dev/vuln/GO-2024-3321 Module: golang.org/x/crypto Found in: golang.org/x/crypto.0 Fixed in: golang.org/x/crypto.0 === Module Results === No other vulnerabilities found. Your code is affected by 0 vulnerabilities. This scan also found 2 vulnerabilities in packages you import and 0 vulnerabilities in modules you require, but your code doesn't appear to call these vulnerabilities. cri-o [ release-1.21][✘?] ❯