CVE-2019-0207: Path traversal attack on Windows platforms in org.apache.tapestry:tapestry-core

Summary

18/11/2019
Yes i
High
7.5

CVE-2019-0207: Path traversal attack on Windows platforms. Affects org.apache.tapestry:tapestry-core versions >= 5.4.0, < 5.4.5. Fixed in 5.4.5. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

org.apache.tapestry:tapestry-core is a Maven package that provides core functionality for the Tapestry web application framework. It includes classes and utilities for handling assets, such as the StaticFilesFilter, AssetDispatcher, and ContextResource. These components are responsible for processing and serving static assets in a Tapestry application.

Vulnerability Detail

The vulnerability (CVE-2019-0207) arises from a path traversal attack that can be performed on Windows platforms. The issue lies in the way Tapestry processes assets using the classes chain StaticFilesFilter -> AssetDispatcher -> ContextResource. These classes do not properly filter the character '', allowing an attacker to traverse the file system and read any files on a Windows platform. This can lead to unauthorized access to sensitive information and potential compromise of the system.

How To Fix

Latest published version: 5.9.1 as of 22 Oct 2026

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

5.4.5

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

If upgrading the package is not immediately feasible, a temporary workaround is to implement a custom filter or interceptor that sanitizes the asset paths and prevents path traversal attacks. Here is an example of a filter that can be used:

import javax.servlet.*;
import javax.servlet.http.HttpServletRequest;
import java.io.IOException;

public class AssetPathFilter implements Filter {

    @Override
    public void init(FilterConfig filterConfig) throws ServletException {
        // Initialization code
    }

    @Override
    public void doFilter(ServletRequest request, ServletResponse response, FilterChain chain) throws IOException, ServletException {
        HttpServletRequest httpRequest = (HttpServletRequest) request;
        String assetPath = httpRequest.getParameter("assetPath");
        if (assetPath != null && assetPath.contains("\\")) {
            // Handle the path traversal attack
            // Log or block the request
        }
        chain.doFilter(request, response);
    }

    @Override
    public void destroy() {
        // Cleanup code
    }
}

This filter intercepts requests and checks if the "assetPath" parameter contains the '' character. If it does, appropriate actions can be taken, such as logging the request or blocking it.

Conclusion

In conclusion, the org.apache.tapestry:tapestry-core package is vulnerable to a path traversal attack on Windows platforms. This can lead to unauthorized access to sensitive files and potential compromise of the system. It is recommended to upgrade to version 5.4.5 or later to fix this vulnerability. If immediate upgrade is not possible, implementing a custom filter or interceptor can provide a temporary workaround. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for org.apache.tapestry:tapestry-core →

Share this vulnerability

FAQ

org.apache.tapestry:tapestry-core is a Maven package that provides core functionality for the Tapestry web application framework. It includes classes and utilities for handling assets and serving static files.

A path traversal attack, also known as directory traversal or directory climbing, is a web security vulnerability that allows an attacker to access files and directories outside of the intended directory structure. It occurs when user input is not properly sanitized or validated, allowing attackers to manipulate file paths and access sensitive information.

This vulnerability can allow an attacker to read any files on a Windows platform, potentially leading to unauthorized access to sensitive information. It can also be used as a stepping stone for further attacks, such as remote code execution or data exfiltration.

No, only versions 5.4.0 to 5.4.4 of org.apache.tapestry:tapestry-core are affected by this vulnerability. Versions 5.4.5 and later include the necessary fixes to prevent path traversal attacks on Windows platforms.

You can use Vulert's playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability. Simply provide your pom.xml file, and Vulert will analyze it in real-time and alert you if any open-source vulnerabilities, including this one, are found.

Related vulnerabilities

Recent vulnerabilities recorded for org.apache.tapestry:tapestry-core.

How To Fix

Latest published version: 5.9.1 as of 22 Oct 2026

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

5.4.5

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback