dbcli mycli Whitelist source.py source_special_command_is_safe os command injection
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
The mycli command-line MySQL/MariaDB client, a database tool built by dbcli, is affected through a flaw in its special-command safety check (the "Whitelist" component used for the source command). An attacker with local access could exploit this to inject operating system commands, potentially gaining control of the affected user's system.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
A weakness has been identified in dbcli mycli up to 2.29.4/2.30.1. The impacted element is the function source_special_command_is_safe of the file mycli/packages/special/source.py of the component Whitelist. Executing a manipulation can lead to os command injection. It is possible to launch the attack on the local host. The exploit has been made available to the public and could be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- dbcli mycli
2.29.0, 2.29.1, 2.29.2, 2.29.3, 2.29.4, 2.30.0, 2.30.1