# CVE-2023-6068: Security feature bypass in MOS

> Incorrect ACL operation on Arista 7130 FPGA platforms allows unauthorized packets to bypass security controls and be permitted.

- **Severity:** Low 3.1 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Mar 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-2qwg-cqpg-9qrr

## What is CVE-2023-6068?

CVE-2023-6068 is a low-severity vulnerability in Arista Networks MOS, published on 4 Mar 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

On affected 7130 Series FPGA platforms running MOS and recent versions of the MultiAccess FPGA, application of ACL’s may result in incorrect operation of the configured ACL for a port resulting in some packets that should be denied being permitted and some

Weakness: CWE-283 (Unverified Ownership)

## Which versions are affected by CVE-2023-6068?

It affects 1 product.


Products: Arista Multiaccess.

## How do I fix CVE-2023-6068?

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

## Is CVE-2023-6068 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-6068 and fix it if it is affected.

What it is: CVE-2023-6068 is a low-severity vulnerability in Arista Networks MOS, published on 4 Mar 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-6068 in the wild and no public exploit code.

Affected product: Arista Networks MOS. 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-2023-6068/ (Markdown: https://insights.sbomify.com/CVE-2023-6068/index.md)
```

## Sources

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

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