# CVE-2024-7142: Weak cryptography in CloudVision Appliance

> Attackers with physical access can read unencrypted data from Arista CloudVision Appliance disks due to failed hardware encryption.

- **Severity:** Medium 4.6 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jan 2025
- **Updated:** 13 Jan 2025
- **Also known as:** GHSA-w5g9-ccrp-5568

## What is CVE-2024-7142?

CVE-2024-7142 is a medium-severity vulnerability in Arista Networks CloudVision Appliance, published on 10 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

On Arista CloudVision Appliance (CVA) affected releases running on appliances that support hardware disk encryption (DCA-350E-CV only), the disk encryption might not be successfully performed. This results in the disks remaining unsecured and data on them

Weakness: CWE-311 (Missing Encryption of Sensitive Data)

## Which versions are affected by CVE-2024-7142?


## How do I fix CVE-2024-7142?

No fix has been published for CVE-2024-7142 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-7142 being exploited?

There is no known exploitation of CVE-2024-7142 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-7142 and fix it if it is affected.

What it is: CVE-2024-7142 is a medium-severity vulnerability in Arista Networks CloudVision Appliance, published on 10 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-7142 in the wild and no public exploit code.

Affected product: Arista Networks CloudVision Appliance. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-7142/ (Markdown: https://insights.sbomify.com/CVE-2024-7142/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-7142
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-7142
- OSV: https://osv.dev/vulnerability/CVE-2024-7142

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-7142/
Summaries are generated and may contain mistakes; the official description above is the record.