neuron-core/neuron-ai
Affected
- introduced
0, fixed2.8.12(ecosystem)
Fixed versions
2.8.12
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: CVE-2025-67509
Neuron MySQLSelectTool “read-only” bypass via SELECT ... INTO OUTFILE (file write → potential RCE)
Impact
MySQLSelectTool is intended to be a read-only SQL tool (e.g., for LLM agent querying). However, validation based on the first keyword (e.g., SELECT) and a forbidden-keyword list does not block file-writing constructs such as INTO OUTFILE / INTO DUMPFILE.
As a result, an attacker who can influence the tool input (e.g., prompt injection through a public agent endpoint) may be able to write arbitrary content to files on the DB server.
If the MySQL/MariaDB account has the FILE privilege and server configuration permits writes to a useful location (e.g., a web-accessible directory), the impact can escalate to remote code execution on the application host (for example, by writing a PHP web shell).
Who is impacted: Deployments that expose an agent using MySQLSelectTool to untrusted input and run with overly-permissive DB privileges/configuration.
Patches
Not patched in: 2.8.11
Fixed in: 2.8.12
Recommended fix direction:
INTO, OUTFILE, DUMPFILE, LOAD_FILE, and other file/IO-related functions/clauses.Workarounds
If you cannot upgrade immediately:
MySQLSelectTool for any agent reachable from untrusted input.FILE privilege.secure_file_priv is set to a directory that is not web-accessible (or restrict it tightly).INTO OUTFILE, INTO DUMPFILE, LOAD_FILE, ; (multi-statements), and suspicious comment patterns.High Basis: The source's own band: HIGH
0, fixed 2.8.12 (ecosystem)2.8.12
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0