# CVE-2023-24547: On Arista MOS configuration of a BGP password will cause the password to be logged in clear text.

> Authenticated users can view BGP passwords in clear text within local logs, remote logging servers, and the device's running configuration.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Dec 2023
- **Updated:** 28 May 2025
- **Also known as:** GHSA-p4r9-xg4m-74hx

## What is CVE-2023-24547?

CVE-2023-24547 is a medium-severity vulnerability in Arista Networks MOS, published on 5 Dec 2023. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

On affected platforms running Arista MOS, the configuration of a BGP password will cause the password to be logged in clear text that can be revealed in local logs or remote logging servers by authenticated users, as well as appear in clear text in the device’s running config.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

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

It affects 1 product.


Products: Arista Mos.

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

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

## Is CVE-2023-24547 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-24547 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2023-24547 is a medium-severity vulnerability in Arista Networks MOS, published on 5 Dec 2023. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-24547 exists.

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-24547/ (Markdown: https://insights.sbomify.com/CVE-2023-24547/index.md)
```

## Sources

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

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