GPU VulnDB

Database/Firmware, BMC & network fabric

Junos OS: stack overflow in the dot1x daemon lets an ICCP peer crash or own a Fusion AD

CVSS 8.7CVE-2026-102069Firmware, BMC & network fabriccurated

Impact

On Junos devices acting as Fusion Aggregation Devices with dot1x synchronization enabled, an attacker able to act as the configured ICCP peer can overflow a stack buffer in the dot1x daemon, causing a denial of service and potentially code execution as root. The ICCP peer is the other half of a redundant aggregation pair, so this is a lateral path: compromise one aggregation device and you can take or crash its partner, which removes the redundancy that the access layer under the fleet depends on. It only applies to the Fusion satellite topology with dot1x sync configured - most spine/leaf GPU fabrics do not run it, so check the configuration before scheduling anything.

Who can reach it

Adjacent network, no device authentication needed beyond being the configured ICCP peer - an attacker must already be, or have compromised, the peer aggregation device. Only applies when dot1x synchronization is enabled in a Junos Fusion satellite topology.

What to do

Upgrade to a fixed Junos release per Juniper advisory JSA112188; the record does not list fixed versions. The upgrade is a reboot of each aggregation device, which on a redundant pair can be rolled one side at a time. If Junos Fusion or dot1x synchronization is not in use, you are not exposed and no maintenance window is needed.

References

Related entries

All Firmware, BMC & network fabric entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.