Signature Detail

MS-RPC: Wrong Fragment

This protocol anomaly triggers when it detects an MSRPC message other than BIND, BIND_ACK, ALTER_CONTEXT, or ALTER_CONTEXT_RESPONSE that is fragmented.

Extended Description

A remote attacker could maliciously craft an MSRPC packet to cause an exception in an application. This could result in a disclosure of sensitive information, a buffer overflow, a denial of service, or the execution of malicious code.

References

• URL: http://windowssdk.msdn.microsoft.com/en-us/library/ms719418.aspx
• URL: http://en.wikipedia.org/wiki/MSRPC