Skip to main content
VulnerabilityPublished Updated

CVE-2023-24547: Arista Networks MOS · CWE-212

Affects Arista Networks MOSSource CVE Database V5

0

Not known to be exploited · CVSS 5.9 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
5.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Dec 2023

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Arista Networks MOSAffected
  • =0.13.0
Fixed in–

AI-suggested

  1. Immediate review and restriction of access controls to device logs and running configurations to ensure only highly trusted personnel have authenticated access.
  2. Implement strict logging policies to avoid forwarding sensitive logs to remote servers unless encrypted and access-controlled.
  3. Regularly audit device configurations and logs for presence of clear text passwords and remove or mask them where possible.
  4. Engage with Arista Networks support to obtain patches or firmware updates addressing this vulnerability as they become available.
  5. Consider rotating BGP passwords after remediation to invalidate any potentially exposed credentials.
  6. Employ network segmentation and multi-factor authentication for device management interfaces to reduce risk of unauthorized authenticated access.
  7. Monitor network traffic for anomalous BGP activity that could indicate exploitation attempts.
  8. Use configuration management tools that avoid storing or displaying passwords in clear text in running configurations.
  9. Educate network administrators about the risks of storing sensitive information in logs and configurations and enforce secure operational procedures.

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.

References

Community reviews

Loading reviews…