This message was deleted.

@Will Droste Thanks for the great question, I did some tests:

from <http://nebula3.gclient.net|nebula3.gclient.net> import ConnectionPool
from nebula3.Config import Config

config = Config()
config.max_connection_pool_size = 10
connection_pool = ConnectionPool()
# client connecting to graphd
connection_pool.init([('127.0.0.1', 9669)], config)

from nebula3.gclient.net.AuthResult import AuthResult
from nebula3.gclient.net.Session import Session

session = connection_pool.get_session('root', 'nebula')
session_id = session._session_id


# simulate another client connecting to graphd2
connection_pool2 = ConnectionPool()
connection_pool2.init([('127.0.0.1', 49433)], config)


connection = connection_pool2.get_connection()

auth_result = AuthResult(session_id, 0, b'UTC')

session_from_evil = Session(connection, auth_result, connection_pool, True)

session_from_evil.execute("SHOW HOSTS")
# it worked!!!
# Out[28]: ResultSet(keys: ['Host', 'Port', 'HTTP port', 'Status', 'Leader count', 'Leader distribution', 'Partition distribution', 'Version'], values: ["storaged0", 9779, 19779, "ONLINE", 9, "basketballplayer:3, moviegraph:3, test:3", "basketballplayer:3, moviegraph:3, test:3", "3.3.0"],["storaged1", 9779, 19779, "ONLINE", 9, "basketballplayer:3, moviegraph:3, test:3", "basketballplayer:3, moviegraph:3, test:3", "3.3.0"],["storaged2", 9779, 19779, "ONLINE", 12, "basketballplayer:4, moviegraph:4, test:4", "basketballplayer:4, moviegraph:4, test:4", "3.3.0"])

# In [31]: session._session_id == session_from_evil._session_id
# Out[31]: True

# In [32]: session._connection == session_from_evil._connection
# Out[32]: False

So can you just pass in the

sessoinId

in to any connection?

The interface seems not yet allow passing(at least from python client) sessionID, but it’s actually totally doable as my test.

Is the session ID unique enough not be a security concern. For instance if you make a connection to Nebula can somebody guess a

sessionId

just be doing

YIELD 1

statements?

Yes, unfortunately, this is doable, I don’t have security background, this looks very bad or, do you have any suggestions/expected behaviors in such scenario?

Also though from a resource perspective it seems then I can re-connect and just keep using the same session ID, which is good considering that the default expiration for a session is 8hrs. From a security perspective though if I can reuse the session ID and not have to auth then there should be additional protections in place like this session came from this IP addresss. (edited)

Yes, the session to be persistent in metaD came with the intuition to enable cross-client/cross GraphD reuse auth context, but as you mentioned, maybe we should enable strict mode to optionally add verification of source_IP etc on this?

If we are to think of this like connecting to a web service the general security approach is this.

I moved this topic to https://github.com/vesoft-inc/nebula/discussions/4874 🙂