Security context
What an agent needs to avoid regressing past fixes and find the next vuln in this repo.
eth-brownie/brownie
master @ ff3d7f1
2
Fixes
0
CVEs
HIGH
Peak severity
Highlights
Code Execution: 1 prior fix. Scrutinize any change in this area.
brownie._cli/networks.py: most-fixed (1 issue). Treat as high-risk during review.
1 high-severity fix in this history; regressions here are high-impact.
Recurring patterns
The bug types that recur here, drawn from past fixes, not open vulnerabilities.
Code Execution: The use of the unsafe 'eval' function inside the networks CLI component allowed malicious arguments to execute arbitrary shell code on the user host machine. Developers must avoid using dynamic evaluation of strings and enforce safe parsing alternatives like 'ast.literal_eval'.
Information Disclosure: Interactive user sessions involving the 'account' component inadvertently saved highly sensitive assets (such as private keys and mnemonics) into standard, unencrypted shell history files. Robust input filtering must be enforced to ensure sensitive inputs are stripped prior to history storage.