Browse / AI Framework and Platform Flaws / Path traversal and file access
Path traversal and file access
192 records in AI Framework and Platform Flaws.
- MLflow has a Local File Read/Path Traversal bypass A hash fragment in an artifact URL slips past the earlier path check, letting the server resolve and read arbitrary local files.
- gradio vulnerable to Path Traversal The component endpoint lets callers invoke a block method that copies arbitrary host files into a cache directory, which they can then download.
- langchain vulnerable to path traversal Path traversal sequences in keys passed to LocalFileStore escape its root directory, letting callers read or write arbitrary files.
- mlflow vulnerable to Path Traversal Double URL decoding in artifact deletion lets encoded traversal sequences escape path validation and delete arbitrary server directories.
- mlflow vulnerable to Path Traversal Semicolons in request URLs smuggle path traversal sequences into the params portion, letting attackers reach files outside the intended directory.
- mlflow Path Traversal vulnerability Crafted artifact_location and source values using a '#' local URI bypass insufficient path validation, letting requests read arbitrary server files.
- mlflow vulnerable to Path Traversal Local-path detection mishandles empty or file-scheme URIs, so crafted model version sources are treated as non-local and can read arbitrary files.
- mlflow vulnerable to Path Traversal A crafted source parameter slips past the relative-path check during model version creation, letting attackers read arbitrary server files via the artifact handler.
- mlflow vulnerable to Path Traversal A fragment character in the artifact location makes the server resolve paths past checks meant to stop traversal, reading arbitrary files.
- Directory traversal in zenml The steps endpoint's logs URI accepts traversal sequences, letting callers read files outside the intended directory.
- PaddlePaddle allows arbitrary file read via paddle.vision.ops.read_file The read_file operation opens arbitrary filesystem paths supplied to it, letting a caller read any file the process can access.
- PaddlePaddle Path Traversal vulnerability Path traversal sequences in a file path let attackers overwrite files outside the intended directory.
- LangChain directory traversal vulnerability A ../ sequence in the load_chain path escapes the hub-only directory, letting attackers load configuration from arbitrary locations.
- Allegro AI ClearML path traversal vulnerability A dataset with crafted file paths makes the ClearML client SDK write files to arbitrary locations on the user's system.
- Gradio Path Traversal vulnerability A crafted JSON value in a Gradio API request makes the server include and read an arbitrary local file.
- Gradio makes the `/file` secure against file traversal and server-side request forgery attacks Raw HTTP tools could read arbitrary server files and make server-side requests through Gradio's file route, which browser-style URLs could not reach.
- MLflow Path Traversal Vulnerability Filenames containing backslash-dot traversal sequences let a request escape the intended directory and reach other files on the server.
- MLflow Local File Disclosure Vulnerability The MLflow server lets users read arbitrary local files on the host, exposing sensitive server data.
- MLflow Path Traversal Vulnerability The server accepts uploads that write arbitrary files to arbitrary locations on the remote filesystem, using the server process's permissions.
- GitHub Security Lab (GHSL) Vulnerability Report: Arbitary write GHSL-2023-182 A file write operation accepts unvalidated paths, letting attackers create or overwrite files outside the intended directory.
- Path traversal in MLflow A filename containing backslash-dot sequences escapes the intended directory during file handling in MLflow.
- External Control of File Name or Path in h2oai/h2o-3 Unauthenticated requests can make the h2o export write to attacker-chosen paths, overwriting arbitrary server files with attacker-shaped content.
- Path traversal in MLflow Crafted path arguments in MLflow escape the intended directory, letting requests read or write files outside it.
- Improper Input Validation in mindsdb A user-supplied name is used unvalidated in a temporary file path, letting a request write files to arbitrary server locations.
- TorchServe ZipSlip Model archives uploaded through the management API are extracted without checking entry paths, so crafted zip entries can write outside the target directory.
- H2O local file inclusion vulnerability Unauthenticated requests to the import and parse setup endpoints let callers read arbitrary files the server process can access.
- MLflow allowed arbitrary files to be PUT onto the server MLflow accepts file uploads written to arbitrary server paths without restricting the destination to an allowed directory.
- Ray Path Traversal vulnerability The unauthenticated log API endpoint accepts file paths without restriction, letting callers read arbitrary files on the server.
- Ray Missing Authorization vulnerability The static file route accepts traversal sequences, letting unauthenticated requests read arbitrary files on the server.
- MLflow Path Traversal vulnerability Absolute file paths supplied to MLflow are not confined, so crafted input can reach files outside the intended directory.
- Gradio vulnerable to arbitrary file read and proxying of arbitrary URLs Shared Gradio apps let remote users read arbitrary files on the host and use the host to proxy requests to arbitrary URLs.
- mlflow Path Traversal vulnerability An incomplete fix for an earlier MLflow path traversal flaw leaves a bypass that reaches files outside the intended directory.
- mflow vulnerable to directory traversal The MLflow get-artifact endpoint takes an unrestricted path parameter, so traversal sequences let callers read arbitrary files on the server.
- n8n Directory Traversal vulnerability Crafted path sequences in the n8n workflow platform let a user reach files outside the intended directory; the advisory gives few specifics.
- Remote file access vulnerability in `mlflow server` and `mlflow ui` CLIs Older mlflow server and ui releases let remote callers reach arbitrary host files through crafted artifact paths when the server is not access-restricted.
- Relative path traversal in mlflow MLflow before 2.3.1 does not sanitise relative path sequences, letting callers reach files outside the intended directory.
- mindsdb arbitrary file write when extracting a remotely retrieved Tarball Extracting a remotely fetched tarball with extractall lets entries with traversal paths write files outside the intended directory.
- Arbitrary file write in mindsdb when Extracting Tarballs retrieved from a remote location Extracting a remotely fetched tarball with shutil.unpack_archive without path checks lets entries write outside the intended directory.
- Nginx alias path traversal allows unauthenticated attackers to read all files on /label_studio/core/ An off-by-one missing trailing slash in the default Nginx static location lets a traversal path reach the parent directory and its files.
- mlflow is vulnerable to remote file access in `mlflow server` and `mlflow ui` CLIs A remote caller can request files outside the intended directory from the MLflow server, reading arbitrary host files that the server can access.
- Files on the host computer can be accessed from the Gradio interface Older Gradio versions served static files without path checks, so anyone with a public link could read host files by path.
- Internal machine learning API endpoint for CWE classification is vulnerable to path traversal