Defined in 2 files
Last patched
isInvalidWindowsFilename in apache/tomcat was changed by 2 published CVE fixes between 2017 and 2021, in 8 distinct patches that added or removed 62 lines in total.
The name occurs in 2 files: java/org/apache/catalina/webresources/AbstractFileResourceSet.java, java/org/apache/naming/resources/FileDirContext.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 isInvalidWindowsFilename, newest first, with the lines each fix touched.
CVE-2021-24122 · java/org/apache/catalina/webresources/AbstractFileResourceSet.java · line 164 · +1 −1
CVE-2021-24122 · java/org/apache/naming/resources/FileDirContext.java · line 916 · +1 −1
CVE-2017-12617 · java/org/apache/catalina/webresources/AbstractFileResourceSet.java · lines 137–164 · +28 −0
CVE-2017-12617 · java/org/apache/naming/resources/FileDirContext.java · lines 889–918 · +30 −0
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 isInvalidWindowsFilename.
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.
