op-node and op-batcher have --rpc.enable-admin which enables admin API on these RPC. Combined with --rpc.addr=0.0.0.0, this will expose admin API to the public when running outside docker which is a security vulnerability.
As @upnodedev has asked in the ticket that
Why do you expose the batcher admin rpc? It seem to use for start / stop batcher. Wouldn't this be a security issue?
And @sbvegan has spoken to a client engineer
The document is written from docker but users would run it on their own VM. So, I think we shouldn't expose admin API and it would be a security issue if being exposed.
Description
op-node and op-batcher have
--rpc.enable-admin
which enables admin API on these RPC. Combined with--rpc.addr=0.0.0.0
, this will expose admin API to the public when running outside docker which is a security vulnerability.As @upnodedev has asked in the ticket that
And @sbvegan has spoken to a client engineer
The document is written from docker but users would run it on their own VM. So, I think we shouldn't expose admin API and it would be a security issue if being exposed.