107 matches found
polyswarm-api (>=0.1.0, <=0.2.2), polyswarm-client (>=1.0.0rc0, <=1.0.2) +1 more potentially affected by CVE-2023-49082 via aiohttp (2.3.1)
aiohttp PYPI version 2.3.1 is affected by a known vulnerability. The following packages have a transitive dependency on aiohttp and may be impacted: - polyswarm-api =0.1.0, =1.0.0rc0, =0.2.0a7, =0.2.0a10 Source cves: CVE-2023-49082 Source advisory: OSV:GHSA-QVRW-V9RV-5RJX...
polyswarm-api (>=0.1.0, <=0.2.2), polyswarm-client (>=1.0.0rc0, <=1.0.2) +1 more potentially affected by unknown CVE via aiohttp (2.3.1)
aiohttp PYPI version 2.3.1 is affected by a known vulnerability. The following packages have a transitive dependency on aiohttp and may be impacted: - polyswarm-api =0.1.0, =1.0.0rc0, =0.2.0a7, =0.2.0a10 Source cves: unknown CVE Source advisory: OSV:GHSA-PJJW-QHG8-P2P9...
polyswarm-api (>=0.1.0, <=0.2.2), polyswarm-client (>=1.0.0rc0, <=1.0.2) +1 more potentially affected by CVE-2023-47627 via aiohttp (2.3.1)
aiohttp PYPI version 2.3.1 is affected by a known vulnerability. The following packages have a transitive dependency on aiohttp and may be impacted: - polyswarm-api =0.1.0, =1.0.0rc0, =0.2.0a7, =0.2.0a10 Source cves: CVE-2023-47627 Source advisory: OSV:GHSA-GFW2-4JVH-WGFG...
polyswarm-api (>=0.1.0, <=0.2.2), polyswarm-client (>=1.0.0rc0, <=1.0.2) +1 more potentially affected by CVE-2023-47627 via aiohttp (2.3.1)
aiohttp PYPI version 2.3.1 is affected by a known vulnerability. The following packages have a transitive dependency on aiohttp and may be impacted: - polyswarm-api =0.1.0, =1.0.0rc0, =0.2.0a7, =0.2.0a10 Source cves: CVE-2023-47627 Source advisory: OSV:PYSEC-2023-246...
polyswarm-api (>=0.1.0, <=0.2.2), polyswarm-client (>=1.0.0rc0, <=1.0.2) +1 more potentially affected by CVE-2023-47641 via aiohttp (2.3.1)
aiohttp PYPI version 2.3.1 is affected by a known vulnerability. The following packages have a transitive dependency on aiohttp and may be impacted: - polyswarm-api =0.1.0, =1.0.0rc0, =0.2.0a7, =0.2.0a10 Source cves: CVE-2023-47641 Source advisory: OSV:GHSA-XX9P-XXVH-7G8J...
polyswarm-api (>=0.1.0, <=0.2.2), polyswarm-client (>=1.0.0rc0, <=1.0.2) +1 more potentially affected by CVE-2023-37276 via aiohttp (2.3.1)
aiohttp PYPI version 2.3.1 is affected by a known vulnerability. The following packages have a transitive dependency on aiohttp and may be impacted: - polyswarm-api =0.1.0, =1.0.0rc0, =0.2.0a7, =0.2.0a10 Source cves: CVE-2023-37276 Source advisory: OSV:GHSA-45C4-8WX5-QW6W...
polyswarm-api (>=0.1.0, <=0.2.2), polyswarm-client (>=1.0.0rc0, <=1.0.2) +1 more potentially affected by CVE-2023-37276 via aiohttp (2.3.1)
aiohttp PYPI version 2.3.1 is affected by a known vulnerability. The following packages have a transitive dependency on aiohttp and may be impacted: - polyswarm-api =0.1.0, =1.0.0rc0, =0.2.0a7, =0.2.0a10 Source cves: CVE-2023-37276 Source advisory: OSV:PYSEC-2023-120...
polyswarm-api (>=0.1.0, <=0.2.2), polyswarm-client (>=1.0.0rc0, <=1.0.2) +1 more potentially affected by CVE-2021-21330 via aiohttp (2.3.1)
aiohttp PYPI version 2.3.1 is affected by a known vulnerability. The following packages have a transitive dependency on aiohttp and may be impacted: - polyswarm-api =0.1.0, =1.0.0rc0, =0.2.0a7, =0.2.0a10 Source cves: CVE-2021-21330 Source advisory: OSV:PYSEC-2021-76...
polyswarm-api (>=0.1.0, <=0.2.2), polyswarm-client (>=1.0.0rc0, <=1.0.2) +1 more potentially affected by CVE-2021-21330 via aiohttp (2.3.1)
aiohttp PYPI version 2.3.1 is affected by a known vulnerability. The following packages have a transitive dependency on aiohttp and may be impacted: - polyswarm-api =0.1.0, =1.0.0rc0, =0.2.0a7, =0.2.0a10 Source cves: CVE-2021-21330 Source advisory: OSV:GHSA-V6WP-4M6F-GCJG...
Py-EVM Security Vulnerability
Py-EVM is a Python-based implementation of an Ethernet virtual machine. A security vulnerability exists in Py-EVM version 0.2.0-alpha.33. An attacker can exploit the vulnerability to cause a denial of service...
eth-cobra (>=0.1.0, <=0.1.1), eth-pm (0.1.0a23) +12 more potentially affected by CVE-2018-18920 via py-evm (>=0.2.0a16, <=0.2.0a33)
py-evm PYPI version =0.2.0a16, =0.1.0, =0.1.0b1, =0.1.0a18, =0.2.0rc1, =1.0.0a1, =0.1.2a2, =0.8.0, =0.0.1a3, =0.2.0, =0.1.0a12, =0.1.2b2, =0.1.2b4 Source cves: CVE-2018-18920 Source advisory: OSV:GHSA-VQGP-4JGJ-5J64...
eth-cobra (>=0.1.0, <=0.1.1), eth-pm (0.1.0a23) +12 more potentially affected by CVE-2018-18920 via py-evm (>=0.2.0a16, <=0.2.0a33)
py-evm PYPI version =0.2.0a16, =0.1.0, =0.1.0b1, =0.1.0a18, =0.2.0rc1, =1.0.0a1, =0.1.2a2, =0.8.0, =0.0.1a3, =0.2.0, =0.1.0a12, =0.1.2b2, =0.1.2b4 Source cves: CVE-2018-18920 Source advisory: GHSA-VQGP-4JGJ-5J64...
Py-EVM is vulnerable to arbitrary bytecode injection
Py-EVM v0.2.0-alpha.33 allows attackers to make a vm.executebytecode call that triggers computation.stack.values with '"stack": 100, 100, 0' where b'\x' was expected, resulting in an execution failure because of an invalid opcode. This is reportedly related to "smart contracts can be executed...
Denial Of Service (DoS)
py-evm is vulnerable to a denial of service DoS attack. A malicious user can pass a contract to the application to cause invalid values in the stack, crashing the application...
PYSEC-2018-96
Py-EVM v0.2.0-alpha.33 allows attackers to make a vm.executebytecode call that triggers computation.stack.values with '"stack": 100, 100, 0' where b'\x' was expected, resulting in an execution failure because of an invalid opcode. This is reportedly related to "smart contracts can be executed...
CVE-2018-18920
Py-EVM v0.2.0-alpha.33 allows attackers to make a vm.executebytecode call that triggers computation.stack.values with '"stack": 100, 100, 0' where b'\x' was expected, resulting in an execution failure because of an invalid opcode. This is reportedly related to "smart contracts can be executed...
PYSEC-2018-155
Py-EVM v0.2.0-alpha.33 allows attackers to make a vm.executebytecode call that triggers computation.stack.values with '"stack": 100, 100, 0' where b'\x' was expected, resulting in an execution failure because of an invalid opcode. This is reportedly related to "smart contracts can be executed...
PYSEC-2018-155
Py-EVM v0.2.0-alpha.33 allows attackers to make a vm.executebytecode call that triggers computation.stack.values with '"stack": 100, 100, 0' where b'\x' was expected, resulting in an execution failure because of an invalid opcode. This is reportedly related to "smart contracts can be executed...
eth-pm (0.1.0a23), eth-tester-rpc (>=0.1.0b1, <=0.2.0b1) +7 more potentially affected by CVE-2018-18920 via py-evm (>=0.2.0a16, <=0.2.0a32)
py-evm PYPI version =0.2.0a16, =0.1.0b1, =0.1.0a18, =0.1.2a2, =0.10.0, =0.0.1a3, =0.1.0a12, =0.1.2b2, =0.1.2b3 Source cves: CVE-2018-18920 Source advisory: OSV:PYSEC-2018-96...
CVE-2018-18920
Py-EVM v0.2.0-alpha.33 allows attackers to make a vm.executebytecode call that triggers computation.stack.values with '"stack": 100, 100, 0' where b'\x' was expected, resulting in an execution failure because of an invalid opcode. This is reportedly related to "smart contracts can be executed...