You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Peter Rozovski (Jira)" <ji...@apache.org> on 2019/09/16 20:24:00 UTC
[jira] [Comment Edited] (IO-559) FilenameUtils.normalize should
verify hostname syntax in UNC path
[ https://issues.apache.org/jira/browse/IO-559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16930820#comment-16930820 ]
Peter Rozovski edited comment on IO-559 at 9/16/19 8:23 PM:
------------------------------------------------------------
Gary - thank you! It would be really great to get COMMONS-IO 2.7 release production version.
was (Author: prozovski):
Gary - thank you! It would be really great to get COMMONS-IO 2.7 production version.
> FilenameUtils.normalize should verify hostname syntax in UNC path
> -----------------------------------------------------------------
>
> Key: IO-559
> URL: https://issues.apache.org/jira/browse/IO-559
> Project: Commons IO
> Issue Type: Bug
> Components: Utilities
> Affects Versions: 2.6
> Reporter: Stefan Bodewig
> Priority: Major
> Fix For: 2.7
>
>
> {{FilenameUtils.normalize}} will accept broken file names as UNC path even if their hostname part doesn't match the syntax of a proper hostname. Using certain hostnames like "." this may lead to strange side effects.
> Most likely the best fix will be to make {{getPrefixLength}} verify the hostname part of a suspected UNC path and return a value of {{NOT_FOUND}} if it is not a valid hostname - much like it does for triple slashes.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)