github_osv/GHSA-gwrp-pvrq-jmwv
Path Traversal and Improper Input Validation in Apache Commons IO
In Apache Commons IO before 2.7, When invoking the method FileNameUtils.normalize with an improper input string, like "//../foo", or "\\..\foo", the result would be the same value, thus possibly providing access to files in the parent directory, but not further above (thus "limited" path traversal), if the calling code would use the result to construct a path value.
gitlab/maven/com.cosium.vet/vet/CVE-2021-29425
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
In Apache Commons IO before 2.7, When invoking the method FileNameUtils.normalize with an improper input string, like "//../foo", or "\\..\foo", the result would be the same value, thus possibly providing access to files in the parent directory, but not further above (thus "limited" path traversal), if the calling code would use the result to construct a path value.
gitlab/maven/com.diamondq.common/common-thirdparty.jcasbin/CVE-2021-29425
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
In Apache Commons IO before 2.7, When invoking the method FileNameUtils.normalize with an improper input string, like "//../foo", or "\\..\foo", the result would be the same value, thus possibly providing access to files in the parent directory, but not further above (thus "limited" path traversal), if the calling code would use the result to construct a path value.
gitlab/maven/com.liferay/com.liferay.sass.compiler.jsass/CVE-2021-29425
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
In Apache Commons IO before 2.7, When invoking the method FileNameUtils.normalize with an improper input string, like "//../foo", or "\\..\foo", the result would be the same value, thus possibly providing access to files in the parent directory, but not further above (thus "limited" path traversal), if the calling code would use the result to construct a path value.
gitlab/maven/commons-io/commons-io/CVE-2021-29425
Path Traversal
In Apache Commons IO, When invoking the method `FileNameUtils.normalize` with an improper input string, the result would be the same value, thus possibly providing access to files in the parent directory, but not further above, if the calling code would use the result to construct a path value.
gitlab/maven/com.virjar/ratel-api/CVE-2021-29425
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
In Apache Commons IO before 2.7, When invoking the method FileNameUtils.normalize with an improper input string, like "//../foo", or "\\..\foo", the result would be the same value, thus possibly providing access to files in the parent directory, but not further above (thus "limited" path traversal), if the calling code would use the result to construct a path value.
gitlab/maven/io.helidon/helidon-dependencies/CVE-2021-29425
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
In Apache Commons IO before 2.7, When invoking the method FileNameUtils.normalize with an improper input string, like "//../foo", or "\\..\foo", the result would be the same value, thus possibly providing access to files in the parent directory, but not further above (thus "limited" path traversal), if the calling code would use the result to construct a path value.
gitlab/maven/net.hasor/cobble-lang/CVE-2021-29425
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
In Apache Commons IO before 2.7, When invoking the method FileNameUtils.normalize with an improper input string, like "//../foo", or "\\..\foo", the result would be the same value, thus possibly providing access to files in the parent directory, but not further above (thus "limited" path traversal), if the calling code would use the result to construct a path value.
gitlab/maven/org.apache.commons/commons-io/CVE-2021-29425
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
In Apache Commons IO before 2.7, When invoking the method FileNameUtils.normalize with an improper input string, like "//../foo", or "\\..\foo", the result would be the same value, thus possibly providing access to files in the parent directory, but not further above (thus "limited" path traversal), if the calling code would use the result to construct a path value.
gitlab/maven/org.apache.servicemix.bundles/org.apache.servicemix.bundles.commons-io/CVE-2021-29425
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
In Apache Commons IO before 2.7, When invoking the method FileNameUtils.normalize with an improper input string, like "//../foo", or "\\..\foo", the result would be the same value, thus possibly providing access to files in the parent directory, but not further above (thus "limited" path traversal), if the calling code would use the result to construct a path value.
gitlab/maven/org.checkerframework.annotatedlib/commons-io/CVE-2021-29425
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
In Apache Commons IO before 2.7, When invoking the method FileNameUtils.normalize with an improper input string, like "//../foo", or "\\..\foo", the result would be the same value, thus possibly providing access to files in the parent directory, but not further above (thus "limited" path traversal), if the calling code would use the result to construct a path value.
gitlab/maven/org.smartboot.servlet/servlet-core/CVE-2021-29425
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
In Apache Commons IO before 2.7, When invoking the method FileNameUtils.normalize with an improper input string, like "//../foo", or "\\..\foo", the result would be the same value, thus possibly providing access to files in the parent directory, but not further above (thus "limited" path traversal), if the calling code would use the result to construct a path value.