CVE-2024-12378On affected platforms running Arista EOS with secure Vxlan configured, restarting the Tunnelsec agent will result in packets being sent over the secure Vxlan tunnels in the clear.
- 9.1CriticalCVSS base score
- 0.51%Exploitation in 30 daysEPSS · top 56% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
On affected platforms running Arista EOS with secure Vxlan configured, restarting the Tunnelsec agent will result in packets being sent over the secure Vxlan tunnels in the clear.
Timeline
ID reserved
By Arista
- 5 months later
· 5 months later
Published
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| AristaCNA (assigner) | 3.1 | Critical9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
| NVDNVD · Deferred | 3.1 | Critical9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
- EPSS (exploitation in 30 days)
- 0.51% · top 56% of all CVEs (17 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: yes · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.1.
Affected products
Arista Networks · CloudVision Portal
- affected 4.32.0 – ≤ 4.32.2F
- affected 4.31.0 – ≤ 4.31.6M
- affected 4.30.0 – ≤ 4.30.8M
- affected 4.29.0 – ≤ 4.29.9M
- affected 4.28.0 – ≤ 4.28.12M
- affected 4.27.0 – ≤ 4.27.12M
What to do
Solution: The recommended resolution is to upgrade to a remediated software version at your earliest convenience. Arista recommends customers move to the latest version of each release that contains all the fixes listed below. For more information about upgrading see EOS User Manual: Upgrades and Downgrades https://www.arista.com/en/um-eos/eos-upgrades-and-downgrades CVE-2024-12378 has been fixed in the following releases: * 4.33.0F and later releases in the 4.33.x train * 4.32.3M and later releases in the 4.32.x train * 4.31.7M and later releases in the 4.31.x train * 4.30.9M and later releases in the 4.30.x train * 4.29.10M and later releases in the 4.29.x train
Workaround: The workaround is to remove and re-apply security profiles for each secure VTEP. switch> show vxlan security profile VTEP Security Profile ------------- ---------------- 1.0.2.1 p1 switch> en switch# config switch(config)# interface vxlan 1 switch(config-if-Vx1)# no vxlan vtep 1.0.2.1 ip security profile p1 switch(config-if-Vx1)# vxlan vtep 1.0.2.1 ip security profile p1
References
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2024-54462 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2024-12378)Record last updated .