Package: jfx-bridge
jfx(justfoxing) bridgeOriginally developed as part ofhttps://github.com/justfoxing/ghidra_bridgejfx_bridge is a simple, single file Python RPC bridge, designed to allow interacting from modern python3 to python2. It was built to operate in constrained interpreters, like the Jython interpreters built into more than one reverse-engineering tool, to allow you to access and interact with the data in the tool, and then use modern python and up-to-date packages to do your work.The aim is to be as transparent as possible, so once you're set up, you shouldn't need to know if an object is local or from the remote environment - the bridge should seamlessly handle getting/setting/calling against it.If you like this, feel free to buy me a coffee:https://ko-fi.com/justfoxingTable of contentsHow to useSecurity warningRemote evalRemoteify and remote execLong-running commandsRemote importsOptimising for performanceHow it worksDesign principlesTestedTODOContributorsHow to useYou might actually want one of the following projects that uses jfx_bridge:ghidra_bridgefor Ghidrajfx_bridge_idafor IDA Projfx_bridge_jebfor JEB DecompilerSecurity warningBe aware that when running, a jfx_bridge server effectively provides code execution as a service. If an attacker is able to talk to the port jfx_bridge is running on, they can trivially gain execution with the privileges the server is run with.Also be aware that the protocol used for sending and receiving jfx_bridge messages is unencrypted and unverified - a person-in-the-middle attack would allow complete control of the commands and responses, again providing trivial code execution on the server (and with a little more work, on the client).By default, the jfx_bridge server only listens on localhost to slightly reduce the attack surface. Only listen on external network addresses if you're confident you're on a network where it is safe to do so. Additionally, it is still possible for attackers to send messages to localhost (e.g., via malicious javascript in the browser, or by exploiting a different process and attacking jfx_bridge to elevate privileges). You can mitigate this risk by running jfx_bridge from a process with reduced permissions (a non-admin user, or inside a container), by only running it when needed, or by running on non-network connected systems.Remote evaljfx_bridge is designed to be transparent, to allow easy porting of non-bridged scripts without too many changes. However, if you're happy to make changes, and you run into slowdowns caused by running lots of remote queries (e.g., something likefor remote_val in remote_iterable: doSomethingRemote()can be quite slow with a large number of values as each one will result in a message across the bridge), you can make use of the remote_eval() function to ask for the result to be evaluated on the bridge server all at once, which will require only a single message roundtrip.The following example demonstrates getting a list of all the names of all the functions in a binary:importghidra_bridgeb=ghidra_bridge.GhidraBridge(namespace=globals())name_list=b.remote_eval("[ f.getName() for f in currentProgram.getFunctionManager().getFunctions(True)]")If your evaluation is going to take some time, you might need to use the timeout_override argument to increase how long the bridge will wait before deciding things have gone wrong.If you need to supply an argument for the remote evaluation, you can provide arbitrary keyword arguments to the remote_eval function which will be passed into the evaluation context as local variables. The following argument passes in a function:importghidra_bridgeb=ghidra_bridge.GhidraBridge(namespace=globals())func=currentProgram.getFunctionManager().getFunctions(True).next()mnemonics=b.remote_eval("[ i.getMnemonicString() for i in currentProgram.getListing().getInstructions(f.getBody(), True)]",f=func)As a simplification, note also that the evaluation context has the same globals loaded into the __main__ of the script that started the server.Remoteify and remote execMaybe turning something into a list comprehension is too clunky, or you need more flexibility than remote eval provides - perhaps you need to define a callback with exception handling for bridge failures, to avoid a unexpected bridge disconnection breaking things on the other end. In that case, remoteify() might be for you! remoteify takes a module, function or class and defines it on the remote side of the connection then returns you a bridged handle back to it. This allows you to do things like:importghidra_bridgeb=ghidra_bridge.GhidraBridge(namespace=globals())# define the function locallydefget_function_names(program):# all this code will be run remotely, in a single bridge callname_list=[]forfinprogram.getFunctionManager().getFunctions(True):name_list.append(f.getName())returnname_list# push the function to the remote side and get a handle backremote_get_function_names=b.bridge.remoteify(get_function_names)# call the remote version of the function!names=remote_get_function_names(currentProgram)This works similarly for classes, with two caveats. First, only classes defined in files can be remoteify-ed - classes defined dynamically in a REPL will fail when the python inspect module tries to get their source (a limitation of inspect). Second, if you're defining a class that inherits from a remote class (for example, for a callback), you need to be a little careful, as follows:importjfx_bridgeb=jfx_bridge.BridgeClient()# we lie to the local interpreter about what we want to inherit from - inspect.getsource tries to follow the inheritance chain, and doesn't understand bridged objectsRemoteCallback=objectclassSafeCallback(RemoteCallback):""" We want to install a callback, but need to swallow any errors from the bridge on the remote end in case it's disconnected """def__init__(self,callback_fn)self.callback=callback_fndefdo_callback(self,value):try:self.callback(value)except:# swallow the exceptionspass# now get a handle to the remote class we really want to inherit from, so we can tell the other sideRemoteCallback=b.remote_import("foobar").Callback# push the class to the remote side and get a handle back# Note that we supply the real class to inherit from as a kwargRemoteSafeCallback=b.remoteify(SafeCallback,RemoteCallback=RemoteCallback)# instantiate!x=RemoteSafeCallback(callback_fn)As the previous example shows, you can supply globals to the definitions by providing kwargs to remoteify.remoteify-ing a module, function or class requires that the Python interpreters on BOTH ends understand your code - the local end needs to understand it enough to create the module, function or class, and the remote end needs to understand it to create it and run it. This means that if you're remoteify-ing something from Python 3 to Python 2, you'll need to make sure it's compatible with both languages.remoteify() is built on top of the remote_exec() function, which provides access to exec(). If you need something even more flexible than remoteify, remote_exec() is a backdoor that should let you do just about anything you can think of. remote_exec just takes a string of code to execute (and optionally kwargs to add as globals), so the code only has to be understood by the remote Python interpreter - this might be helpful if you're having problems writing something that's compatible with two different versions.Long-running commandsIf you have a particularly slow call in your script, it may hit the response timeout that the bridge uses to make sure the connection hasn't broken. If this happens, you'll see something likeBridgeTimeoutException: Didn't receive response <UUID> before timeout.There are two options to increase the timeout. When creating the bridge, you can set a timeout value in seconds with the response_timeout argument (e.g.,b = jfx_bridge.bridge.BridgeClient(response_timeout=20)) which will apply to all commands run across the bridge. Alternatively, if you just want to change the timeout for one command, you can use remote_eval as mentioned above, with the timeout_override argument (e.g.,b.remote_eval("<long running eval>", timeout_override=20)). If you use the value -1 for either of these arguments, the response timeout will be disabled and the bridge will wait forever for your response to come back - note that this can cause your script to hang if the bridge runs into problems.Remote importsIf you want to import modules from the other side (e.g., to access modules only available there), there are two options:Use remote_import to get a BridgedModule back directly (e.g.,remote_module = b.remote_import("foo.bar")). This has the advantage that you have exact control over getting the remote module (and can get remote modules with the same name as local modules) and when it's released, but it does take a little more work.Specify hook_import=True when creating the bridge (e.g.,b = jfx_bridge.bridge.BridgeClient(hook_import=True)). This will add a hook to the import machinery such that, if nothing else can fill the import, the bridge will try to handle it. This allows you to just use the standardimport foo.barsyntax after you've connected the bridge. This has the advantage that it may be a little easier to use (you still have to make sure the imports happen AFTER the bridge is connected), but it doesn't allow you to import remote modules with the same name as local modules (the local imports take precedence) and it places the remote modules in sys.modules as proper imports, so they and the bridge will likely stay loaded until the process terminates. Additionally, multiple bridges with hook_import=True will attempt to resolve imports in the order they were connected, which may not be the behaviour you want.Optimising for performanceIf your bridged script is running slowly, a few tips:Don't optimise without data! Create the bridge with record_stats=True, and use get_stats() to record the statistics (hits on different remote commands and send times) through your script to see where the most bridge usage is taking place. As a simple rule of thumb, more hits = more traffic on the bridge = slower script.b=jfx_bridge.bridge.BridgeClient(record_stats=True)start_stats=b.get_stats()# do something chunky....print(b.get_stats()-start_stats)# Stats(total_hits=918,hits={'remote_import': 32, 'add_response': 354, 'remote_get': 212, 'remote_call': 71, 'remote_get_type': 18, 'remote_del': 156, 'remote_eval': 10, 'local_get_type': 4, 'local_get': 29, 'local_eval': 2, 'local_del': 11, 'remote_isinstance': 6, 'local_call': 5, 'remote_call_nonreturn': 3, 'remote_create_type': 1, 'remote_set': 4},total_time=(512, 8.389705419540405),times={'send_cmd': (512, 8.389705419540405)})Cache values that don't change. Every "." on a bridged object requires a call across the bridge to fetch the attribute, so something likebridged_foo.bridged_bar.bridged_flamrequires two calls to access. If you know bridged_flam isn't going to change (e.g., it's a function several modules deep) and you need to use it multiple times, get it once then save it to avoid repeating the calls.For loops that cause lots of bridged operations can often be replaced with remote_evals doing list comprehesions. Instead of:name_list=[]forbridged_xinbridged_get_objects():name_list.append(bridged_x.get_name())# 2 bridge calls for each x (1 to get the get_name function, 1 to call it)try:name_list=b.remote_eval("[x.get_name() for x in bridged_get_objects()]",bridged_get_objects=bridged_get_objects)Use nonreturning calls when you don't need the result and don't have to wait for the bridged function to complete. Every BridgedCallable has a _bridge_call_nonreturn() function, which takes whatever arguments/kwargs you give it and calls the function across the bridge, but doesn't wait for a response. This is useful for when you want to call remote code that might be slow, but you don't care about the response. Alternatively, if you want remote code to call you, but you know you're not going to respond (e.g., event notifications), you can decorate your functions with @jfx_bridge.bridge.nonreturn.remote_time=b.remote_import("time")remote_time.sleep._bridge_call_nonreturn(9999999)# returns immediately@jfx_bridge.bridge.nonreturndefcallback(foo):time.sleep(9999999)# on the remote side, will call back to the callback function and return immediatelyremote_trigger_callback(callback)How it worksbridge.py contains a py2/3 compatible python object RPC proxy. One python environment sets up a server on a port, which clients connect to. The bridge provides a handful of commands to carry out remote operations against python objects in the other environment.A typical first step is remote_import() with a module to load in the target environment. This will make the RPC call to the remote bridge, which will load the module, then create a BridgeHandle to keep it alive and reference it across the bridge. It'll then return it to the local bridge, along with a list of the callable and non-callable attributes of the module.At the local bridge, this will be deserialized into a BridgedObject, which overrides __getattribute__ and __setattr__ to catch any get/set to the attribute fields, and proxy them back across to the remote bridge, using the bridge handle reference so it knows which module (or other object) we're talking about.The __getattribute__ override also affects callables, so doing bridged_obj.func() actually returns a BridgedCallable object, which is then invoked (along with any args/kwargs in use). This packs the call parameters off to the remote bridge, which identifies the appropriate object and invokes the call against it, then returns the result.The bridges are symmetric, so the local bridge is able to send references to local python objects to the remote bridge, and have them used over there, with interactions being sent back to the local bridge (e.g., providing a callback function as an argument works).Finally, there's a few other miscellaneous features to make life easier - bridged objects which are python iterators/iterables will behave as iterators/iterables in the remote environment, and bridged objects representing types can be inherited from to make your own subclasses of them (note that this will actually create the subclass in the remote environment - this is designed so you can create types to implement Java interfaces for callbacks/listeners/etc in Jython environments, so it was easier to make sure they behave if they're created in the Jython environment).Design principlesNeeds to be run in Jython 2.7 and Python 3Needs to be easy to install in constrained environments - no pip install, just add a single directory
(these two requirements ruled out some of the more mature Python RPC projects I looked into)TestedAutomatically tested on Python 3.10->Python 2.7, Python 3.11->Python 2.7, Python 2.7->Python 2.7, Python 2.7->Python 3.10, Python 3.11->Python 3.10TODOHandle server/client teardown cleanlyExceptions - pull traceback info in the exceptions we handle for pushing backBetter transport/serialization (JSON/TCP just feels wrong)Better threadpool control (don't keep all threads around forever, allow some to die off)ContributorsThx @fmagin for better iPython support, and much more useful reprs!Thanks also to @fmagin for remote_eval, allowing faster remote processing for batch queries!