BOSagora has 4 public audit reports from CertiK; the latest is CertiK, 9 Jun 2024; no critical findings reported.
Last updated . It holds audits and findings, contracts and incidents up to Nov 2026. Trustblock does not review code.
Statuses are the security firms’ own
9 findings are still open or acknowledged in the firms’ reports: 2 high, 1 medium, 6 low (6 open, 3 acknowledged).
Initial Token Distribution and Mint Centralizatio
BOSagora - Loyal Token · CertiK · 9 Jun 2024 · Report ↗
Initial Token Distribution and Mint Centralizatio
BOSagora - Multi-Signature Wallet · CertiK · 9 Jun 2024 · Report ↗
Inconsistency Via Out-of-Order EIPs Leads To `eth
BOSagora - EL · CertiK · 9 Jun 2024 · Report ↗
Identified Unpatched Issues in Forked Geth Codeba
BOSagora - EL · CertiK · 9 Jun 2024 · Report ↗
Building Failure Caused By Outdated WORKSPACE Tar
BOSagora - CL · CertiK · 9 Jun 2024 · Report ↗
Identified Unpatched Issues in Forked Prysm Codeb
BOSagora - CL · CertiK · 9 Jun 2024 · Report ↗
Incompatible Agora EL Import For Agora CL
BOSagora - CL · CertiK · 9 Jun 2024 · Report ↗
Reward Calculation Optimization
BOSagora - CL · CertiK · 9 Jun 2024 · Report ↗
Vulnerable Dependencies
BOSagora - CL · CertiK · 9 Jun 2024 · Report ↗
Newest first
| Report | Security firm | Date | Scope | Critical findings | Findings | Source |
|---|---|---|---|---|---|---|
| BOSagora - EL | Security firm: CertiK | Date: | Scope: Files listed | None open | Findings: 1 high · 2 medium · 1 low 2 fixed · 1 acknowledged · 1 open | skynet.certik.com ↗ |
| BOSagora - Loyal Token | Security firm: CertiK | Date: | Scope: Files listed | None open | Findings: 1 high · 1 medium 1 fixed · 1 acknowledged | skynet.certik.com ↗ |
| BOSagora - Multi-Signature Wallet | Security firm: CertiK | Date: | Scope: Files listed | None open | Findings: 1 high · 1 medium · 9 low 10 fixed · 1 acknowledged | skynet.certik.com ↗ |
| BOSagora - CL | Security firm: CertiK | Date: | Scope: Files listed | None open | Findings: 1 medium · 6 low 2 fixed · 5 open | skynet.certik.com ↗ |
Statuses are the security firm’s own, from each report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 0 | 2 | 1 |
| Medium | 1 | 0 | 4 |
| Low | 5 | 1 | 10 |
Repository: - agora-el Commit hash: - [`b313d5358345f55bbc4e79b05904b5782227353f`](https://github.com/bosagora/agora-el/tree/b313d5358345f55bbc4e79b05904b5782227353f) Files: - agora-el/core/vm/operations_acl.go - agora-el/params/config.go The coordination of EIPs that rely on the ctx block number is lax within EVM stacks. Within the output of `makeCallVariantGasCallEIP2929`, there exists a risk of value overflow. ```go func makeCallVariantGasCallEIP2929(oldCalculator gasFunc) gasFunc { return func(evm *EVM, contract *Contract, stack *Stack, mem *Memory, memorySize uint64) (uint64, error) { ... gas, err := oldCalculator(evm, contract, stack, mem, memorySize) if warmAccess || err != nil { return gas, err } // In case of a cold access, we temporarily add the cold charge back, and also // add it to the returned gas. By adding it to the return, it will be charged // outside of this function, as part of the dynamic gas, and that will make it // also become correctly reported to tracers. contract.Gas += coldCost return gas + coldCost, nil } } ``` This vulnerability opens up the possibility of a targeted attack scenario where a specific gas value is strategically provided to the `CALL` operation through the stack. By also requesting the maximum memory allocation, it could trigger an overflow in the resultant return value of `makeCallVariantGasCallEIP2929()`. This overflow could potentially lead to a situation where the `CALL` operation is undercharged inadequately, allowing for the allocation of the full 128GB memory capacity. It could easily lead to out-of-memory issue on the targeted serving node. References: - [*geth-out-of-order-eip-application-denial-of-service*](https://iosiro.com/blog/geth-out-of-order-eip-application-denial-of-service) - [*core/vm, params: ensure order of forks, prevent overflow #29023*](https://github.com/ethereum/go-ethereum/pull/29023)
Open the reportRepository: - agora-cl Commit hash: - [`87ad355e94635ccf7fe4b2fb1cf5e308fcd9e5d5`](https://github.com/bosagora/agora-cl/tree/87ad355e94635ccf7fe4b2fb1cf5e308fcd9e5d5) Files: - agora-cl/WORKSPACE The WORKSPACE file specifies the external libraries, tools, and packages that the project depends on. It uses Bazel's repository rules to fetch and integrate these dependencies into the project's build environment. However, the dependency `com_grail_bazel_toolchain`'s repo `https://github.com/grailbio/bazel-toolchain` has been changed to `https://github.com/bazel-contrib/toolchains_llvm`, which would bring the error while building the project.
Open the reportRepository: - agora-cl In the Prysm codebase, several issues were identified and resolved following the release of version 4.0.5. However, these fixes have not been implemented in the agora-cl codebase. While these issues may not be critical, addressing them would enhance the project's resilience and overall robustness. ### Consensus-Related Issues - [*Fix sandwich attack on honest reorgs #12418*](https://github.com/prysmaticlabs/prysm/pull/12418) - [*fixed erroneous panic #12450*](https://github.com/prysmaticlabs/prysm/pull/12450) ### Sync-Related Issues - [*Checkpoint sync: get block using state.latest_block_header.slot #12447*](https://github.com/prysmaticlabs/prysm/pull/12447) - [*fix: late block task wait for initial sync #12526*](https://github.com/prysmaticlabs/prysm/pull/12526) - [*fix: prune invalid blocks during initial sync #12591*](https://github.com/prysmaticlabs/prysm/pull/12591) - [*Use last optimistic status on batches #12741*](https://github.com/prysmaticlabs/prysm/pull/12741) - [*set optimistic status in head at init sync #12748*](https://github.com/prysmaticlabs/prysm/pull/12748) - [*Check block exists in pending queue before requesting from peer #13013*](https://github.com/prysmaticlabs/prysm/pull/13013) - [*Fix Pending Queue Expiration Bug #13104*](https://github.com/prysmaticlabs/prysm/pull/13104) - [*Ignore Pubsub Messages Hitting Context Deadlines #13716*](https://github.com/prysmaticlabs/prysm/pull/13716) ### State-Related Issues - [*Handle Epoch Boundary Misses #12579*](https://github.com/prysmaticlabs/prysm/pull/12579) - [*fix: set current and prev epoch participations for interop genesis #12814*](https://github.com/prysmaticlabs/prysm/pull/12814) - [*blockchain: Check nilness before accessing head in IsOptimistic #13439*](https://github.com/prysmaticlabs/prysm/pull/13439) ### Cache-Related Issues - [*fix: update committee cache epoch + 1 #12667*](https://github.com/prysmaticlabs/prysm/pull/12667) - [*Fix Update Of Committee Cache #12668*](https://github.com/prysmaticlabs/prysm/pull/12668) - [*Fix: use correct context for UpdateCommitteeCache #12691*](https://github.com/prysmaticlabs/prysm/pull/12691) - [*Don't prune proposer ID cache in a loop #12996*](https://github.com/prysmaticlabs/prysm/pull/12996) - [*Fix minor issue in blsToExecChange message validator #13498*](https://github.com/prysmaticlabs/prysm/pull/13498) ### P2P-Related Issues - [*Fix the bug that return 500 in /eth/v1/node/peers interface #12483*](https://github.com/prysmaticlabs/prysm/pull/12483) - [*Fix minor issue in blsToExecChange message validator #13498*](https://github.com/prysmaticlabs/prysm/pull/13498) ### RPC/API-Related Issues - [*Fix Epoch Participation Parsing #12534*](https://github.com/prysmaticlabs/prysm/pull/12534) - [*Fix Uint256 Json Parsing #12540*](https://github.com/prysmaticlabs/prysm/pull/12540) - [*Fix: Size of SyncCommitteeBits should be 64 bytes (512 bits) instead of 512 bytes #12586*](https://github.com/prysmaticlabs/prysm/pull/12586) - [*Return historical roots in Capella state #12642*](https://github.com/prysmaticlabs/prysm/pull/12642) - [*Fix Pagination Panic #12932*](https://github.com/prysmaticlabs/prysm/pull/12932) - [*Handle hex in Blocker, Stater and optimistic mode checker #12979*](https://github.com/prysmaticlabs/prysm/pull/12979) - [*Enhance Validation for Block by Root RPC Requests #13184*](https://github.com/prysmaticlabs/prysm/pull/13184) ### Config-Related Issues - [*Add missing config yamls for domains #12442*](https://github.com/prysmaticlabs/prysm/pull/12442) - [*Increase validator client startup proposer settings deadline #12533*](https://github.com/prysmaticlabs/prysm/pull/12533) ### Log-Related Issues - [*log the right blocknumber #12529*](https://github.com/prysmaticlabs/prysm/pull/12529) - [*Correct log level for 'Could not send a chunked response' #12562*](https://github.com/prysmaticlabs/prysm/pull/12562) ### Others - [*Release Lock Before Panicking #12464*](https://github.com/prysmaticlabs/prysm/pull/12464) - [*Reopenning fix for keystore field name change to align with EIP2335 #12530*](https://github.com/prysmaticlabs/prysm/pull/12530) - [*Ensure File Does Not Exist #12536*](https://github.com/prysmaticlabs/prysm/pull/12536) - [*Fix prysmctl writing empty JSON/YAML files #12599*](https://github.com/prysmaticlabs/prysm/pull/12599) - [*Fix Withdrawals Marshalling #13066*](https://github.com/prysmaticlabs/prysm/pull/13066) - [*fix segmentation fork when Capella for epoch is MaxUint64 #13126*](https://github.com/prysmaticlabs/prysm/pull/13126) - [*Fix port logging in bootnode #13457*](https://github.com/prysmaticlabs/prysm/pull/13457)
Open the reportRepository: - agora-cl Commit hash: - [`87ad355e94635ccf7fe4b2fb1cf5e308fcd9e5d5`](https://github.com/bosagora/agora-cl/tree/87ad355e94635ccf7fe4b2fb1cf5e308fcd9e5d5) Files: - agora-cl/go.mod - agora-cl/cmd/prysmctl/testnet/generate_genesis.go In agora-cl, the agora-el is supposed to be the dependency package. However, the project is importing **github.com/ethereum/go-ethereum v1.11.3** instead of the agora-el, which will not maintain the agora-specific features which will bring inconsistent issues. Take `generate-genesis` functionality as an example, when using functionality like `generate-genesis`, the following fields will be ignored in the generated gensesis.json: ```json "bosagoraBlock": ..., "bosagora": { "commonsBudget": "0x", "commonsBudgetReward": ..., "lastCommonsBudgetRewardBlock": ... }, ```
Open the reportRepository: - agora-cl Commit hash: - [`87ad355e94635ccf7fe4b2fb1cf5e308fcd9e5d5`](https://github.com/bosagora/agora-cl/tree/87ad355e94635ccf7fe4b2fb1cf5e308fcd9e5d5) Files: - agora-cl/beacon-chain/core/altair/block.go - agora-cl/agora/block_rewards.go The function `ValidatorRewardPerEpoch` calculates the validator's reward based on its `effectiveBalance` relative to the `totalBalance` within a specific epoch. The calculation follows this formula: > ValidatorRewardPerEpoch = effectiveBalance * allocatedValidatorRewardsPerEpoch / totalBalance **agora-cl/agora/block_rewards.go** ```go=50 func ValidatorRewardPerEpoch(secondsSinceGenesis uint64, totalBalance uint64, effectiveBalance uint64, cfg RewardConfig) (uint64, error) { if totalBalance <= 0 { return 0, errors.New("active balance can't be 0") } allocatedValidatorRewardsPerEpoch := new(big.Int).SetUint64(AllocatedValidatorRewardsPerEpoch(secondsSinceGenesis, cfg)) increments := new(big.Int).SetUint64(effectiveBalance / cfg.EffectiveBalanceIncrement) bigTotalBalance := new(big.Int).SetUint64(totalBalance) bigEffectiveBalance := new(big.Int).SetUint64(cfg.EffectiveBalanceIncrement) bigEffectiveBalance.Mul(bigEffectiveBalance, increments) bigEffectiveBalance.Mul(bigEffectiveBalance, allocatedValidatorRewardsPerEpoch) bigEffectiveBalance.Div(bigEffectiveBalance, bigTotalBalance) return bigEffectiveBalance.Uint64(), nil } ``` The function is invoked in processes such as attestation and epoch precompute. However, in the `SyncRewards` function, replacing the constant `EffectiveBalance` with `EffectiveBalanceIncrement` is not suitable for calculating the base rewards per increment. **agora-cl/beacon-chain/core/altair/block.go** ```go=157 func SyncRewards(secondsSinceGenesis uint64, activeBalance uint64) (proposerReward, participantReward uint64, err error) { cfg := params.BeaconConfig() totalActiveIncrements := activeBalance / cfg.EffectiveBalanceIncrement agoraConfig := agora.MakeAgoraRewardConfig(cfg) baseRewardPerInc, err := agora.ValidatorRewardPerEpoch(secondsSinceGenesis, activeBalance, cfg.EffectiveBalanceIncrement, agoraConfig) if (err != nil) { return 0, 0, err } totalBaseRewards := baseRewardPerInc * totalActiveIncrements ... } ``` To compute `totalBaseRewards` efficiently, it is advisable to utilize the `AllocatedValidatorRewardsPerEpoch` function from the `block_rewards.go` file, avoiding complex and unnecessary computations.
Open the reportRepository: - agora-cl Commit hash: - [`87ad355e94635ccf7fe4b2fb1cf5e308fcd9e5d5`](https://github.com/bosagora/agora-cl/tree/87ad355e94635ccf7fe4b2fb1cf5e308fcd9e5d5) Files: - agora-cl/deps.bzl - agora-cl/go.mod - agora-cl/go.sum The go crypto library has released a security update to fix a vulnerability identified as CVE-2023-48795. This vulnerability affects the SSH (Secure Shell) protocol. The version of the libp2p library being used falls within the range of versions affected by CVE-2023-39533 and CVE-2023-40583. It is highly recommended to upgrade the dependency to a patched version of the library, which will help mitigate the security risks associated with these vulnerabilities. References: - [*Update Our Golang Crypto Library #13415*](https://github.com/prysmaticlabs/prysm/pull/13415) - [*libp2p-CVE-2023-39533*](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-39533) - [*libp2p-CVE-2023-40583*](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-40583)
Open the reportThe reports name a repository or files. Open a report to see its scope.
Trustblock holds 4 public audit reports for BOSagora, dated 9 Jun 2024 to 9 Jun 2024. The latest is by CertiK (“BOSagora - EL”).
CertiK wrote the 4 reports Trustblock holds for BOSagora.
9 findings are still open or acknowledged in the firms’ reports: 2 high, 1 medium, 6 low (6 open, 3 acknowledged). No critical finding is reported. Statuses are the security firms’ own.
Is this your project? Show this record on your own website. The label states what the record holds, links to this page and updates by itself. It is free and needs no sign-in.
Automatic: the three strongest facts of this project’s own record (its last audit and two more), highlighted. They update with the record. Picking a fact turns Automatic off.
<head><script src="https://widget.trustblock.run/project-widget.min.js" defer></script></head><body><divdata-tb-project-widgetdata-tb-project-slug="bosagora"></div></body>
Paste the code where the label should appear. It uses no API credit and updates by itself.
Something 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