# _to argument missing 0x0 address check in the ConnextRouter Low/Info · Three Sigma · Lending aggregator · 6th May, 2023 Finding 3S-FUJI-N11 of the Fuji Finance security review. - Report: /reports/fuji-finance - Source: https://cdn.sanity.io/files/qoqld077/staging/32181a28eac3175d15fb8924d249bb0d91ca350c.pdf --- ### Description The ConnextRouter does not check, in the _crossTransfer(...) and _crossTransferWithCalldata(...) functions, if the receiver and routerByDomain[destDomain] equal address(0). This should revert anyway because the Connext contract reverts if _to is address(0), but it's safer to make this additional check. ### Recommendation Check if the address is 0. ### Status Addressed here: [Fujicracy/fuji-v2#632](https://github.com/Fujicracy/fuji-v2/pull/632) --- Related findings: - [When changing addresses, use 2 step transfer and/or address 0x0 checks](https://0xsimao.com/findings/glacier-changing-addresses-transfer-0x0): Glacier - [triggerSendFrom() will send all the ETH in the destination chain where sendFrom() is called to the refundAddress in the LzCallParams argument](https://0xsimao.com/findings/tapioca-dao-eth-refund-params-argument): Tapioca DAO - [In MapleGlobals, there is no check in the dataHash argument when unscheduling a call.](https://0xsimao.com/findings/maple-finance-iii-globals-hash-argument-unscheduling): Maple Finance - [Throughout code-base: missing address checks.](https://0xsimao.com/findings/maple-finance-iii-throughout-code-address-checks): Maple Finance