RPC: Invalid Procedure
This protocol anomaly triggers when it detects an RPC message with an invalid procedure field (for example, not NULL, DUMP, SET, UNSET, GETPORT, or CALLIT). This can indicate a nonstandard RPC client or server or an exploit/buffer overflow attempt.
Extended Description
Any invalid procedure in an RPC message is treated as a protocol anomaly. It may indicate a non-standard RPC client or server is operating on a network, or an attack attempt. The impact depends on how an affected system handles malformed RPCs.
References
mx-19.3
vmx-19.3
vsrx-19.2
srx-19.3
srx-branch-19.3
vsrx3bsd-19.2
srx-19.4
vsrx3bsd-19.4
srx-branch-19.4
vsrx-19.4
vmx-19.4
mx-19.4
srxevo-25.4
vsrx-26.2
srx-26.2
srx-branch-26.2
vsrx3bsd-26.2
mx-12.3
srx-12.3
srx-branch-12.3
vsrx-12.3