rpcrt4: Fix potential NULL pointer access in process_bind_packet.

Upon failure to allocate results in process_bind_packet, build nack packet and send right away, instead of falling into the normal path and potentially dereferencing the NULL pointer.

rpcrt4: Fix potential NULL pointer access in process_bind_packet.
eb0d2828 · Rob Shearman · Alexandre Julliard · 79307e59 · eb0d2828
Commit eb0d2828 authored Nov 13, 2009 by Rob Shearman Committed by Alexandre Julliard Nov 16, 2009
Hide whitespace changes
Inline Side-by-side

Showing with 1 addition and 0 deletions

rpc_server.c dlls/rpcrt4/rpc_server.c +1 -0

No files found.
--- a/dlls/rpcrt4/rpc_server.c
+++ b/dlls/rpcrt4/rpc_server.c
@@ -203,6 +203,7 @@ static RPC_STATUS process_bind_packet(RpcConnection *conn, RpcPktBindHdr *hdr, R
        response = RPCRT4_BuildBindNackHeader(NDR_LOCAL_DATA_REPRESENTATION,
                                              RPC_VER_MAJOR, RPC_VER_MINOR,
                                              REJECT_LOCAL_LIMIT_EXCEEDED);
+        goto send;
    }

    for (i = 0, ctxt_elem = (RpcContextElement *)msg->Buffer;