dbcve.org
Ng FirewallApplication · Arista

CVE-2024-12829

HIGH · 8.8 CVSS v3.1 Published 2024-12-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Arista NG Firewall ExecManagerImpl Command Injection Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Arista NG Firewall. Authentication is required to exploit this vulnerability. The specific flaw exists within the ExecManagerImpl class. The issue results from the lack of proper validation of a user-supplied string before using it to execute a system call. An attacker can leverage this vulnerability to execute code in the context of root. Was ZDI-CAN-24015.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Arista NG Firewall contains a command injection vulnerability in the ExecManagerImpl class where user-supplied input is not validated before being passed to a system call. An authenticated attacker can exploit this to execute arbitrary code with root privileges.

MitigationApply the vendor-supplied patch or firmware update for Arista NG Firewall. Until patched, limit access to the management interface to trusted personnel only and monitor for suspicious command execution.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Ng FirewallApplication
Affected:= 17.1.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed Arista NG Firewall version
    Access the firewall management interface or use the command line interface (CLI) and run the command to display the system version, such as 'show version' or check the web UI dashboard for the firmware version information
    Affected if The displayed version is exactly 17.1.1 (the only affected version listed)
  2. Confirm management interface accessibility
    Verify whether the Arista NG Firewall management interface (web UI or CLI) is reachable from network segments. Check firewall rules or access control lists that govern access to port 443/HTTPS or 22/SSH on the firewall device
    Affected if The management interface is exposed to untrusted or public networks, increasing the attack surface for authenticated attackers
  3. Review for unexpected privileged processes
    On the firewall system, use commands like 'ps aux' or check system logs to look for unusual processes running as root that were not initiated by known administrative tasks
    Affected if Unexpected processes or commands are running with root privileges that cannot be attributed to legitimate administrator actions
  4. Audit management interface access logs
    Examine authentication and command logs from the NG Firewall management interface for signs of suspicious or unauthorized authenticated sessions, particularly those executing system commands
    Affected if There are authenticated sessions executing commands that are abnormal or were not initiated by authorized administrators

A system is affected if it is running Arista NG Firewall version 17.1.1 and has the management interface accessible to an attacker who could authenticate and invoke the ExecManagerImpl class functionality.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-supplied patch or firmware update for Arista NG Firewall. Until patched, limit access to the management interface to trusted personnel only and monitor for suspicious command execution.

Fix this in Ng Firewall Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-12829 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-12829 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data