Improper AuthenticationWeakness · CWE-287

CVE-2024-11186

CRITICAL · 10.0 CVSS v3.1 Published 2025-05-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
On affected versions of the CloudVision Portal, improper access controls could enable a malicious authenticated user to take broader actions on managed EOS devices than intended. This advisory impacts the Arista CloudVision Portal products when run on-premise. It does not impact CloudVision as-a-Service.

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

This is an authorization bypass vulnerability in Arista CloudVision Portal (on-premise) where improper access controls allow authenticated users to perform actions on managed EOS devices beyond what their assigned permissions should permit. A malicious authenticated user could escalate privileges to take broader administrative actions on network devices.

MitigationApply vendor-provided patches for CloudVision Portal when available; ensure least-privilege user roles are enforced and monitor for unauthorized administrative actions on managed EOS devices.

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

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
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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. Confirm Arista CloudVision Portal deployment
    Identify if your environment runs Arista CloudVision Portal (on-premise) by checking for the CVP application services, typically accessible via web UI on port 443 or configured hostname
    Affected if CloudVision Portal (on-premise) is present in the environment
  2. Determine CloudVision Portal version
    Access CVP administration interface or run 'cvpversion' command on the CVP server to retrieve the installed version number
    Affected if Version is unpatched and falls within the vulnerable range (check against vendor advisories for CVE-2024-11186)
  3. Review user role assignments
    In CVP, navigate to Administration > Users and Roles and examine the assigned roles for each user account, particularly those with limited or non-administrative roles
    Affected if Users exist with limited roles who should not have administrative access to EOS devices
  4. Audit EOS device configuration changes
    In CVP, review the Change Control history and Device Snapshots for managed EOS devices to identify unexpected configuration changes or commands issued outside normal workflows
    Affected if Configuration changes appear that were not initiated through authorized change management processes
  5. Inspect CVP audit logs for privilege escalation
    Examine CVP audit logs (Administration > Logs > Audit) for actions where users performed administrative operations on EOS devices that exceed their assigned role permissions
    Affected if Audit logs show users executing privileged EOS commands outside their defined role scope

A user is affected if they run an unpatched Arista CloudVision Portal (on-premise) version and have users with restricted roles who could potentially bypass authorization controls to perform privileged actions on managed EOS devices.

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 vendor-provided patches for CloudVision Portal when available; ensure least-privilege user roles are enforced and monitor for unauthorized administrative actions on managed EOS devices.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-11186 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