{ "CVE_data_meta": { "ASSIGNER": "cve@mitre.org", "ID": "CVE-2022-35411", "STATE": "PUBLIC" }, "affects": { "vendor": { "vendor_data": [ { "product": { "product_data": [ { "product_name": "n/a", "version": { "version_data": [ { "version_value": "n/a" } ] } } ] }, "vendor_name": "n/a" } ] } }, "data_format": "MITRE", "data_type": "CVE", "data_version": "4.0", "description": { "description_data": [ { "lang": "eng", "value": "rpc.py through 0.6.0 allows Remote Code Execution because an unpickle occurs when the \"serializer: pickle\" HTTP header is sent. In other words, although JSON (not Pickle) is the default data format, an unauthenticated client can cause the data to be processed with unpickle." } ] }, "problemtype": { "problemtype_data": [ { "description": [ { "lang": "eng", "value": "n/a" } ] } ] }, "references": { "reference_data": [ { "url": "https://medium.com/@elias.hohl/remote-code-execution-0-day-in-rpc-py-709c76690c30", "refsource": "MISC", "name": "https://medium.com/@elias.hohl/remote-code-execution-0-day-in-rpc-py-709c76690c30" }, { "url": "https://github.com/ehtec/rpcpy-exploit", "refsource": "MISC", "name": "https://github.com/ehtec/rpcpy-exploit" }, { "url": "https://github.com/abersheeran/rpc.py/commit/491e7a841ed9a754796d6ab047a9fb16e23bf8bd", "refsource": "MISC", "name": "https://github.com/abersheeran/rpc.py/commit/491e7a841ed9a754796d6ab047a9fb16e23bf8bd" }, { "refsource": "MISC", "name": "http://packetstormsecurity.com/files/167872/rpc.py-0.6.0-Remote-Code-Execution.html", "url": "http://packetstormsecurity.com/files/167872/rpc.py-0.6.0-Remote-Code-Execution.html" } ] } }