<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-28T14:39:24.116192+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-47708</id>
    <title>CVE-2026-47708 — MCP-for-Stata: Command injection via log_file_name parameter in Stata command wrapper</title>
    <updated>2026-09-28T14:39:24.146224+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> SepineTam stata-mcp</p>
<p>MCP-for-Stata is an MCP server for Stata to integrate Stata into an agent. Prior to version 1.17.3, the `log_file_name` parameter in the `stata_do` API and CLI is directly interpolated into a Stata command string without sanitization. The security guard (`GuardValidator`) only scans the do-file content but does not validate this parameter. An attacker can inject arbitrary Stata commands (including `shell`, `python`, `erase`, etc.) by crafting a malicious `log_file_name` containing quotes, newlines, or Stata command separators. Version 1.17.3 contains a patch for the issue.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-47708"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-4p62-hqp5-g644</id>
    <title>GHSA-4p62-hqp5-g644 — MCP-for-Stata: Command injection via log_file_name parameter in Stata command wrapper</title>
    <updated>2026-09-28T14:39:24.146359+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: stata-mcp</p>
<p>### Summary
The `log_file_name` parameter in the `stata_do` API and CLI is directly interpolated into a Stata command string without sanitization. The security guard (`GuardValidator`) only scans the do-file content but does not validate this parameter. An attacker can inject arbitrary Stata commands (including `shell`, `python`, `erase`, etc.) by crafting a malicious `log_file_name` containing quotes, newlines, or Stata command separators.</p>
<p>### Details</p>
<p>In `src/stata_mcp/stata/stata_do/do.py`, both `_execute_unix_like` and `_execute_windows` construct a Stata command string using Python f-strings:</p>
<p>```python
commands = f"""
capture log close
{self.generate_log_command(log_file, is_replace)}
...
do "{dofile_path}"
...
"""
```</p>
<p>The `generate_log_command` method returns:</p>
<p>```python
log_cmd = f'log using "{log_file.as_posix()}", {replace_clause} {log_type} name({log_type}_log)'
```</p>
<p>Where `log_file` is constructed from user-supplied `log_name`:</p>
<p>```python
def generate_log_file(self, log_name: str, extension='log'):
    return self.log_file_path / f"{log_name}.{extension}"
```</p>
<p>The `log_name` parameter comes directly from user input (via MCP tool `stata_do` or CLI `stata-mcp tool do`) without any validation. Since the path is embedded inside double quotes in a Stata command string, an attacker can break out of the string context and inject arbitrary commands.</p>
<p>Additionally, `generate_log_file` does not prevent path traversal via `log_name`, allowing arbitrary file write outside…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-4p62-hqp5-g644"/>
  </entry>
</feed>
