Browse / AI Framework and Platform Flaws / Information exposure
Information exposure
78 records in AI Framework and Platform Flaws.
- LangChain Text Splitters is vulnerable to XML External Entity (XXE) attacks due to unsafe XSLT parsing Developer-supplied XSLT stylesheets are parsed without hardening, so external entities or document() calls can read local files or fetch URLs.
- Langchain Community Vulnerable to XML External Entity (XXE) Attacks The Evernote loader parses attacker-supplied XML with external entities enabled, letting it read local files such as system password files.
- Ollama vulnerable to Cross-Domain Token Exposure A malicious WWW-Authenticate realm makes the client send its stored bearer token to an attacker-chosen host during a registry pull.
- Gradio CORS Origin Validation Bypass Vulnerability A flaw in localhost alias handling in the CORS origin check lets a disallowed origin pass validation and read responses from the server.
- Data exposure via ZeroMQ on multi-node vLLM deployment A multi-node vLLM host binds an internal publish socket to all interfaces, so any reachable client receives broadcast internal state.
- AgentScope Cross-Origin Resource Sharing (CORS) vulnerability The server returns permissive cross-origin headers for any origin, so untrusted websites can read API responses from a visitor's browser.
- Feast Cross-Origin Resource Sharing vulnerability CORS settings accept any origin, so a third-party site can read API responses from a logged-in user's browser.
- unstructured XML External Entity (XXE) Parsing a crafted XML document resolves external entities, letting the parser read local files or internal resources.
- Gradio uses insecure communication between the FRP client and server The tunnel used by share=True runs without enforced HTTPS, so an on-path observer can read uploaded files and modify traffic.
- Gradio's CORS origin validation accepts the null origin The localhost origin list includes the null origin, so sandboxed iframes can make cross-origin requests and read the responses.
- In Gradio, the `enable_monitoring` flag set to `False` does not disable monitoring Setting enable_monitoring to False does not block the /monitoring endpoint, so anyone who requests it can see application analytics.
- Flowise Cors Misconfiguration in packages/server/src/index.ts Flowise sends a wildcard CORS header, letting any origin read responses, and chained path injection can expose arbitrary server files.
- Guardrails AI vulnerable to Improper Restriction of XML External Entity Reference Guardrails parses attacker-supplied RAIL XML with external entities enabled, so a SYSTEM entity can read local files.
- Arbitrary system path lookup in h20 The typeahead lookup accepts a root path and returns filesystem directory listings to remote users without restriction.
- Gradio allows credential leakage on Windows Gradio releases before 4.20 leak credentials when running on Windows, with the advisory giving no further mechanism detail.
- Allegro AI ClearML Stores Credentials in Plaintext in MongoDB Instance ClearML stores user passwords in plaintext in its MongoDB backend, so anyone who reads the database obtains working credentials.
- Gradio Exposure of Sensitive Information to an Unauthorized Actor vulnerability Gradio exposes sensitive information to actors who should not receive it; the advisory gives no further technical detail.
- Information exposure in MLflow A crafted request to the MLflow REST API lets a remote attacker retrieve sensitive information from versions up to 2.8.1.
- Label Studio Object Relational Mapper Leak Vulnerability in Filtering Task Filter paths that traverse Django relations let the task filter reveal sensitive fields such as password hashes one character at a time.
- MindsDB can be made to not verify SSL certificates MindsDB code paths disable certificate checks, so traffic to connected services can be intercepted without detection.
- n8n Information Disclosure vulnerability The advisory gives no technical detail, only that n8n versions before 0.216.1 let unauthorised parties obtain information.
- Remote file existence check vulnerability in `mlflow server` and `mlflow ui` CLIs The MLflow server and UI answer existence queries for arbitrary host files, letting remote clients probe the filesystem.
- Password exposure in H2 Database The H2 web admin console password can be passed as a command-line argument, where any local user listing processes can read it in cleartext.
- Uninitialized variable access in Tensorflow AssignOp checks only that the destination tensor is initialised, so it copies uninitialised source data into a new tensor, causing undefined behaviour.
- Improper Restriction of XML External Entity Reference in com.h2database:h2. Retrieving SQLXML as a DOM source makes H2 parse XML with external entities enabled, so attacker-supplied entities can read or fetch resources.
- Arbitrary memory read in `ImmutableConst` A crafted ImmutableConst op maps an attacker-named file as string memory, letting the attacker read arbitrary file contents.
- Heap OOB in nested `tf.map_fn` with `RaggedTensor`s Missing inner shape checks when converting variant tensors to ragged tensors leave output buffers filled with uninitialised heap data.
- Data leak in Tensorflow Unvalidated split offsets passed to an n-gram op cause out-of-bounds heap reads that return adjacent process memory.