Hydra: Optuna custom_search_space can resolve and execute untrusted callables via get_method
- 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
- Fix
- Fixed in 1.3.0, 1.4.0.dev10
- 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: total
Summary
Hydra is a framework for elegantly configuring complex applications. From 1.2.0 until 1.3.0 and 1.4.0.dev10, the hydra-optuna-sweeper package accepts a configuration-controlled dotted path in hydra.sweeper.custom_search_space, resolves it with hydra.utils.get_method(), and later invokes the returned callable in the Hydra controller process. Because get_method() is a trusted-input lookup helper and does not apply the execution policy used by instantiate(), an attacker who controls Optuna sweep configuration or command-line overrides can select importable Python code for execution with the application's privileges, including bypassing a trusted execution whitelist on affected Hydra 1.4 development releases. This issue is fixed in versions 1.3.0 and 1.4.0.dev10.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- hydra-ecosystem hydra
From 1.2.0 · fixed in 1.3.0; From 1.4.0.dev4 · fixed in 1.4.0.dev10
- hydra-optuna-sweeperPyPI
From 1.2.0 · fixed in 1.3.0
- hydra-optuna-sweeperPyPI
From 1.4.0.dev4 · fixed in 1.4.0.dev10
- hydra-optuna-sweeperPyPI
From 1.2.0 · fixed in 1.3.0; From 1.4.0.dev4 · fixed in 1.4.0.dev10