breakKeepAliveLoop
Defined in 3 files
Last patched
Overview
breakKeepAliveLoop in apache/tomcat was changed by 2 published CVE fixes in 2017, in 4 distinct patches that added or removed 45 lines in total.
Defined in 3 files
Last patched
breakKeepAliveLoop in apache/tomcat was changed by 2 published CVE fixes in 2017, in 4 distinct patches that added or removed 45 lines in total.
The name occurs in 3 files: java/org/apache/coyote/http11/Http11AprProcessor.java, java/org/apache/coyote/http11/Http11Processor.java, java/org/apache/coyote/http11/Http11NioProcessor.java.
apache/tomcat has 135 CVEs with a located fix in total, so 1% of them touched this function.
Every published CVE whose fix changed breakKeepAliveLoop, newest first, with the lines each fix touched.
CVE-2017-5647 · java/org/apache/coyote/http11/Http11AprProcessor.java · lines 215–223 · +9 −1
CVE-2017-5647 · java/org/apache/coyote/http11/Http11NioProcessor.java · lines 279–287 · +9 −1
CVE-2017-5651 · java/org/apache/coyote/http11/Http11Processor.java · lines 1305–1329 · +11 −14
Get an alert when the next CVE fix lands in apache/tomcat, with the patched functions.
Monitor tomcat CVEsFunctions in the same files that CVE fixes also changed.
Functions in apache/tomcat changed by the most CVE fixes.
Common questions about CVE fixes to breakKeepAliveLoop.
Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.
Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.