CertiK reviewed pNetwork on 6 Jan 2023: 42 findings, 0 critical; 34 marked fixed, 8 open.
Report hosted on skynet.certik.com.
Trustblock does not review code.
Statuses are the security firm’s own, from its report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 0 | 0 | 6 |
| Medium | 2 | 0 | 6 |
| Low | 6 | 0 | 22 |
As directed in the `README` file of the project, the first trusted block that is sealed to the database should not contain any transactions related to pTokens otherwise they will be ignored. The list of transactions are a part of the valid JSON format in which the block is submitted and parsed. However, there is no step in the transaction of the core with the database (different from an actual btc "transaction") where the list of transactions are checked for ptoken transactions. Risk: user of library can accidentally supply initial block with transactions that will be silently ignored.
Currently `get_x_random_bytes` relies on `thread_rng()` which is the standard random generator that takes randomness from the system. This may allow attacker to reduce search space of potential random seeds and cause brute force attack against private keys, feasible.
The function `get_eos_enabled_protocol_features_from_db` will accept all features that are fetched from database regardless if they are correct, supported, or known. This may lead to situation where an attacker who managed node operators in the past has enabled features that are not present or known to current version of software (i.e. could clean traces after their activity).
If converting an asset from lower precision to higher precision there is a loss of information. For example from 9 decimal places of precision to 18 decimal places of precision, there is a loss of information. It is unclear how the dust is treated in such a case. This occurs for each of the conversion functions: - `convert_u64_to_eos_asset()`; - `convert_u256_to_eos_asset_string;convert_eos_asset_to_eth_amount()`.
Currently, there is no established process described in the code for introducing new ids in the `chain_ids` Enum. It puts the ecosystem at risk since if there are contributors creating new bridges, they may create overlapping identifiers for chains which could result in collisions.
Currently, Ethereum transactions are formatted as legacy transactions using `gas_price`. This causes the gas fees and hence transactions fees to be maximized as `max_priority_fee_per_gas` is set to `transaction.gas_price` and `max_fee_per_gas` is set to `transaction.gas_price`.
Currently a lot of functions that are not meant to be used in production code are not explicitly limited to debug mode with `#[cfg(feature = "debug")]` . This mean lead to accidentally compiling functions never intended to be used in production , into release build , and creating new attack vectors.
Data is written to DB (database) without encryption. If any existing database is persistent outside TEE, that implies that private keys (and other non-public data) can leak from TEE to outside.
The report names a repository or files. Open the report to see its scope.
1,045 projects reviewed · 1,376 reports · latest May 2025
See CertiK’s auditsSomething wrong on this page? A missing report, a wrong date, a finding that was fixed since. Tell us and we check it against its source.
Tell us