The vulnerability stems from improper handling of user-supplied 'file' parameters in the log viewer endpoint. The description explicitly mentions exploitation via '..' in the file parameter to log, which matches classic path traversal patterns. The JIRA ticket STORM-269 and CWE-22 classification confirm this is a path sanitation failure in log file handling. While no patch diff is available, Storm's architecture suggests the log viewer functionality is implemented in LogResource class (common pattern in Java web apps), and the function name 'serveLogFile' aligns with standard REST resource method naming conventions for file serving endpoints.