On affected EOS platforms with AAA-based gRPC authorization enabled for OpenConfig, gRPC requests of an authenticated user to OpenConfig may use the wrong privilege level, resulting in an authorization using the wrong AAA method list. This does not impact non-gRPC OpenConfig requests such as NETCONF.
The following conditions must both be met for this vulnerability to be exploitable:
- OpenConfig gRPC transport must have an SSL profile configured with request authorization enabled:
Transport: default
SSL profile: oc
Authorization required: yes
- The SSL profile must be configured with a trust certificate.
Ensure that the privilege level 0 AAA authorization method list includes methods beyond 'none' to prevent unintended access escalation:
aaa authorization exec default local group tacacs+
aaa authorization commands 0 default local group tacacs+
To detect potential exploitation, enable AAA accounting and monitor logs for cases where a user's privilege level in gRPC requests does not match their defined privilege level (e.g., a user with privilege 9 appearing as priv-lvl=0 in gRPC requests).
The following EOS releases contain the fix for this vulnerability:
- 4.33.9M and later releases in the 4.33.x train
- 4.34.8M and later releases in the 4.34.x train
- 4.35.6M and later releases in the 4.35.x train
- 4.36.1F and later releases in the 4.36.x train
No hotfix is available for this vulnerability.