Products / picklescan
picklescan
59 records.
- PickleScan's profile.run blocklist mismatch allows exec() bypass A pickle calling the module-level profile run function reaches exec() because the scanner blocklist only matches the class-qualified names.
- PickleScan has multiple stdlib modules with direct RCE not in blocklist The scanner's blocklist omits several standard library modules that can run shell commands, so pickles using them are reported as clean.
- PickleScan's pkgutil.resolve_name has a universal blocklist bypass
- Picklescan (scan_pytorch) Bypass via dynamic eval MAGIC_NUMBER A pickle payload calls eval through __reduce__ with a magic-number value the scanner's opcode check misses but the real torch loader still reads.
- picklescan missing detection by simple obfuscation of a `builtins.eval` call A pickle payload hides a builtins eval call behind getattr, so the scanner does not flag it and the code runs when the file is loaded.
- picklescan vulnerable to arbitrary file create using logging.FileHandler
- picklescan has Arbitrary file read using `io.FileIO` A crafted pickle chains file-reading and HTTP-posting callables to send local file contents to an external server, evading the scanner's execution-focused blocklist.
- Picklescan is vulnerable to RCE via missing detection when calling built-in python _operator.attrgetter Picklescan does not flag _operator.attrgetter gadgets, so a hand-built pickle reaching __import__ runs shell commands when loaded.
- Picklescan is vulnerable to RCE through missing detection when calling numpy.f2py.crackfortran._eval_length A pickle using a numpy f2py helper as its reduce callable executes code on load, and picklescan fails to flag this gadget as dangerous.
- Picklescan is vulnerable to RCE via missing detection when calling built-in python _operator.methodcaller A pickle using the _operator.methodcaller reducer is not flagged by the scanner, so loading it still runs attacker-chosen commands.
- Picklescan is vulnerable to RCE via missing detection when calling numpy.f2py.crackfortran.getlincoef
- Picklescan is vulnerable to RCE through missing detection when calling numpy.f2py.crackfortran.myeval A pickle payload calling a numpy helper evades picklescan's blocklist, so a file reported safe still runs code when loaded.
- Picklescan does not block ctypes Picklescan's denylist omits ctypes, so a pickle that calls ctypes.WinDLL and foreign functions evades detection and runs native code on load.
- Picklescan has Incomplete List of Disallowed Inputs The pickle scanner's deny-list misses pydoc.locate and operator.methodcaller, so a crafted pickle chaining them to call os.system passes the scan.
- Picklescan is vulnerable to RCE via missing detection when calling numpy.f2py.crackfortran.param_eval A pickle payload calls a numpy helper that the scanner does not flag, so scanning passes and loading the file executes attacker-supplied code.
- Picklescan Bypasses Unsafe Globals Check using pty.spawn
- Picklescan vulnerable to Arbitrary File Writing
- Picklescan missing detection when calling numpy.f2py.crackfortran.getlincoef
- Picklescan missing detection when calling pty.spawn
- Picklescan is vulnerable to RCE through missing detection when calling built-in python operator.methodcaller
- Picklescan is Vulnerable to Unsafe Globals Check Bypass through Subclass Imports Pickles referencing subclasses of dangerous asyncio classes evade picklescan's exact module-name check, so their embedded payloads load and execute.
- Picklescan Bypass is Possible via File Extension Mismatch
- Picklescan: ZIP archive scan bypass is possible through non-exhaustive Cyclic Redundancy Check
- Picklescan is missing detection when calling built-in python idlelib.pyshell.ModifiedInterpreter.runcode A pickle payload calling idlelib's ModifiedInterpreter.runcode is not flagged by picklescan, so loading the malicious model file executes attacker code.
- Picklescan has a missing detection when calling built-in python idlelib.debugobj.ObjectTreeItem The pickle scanner does not flag calls to idlelib debugobj methods, so a malicious pickle that uses them passes the scan and runs commands when loaded.
- Picklescan is missing detection when calling built-in python cProfile.run A pickle payload calling cProfile.run executes arbitrary code on load, and the picklescan detector does not flag it.
- Picklescan is missing detection when calling pytorch function torch.utils.bottleneck.__main__.run_autograd_prof A crafted pickle calls a torch profiling helper that runs arbitrary code, and the scanner does not flag that function, so loading the file executes it.
- Picklescan has a missing detection when calling built-in python trace.Trace.run A pickle that calls trace.Trace.run to run a shell command is not flagged by the scanner, so loading it executes the code.
- Picklescan has a missing detection when calling built-in python profile.Profile.runctx A pickle whose reduce calls profile.Profile.runctx runs arbitrary code when loaded, and the scanner does not flag that built-in function.
- Picklescan has a missing detection when calling built-in python idlelib.autocomplete.AutoComplete.get_entity A pickle that calls idlelib AutoComplete.get_entity executes attacker code on load, and the scanner misses this built-in callable.
- Picklescan has a missing detection when calling built-in python idlelib.autocomplete.AutoComplete.fetch_completions A pickle payload calling idlelib's AutoComplete.fetch_completions is not flagged by picklescan, so loading it runs attacker-chosen code.
- Picklescan has a missing detection when calling built-in python idlelib.calltip.Calltip A pickle payload calls idlelib's Calltip.fetch_tip, which evaluates arbitrary expressions, and picklescan does not flag it, so unpickling runs attacker code.
- Picklescan is missing detection when calling built-in Python cProfile.runctx Picklescan does not flag cProfile.runctx, so a pickle that calls it to run arbitrary code passes the scan and executes on load.
- Picklescan has a missing detection when calling built-in python library idlelib.calltip.get_entity A pickle payload calls a standard library helper that evaluates strings as Python, and the scanner does not flag that call, so loading the file runs code.
- Picklescan has a missing detection when calling built-in python code.InteractiveInterpreter A malicious pickle calls the interactive interpreter's runcode method, which the scanner does not flag, so loading the file still runs attacker code.
- Picklescan has a missing detection when calling built-in python lib2to3.pgen2.grammar.Grammar.loads A pickle that calls lib2to3's Grammar.loads to run embedded code is not flagged by picklescan, so loading it executes the attacker's payload.
- Picklescan is missing detection when calling built-in python doctest.debug_script A pickle payload invokes doctest's debug_script to run embedded code, and the scanner does not flag that call.
- Picklescan has a missing detection when calling built-in python trace.Trace.runctx A pickle payload calling trace.Trace.runctx during reconstruction runs commands on load, and the scanner fails to flag it as dangerous.
- Picklescan is missing detection when calling built-in python idlelib.pyshell.ModifiedInterpreter.runcommand
- Picklescan is missing detection when calling built-in python idlelib.run.Executive.runcode
- Picklescan is missing detection when calling built-in python lib2to3.pgen2.pgen.ParserGenerator.make_label
- Picklescan is missing detection when calling built-in python library asyncio.unix_events._UnixSubprocessTransport._start
- Picklescan has a missing detection when calling built-in python profile.Profile.run
- Picklescan is missing detection when calling built-in python ensurepip._run_pip
- Picklescan missing detection when calling pytorch function torch.utils.bottleneck.__main__.run_cprofile A pickle payload calls a torch profiling helper that runs arbitrary code, and the scanner fails to flag that call, so loading the file executes it.
- Picklescan missing detection when calling pytorch function torch._dynamo.guards.GuardBuilder.get A PyTorch dynamo helper is missing from the scanner's list, so a pickle that calls it to run shell commands is reported as safe.
- Picklescan missing detection when calling pytorch function torch.fx.experimental.symbolic_shapes.ShapeEnv.evaluate_guards_expression A pickle payload calling a PyTorch symbolic shapes function evades picklescan's detection yet executes arbitrary code when loaded.
- Picklescan missing detection when calling pytorch function torch.utils.collect_env.run A pickle that calls PyTorch's collect_env run helper to execute a shell command is not detected by picklescan, so loading it runs the command.
- Picklescan missing detection when calling pytorch function torch.utils.data.datapipes.utils.decoder.basichandlers
- Picklescan missing detection when calling pytorch function torch.jit.unsupported_tensor_ops.execWrapper