Fixed packages 7
| Release | Package | Fixed in |
|---|---|---|
| Red Hat · RHEL 9 enterprise_linux:9::appstream | go-toolset | 0:1.20.10-1.el9_3 |
| Red Hat · RHEL 9 enterprise_linux:9::appstream | golang | 0:1.20.10-1.el9_3 |
| Red Hat · RHEL 9 enterprise_linux:9::appstream | golang-bin | 0:1.20.10-1.el9_3 |
| Red Hat · RHEL 9 enterprise_linux:9::appstream | golang-docs | 0:1.20.10-1.el9_3 |
| Red Hat · RHEL 9 enterprise_linux:9::appstream | golang-misc | 0:1.20.10-1.el9_3 |
| Red Hat · RHEL 9 enterprise_linux:9::appstream | golang-src | 0:1.20.10-1.el9_3 |
| Red Hat · RHEL 9 enterprise_linux:9::appstream | golang-tests | 0:1.20.10-1.el9_3 |
Vulnerabilities 4
-
Unscored —
Improper handling of HTML-like comments in script contexts in html/template
The html/template package does not properly handle HTML-like "" comment tokens, nor hashbang "#!" comment tokens, in <script> contexts. This may cause the template parser to improperly interpret the contents of <script> contexts, causing actions to be imprope…
-
Unscored —
Improper handling of special tags within script contexts in html/template
The html/template package does not apply the proper rules for handling occurrences of "<script", "<!--", and "</script" within JS literals in <script> contexts. This may cause the template parser to improperly consider script contexts to be terminated early, …
-
Unscored —
Panic when processing post-handshake message on QUIC connections in crypto/tls
Processing an incomplete post-handshake message for a QUIC connection can cause a panic.
-
Unscored —
Memory exhaustion in QUIC connection handling in crypto/tls
QUIC connections do not set an upper bound on the amount of data buffered when reading post-handshake messages, allowing a malicious QUIC connection to cause unbounded memory growth. With fix, connections now consistently reject messages larger than 65KiB in …
References
-
article
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/9.3_release_notes/index
-
report
https://bugzilla.redhat.com/show_bug.cgi?id=2098211
-
report
https://bugzilla.redhat.com/show_bug.cgi?id=2116995
-
report
https://bugzilla.redhat.com/show_bug.cgi?id=2117248
-
report
https://bugzilla.redhat.com/show_bug.cgi?id=2167409
-
report
https://bugzilla.redhat.com/show_bug.cgi?id=2186496
-
report
https://bugzilla.redhat.com/show_bug.cgi?id=2190184
-
report
https://bugzilla.redhat.com/show_bug.cgi?id=2230705
-
advisory
https://security.access.redhat.com/data/csaf/v2/advisories/2023/rhba-2023_6364.json
-
report
https://access.redhat.com/security/cve/CVE-2023-39318
-
report
https://bugzilla.redhat.com/show_bug.cgi?id=2237776
-
advisory
https://www.cve.org/CVERecord?id=CVE-2023-39318
-
advisory
https://nvd.nist.gov/vuln/detail/CVE-2023-39318
-
article
https://go.dev/cl/526156
-
article
https://go.dev/issue/62196
-
article
https://groups.google.com/g/golang-dev/c/2C5vbR-UNkI/m/L1hdrPhfBAAJ
-
article
https://vuln.go.dev/ID/GO-2023-2041.json
-
report
https://access.redhat.com/security/cve/CVE-2023-39319
-
report
https://bugzilla.redhat.com/show_bug.cgi?id=2237773
-
advisory
https://www.cve.org/CVERecord?id=CVE-2023-39319
-
advisory
https://nvd.nist.gov/vuln/detail/CVE-2023-39319
-
article
https://go.dev/cl/526157
-
article
https://go.dev/issue/62197
-
article
https://vuln.go.dev/ID/GO-2023-2043.json
-
report
https://access.redhat.com/security/cve/CVE-2023-39321
-
report
https://bugzilla.redhat.com/show_bug.cgi?id=2237777
-
advisory
https://www.cve.org/CVERecord?id=CVE-2023-39321
-
advisory
https://nvd.nist.gov/vuln/detail/CVE-2023-39321
-
article
https://go.dev/cl/523039
-
article
https://go.dev/issue/62266
-
article
https://vuln.go.dev/ID/GO-2023-2044.json
-
report
https://access.redhat.com/security/cve/CVE-2023-39322
-
report
https://bugzilla.redhat.com/show_bug.cgi?id=2237778
-
advisory
https://www.cve.org/CVERecord?id=CVE-2023-39322
-
advisory
https://nvd.nist.gov/vuln/detail/CVE-2023-39322
-
article
https://vuln.go.dev/ID/GO-2023-2045.json