CVE-2025-6978 Arbitrary Code Execution in the Arista NG Fire... #1863
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🤖 Automated Content Update
This PR was automatically generated by the HackTricks News Bot based on a technical blog post.
📝 Source Information
🎯 Content Summary
CVE-2025-6978 (blog text describes CVE-2025-6798): Authenticated command injection → root arbitrary code execution in Arista NG Firewall
Product / exposure
Arista NG Firewall (formerly Untangle) can be administered via a Web UI or a JSON-RPC API over HTTP(S). The vulnerable surface is the admin JSON-RPC endpoint reachable via HTTP POST to:
The attack is remote but requires authenticated acces...
🔧 Technical Details
Technique 1 — JSON-RPC → environment variables → shell
evalsink: If a JSON-RPC endpoint converts attacker-controlled key/value pairs into environment variables (e.g.,KEY=valuestrings passed viaRuntime.getRuntime().exec(cmd, envp)) and a downstream shell script concatenates those environment variables into a command string executed witheval, the environment-variable values become a command-injection primitive. Even with an allow-listed primary “command” argument (enum/switch), attackers can inject via secondary arguments that influence the script’s command construction.Technique 2 — Blacklist bypass of shell metacharacters: Filtering only a small set of tokens (e.g.,
; & | > $() is insufficient because shells provide multiple expansion/command-substitution mechanisms. Unblocked characters (the post highlights backticks`) can still cause command substitution and code e...🤖 Agent Actions
Summary:
evalinjection subsection detailing the allowlist flow, weak blacklist, and backtick-based command substitution exploit path./admin/JSON-RPCtraffic.Tests:
This PR was automatically created by the HackTricks Feed Bot. Please review the changes carefully before merging.