Bypasses / Path restriction
Path restriction
109 cases that got past this protection.
- mlflow vulnerable to Path Traversal Double URL decoding in artifact deletion lets encoded traversal sequences escape path validation and delete arbitrary server directories.
- 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.
- LangChain directory traversal vulnerability A ../ sequence in the load_chain path escapes the hub-only directory, letting attackers load configuration from arbitrary locations.
- Onnx Directory Traversal vulnerability An ONNX tensor's external_data path can point outside the model directory, getting around the earlier fix and reading arbitrary files during model loading.
- 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.