dbcve.org
Ng FirewallApplication · Arista

CVE-2024-47520

HIGH · 7.6 CVSS v3.1 Published 2025-01-10
Fix available
A fix is available. Upgrade to after 17.1.1 or later.
See remediation →
80/100
Remediation priority · High
Remotely reachable

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
A user with advanced report application access rights can perform actions for which they are not authorized

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 · low confidence

This is an authorization bypass vulnerability where users granted 'advanced report application access rights' can perform actions outside their intended permissions. The vulnerability indicates broken access control logic in the reporting application that fails to properly validate user authorization boundaries.

MitigationImplement and enforce role-based access control (RBAC) checks to ensure users can only execute actions explicitly authorized for their specific permission level. Conduct a comprehensive access control audit across the reporting application.

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
Low

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

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 Arista Ng Firewall version
    Access the firewall admin console or run 'show version' via CLI to retrieve the installed firmware version
    Affected if The displayed version is 17.1.1 or any version lower than 17.1.1
  2. Locate the reporting application module
    Navigate to the firewall administrative interface and locate the Reporting or Report Application section under the configuration or services menu
    Affected if The reporting application module is present and enabled on the firewall
  3. Identify users with advanced report access rights
    In the user management or access control section of the admin console, examine the permission assignments for each user account and identify any accounts granted 'advanced report application access rights' or equivalent elevated reporting permissions
    Affected if One or more user accounts are assigned advanced report application access rights
  4. Verify access control boundaries for reporting actions
    Attempt to perform reporting actions (such as generating, exporting, or modifying reports) using a user account that has advanced report application access rights, and observe whether actions can be executed that fall outside the expected scope of that user's role
    Affected if Users with advanced report access rights can execute reporting actions that should be restricted to higher permission levels, indicating broken access control logic

A user is affected if they are running Arista Ng Firewall version 17.1.1 or lower AND have the reporting application enabled with users assigned advanced report application access rights, as the access control boundaries can be bypassed.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 17.1.1
Interim mitigation

Implement and enforce role-based access control (RBAC) checks to ensure users can only execute actions explicitly authorized for their specific permission level. Conduct a comprehensive access control audit across the reporting application.

Recommended fix Moderate confidence

17.2.x or later fixed release (verify exact version from Arista security advisory)

  1. 1. Identify the current installed version of Arista Ng Firewall using the system administrative interface or CLI command.
  2. 2. Consult the Arista security advisory for CVE-2024-47520 on www.arista.com to confirm the specific fixed release version.
  3. 3. Plan upgrade during a maintenance window following organizational change management procedures.
  4. 4. Backup the current Ng Firewall configuration before performing the upgrade.
  5. 5. Upgrade to the fixed release version (verify with Arista advisory - typically 17.2.x or later releases contain security fixes).
  6. 6. After upgrade, verify the system is operational and test that the authorization controls function correctly.
  7. 7. Review user access rights in the advanced report application to ensure proper authorization boundaries are enforced.
Caveat Check Arista release notes for any configuration or feature changes between 17.1.x and the target fixed release

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ng Firewall Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-47520 — 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-47520 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