dbcve.org
Cloudvision PortalApplication · Arista

CVE-2023-24546

HIGH · 8.1 CVSS v3.1 Published 2023-06-13
Fix available
A fix is available. Upgrade to after 2021.3 or later.
See remediation →
87/100
Remediation priority · High
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
On affected versions of the CloudVision Portal improper access controls on the connection from devices to CloudVision could enable a malicious actor with network access to CloudVision to get broader access to telemetry and configuration data within the system than intended. This advisory impacts the Arista CloudVision Portal product 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 improper access control vulnerability in Arista CloudVision Portal (on-premise deployments). A malicious actor with network access to CloudVision can bypass intended access restrictions to gain broader access to telemetry and configuration data from managed devices. The vulnerability stems from insufficient controls on the device-to-CloudVision connection channel.

MitigationFor on-premise deployments, review and enforce strict access controls on device-to-CloudVision communications, implement network segmentation to limit exposure, and apply any vendor-supplied patches or configuration guidance to restrict telemetry and configuration data access to authorized paths only.

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
Cloudvision PortalApplication
Affected:>= 2021.1, <= 2021.3= 2022.1.0= 2022.1.1= 2022.2.0= 2022.2.1= 2022.3.0

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
None

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

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 if Arista CloudVision Portal is deployed on-premise
    Check for CloudVision Portal installation by reviewing running services or processes on the management server. Look for cvp-related processes, containers, or services. Check for CloudVision directories in /var/log/cvp or similar paths.
    Affected if CloudVision Portal on-premise deployment is present and version falls within affected ranges (2021.1-2021.3, 2022.1.0, 2022.1.1, 2022.2.0, 2022.2.1, 2022.3.0)
  2. Determine CloudVision Portal version
    Run command 'cvpversion' or access CloudVision UI and navigate to About section to retrieve the exact version number. Alternatively, check /etc/cvp-release or similar version file on the CloudVision server.
    Affected if Installed version matches any of these: 2021.1, 2021.2, 2021.3, 2022.1.0, 2022.1.1, 2022.2.0, 2022.2.1, or 2022.3.0
  3. Verify device-to-CloudVision connection channel access controls
    Review CloudVision configuration files for access control settings on the device communication channel. Check CVP topology or device connection settings to determine if unrestricted telemetry or configuration data access is allowed from managed devices.
    Affected if Device-to-CloudVision connection channel permits broader telemetry or configuration access without proper restriction enforcement
  4. Assess network exposure of CloudVision Portal management interface
    Review firewall rules, network ACLs, or cloud security groups to determine if CloudVision management ports are accessible from unauthorized network segments. Check if port 443 or custom CVP ports are exposed beyond trusted management networks.
    Affected if CloudVision Portal is accessible from network segments beyond the trusted management plane without proper access restrictions

Environment is affected if running an on-premise CloudVision Portal version between 2021.1 and 2022.3.0 with device-to-CloudVision connection channels lacking proper access controls and exposed to untrusted networks.

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
Upgrade available Upgrade to a release after 2021.3
Interim mitigation

For on-premise deployments, review and enforce strict access controls on device-to-CloudVision communications, implement network segmentation to limit exposure, and apply any vendor-supplied patches or configuration guidance to restrict telemetry and configuration data access to authorized paths only.

Fix this in Cloudvision Portal Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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