Vault Contracts v2 Audit | Rho Labs | Halborn Audit Reports

Summary

100% of all REPORTED Findings have been addressed

About this report

Assessment Type

Assurance Assessment

Date of Engagement

July 15th, 2025 - July 29th, 2025

Source Code

vault-contracts-v2

Assessed Commit ID

25d8204

Severity Breakdown

1Acknowledged
1Risk Accepted
16Solved
18All Findings

Critical0
High1
- 1Solved
Medium1
- 1Risk A.
Low3
- 3Solved
Informational13
- 1Ack.
- 12Solved

Introduction#

Rho Labs engaged Halborn to perform a security assessment of their smart contracts from July 15th, 2025, to July 28th, 2025. The assessment scope was limited to the smart contracts provided to Halborn. Commit hashes and additional details are available in the Scope section of this report.

The Rho Labs codebase in scope consists of a smart contract system for asset management, featuring ERC4626-compliant vaults, allocator and off-chain strategy vaults, a secure router for user and vault interactions, and robust access control. The system supports oracle-driven NAV reporting, and protocol-level controls for asset flows and permissions.

Assessment Summary#

Halborn was allocated 10 days for this engagement and assigned 1 full-time security engineer to conduct a comprehensive review of the smart contracts within scope. The engineer is an expert in blockchain and smart contract security, with advanced skills in penetration testing and smart contract exploitation, as well as extensive knowledge of multiple blockchain protocols.

The objectives of this assessment were to:

Identify potential security vulnerabilities within the smart contracts.
Verify that the smart contract functionality operates as intended.

In summary, Halborn identified several areas for improvement to reduce the likelihood and impact of potential risks, which were mostly addressed by the Rho Labs team. The primary recommendations were:

Replace vault.maxWithdraw(vaultAddress, vaultAddress, packages) with vault.maxWithdraw(address(this), address(this), packages) in _calcTotalSubVaultsAssets to ensure the calculation reflects the parent vault’s actual claim on the subVault’s assets.
Fund the vault with a meaningful initial deposit immediately after deployment and before allowing public deposits, ensuring a fair initial share/asset ratio.
Enforce at vault or ERC20Storage initialization that any asset marked as a wrapped native token has the same number of decimals as the native token for the deployment chain.

Test Approach and Methodology#

Halborn conducted a combination of manual code review and automated security testing to balance efficiency, timeliness, practicality, and accuracy within the scope of this assessment. While manual testing is crucial for identifying flaws in logic, processes, and implementation, automated testing enhances coverage of smart contracts and quickly detects deviations from established security best practices.

The following phases and associated tools were employed throughout the term of the assessment:

Research into the platform's architecture, purpose and use.
Manual code review and walkthrough of smart contracts to identify any logical issues.
Comprehensive assessment of the safety and usage of critical Solidity variables and functions within scope that could lead to arithmetic-related vulnerabilities.
Local testing using custom scripts (Foundry).
Fork testing against main networks (Foundry).
Static security analysis of scoped contracts, and imported functions (Slither).

Risk Methodology#

Every vulnerability and issue observed by Halborn is ranked based on two sets of Metrics and a Severity Coefficient. This system is inspired by the industry standard Common Vulnerability Scoring System.

The two Metric sets are: Exploitability and Impact. Exploitability captures the ease and technical means by which vulnerabilities can be exploited and Impact describes the consequences of a successful exploit.

The Severity Coefficients is designed to further refine the accuracy of the ranking with two factors: Reversibility and Scope. These capture the impact of the vulnerability on the environment as well as the number of users and smart contracts affected.

The final score is a value between 0-10 rounded up to 1 decimal place and 10 corresponding to the highest security risk. This provides an objective and accurate rating of the severity of security vulnerabilities in smart contracts.

The system is designed to assist in identifying and prioritizing vulnerabilities based on their level of risk to address the most critical issues in a timely manner.

4.1 EXPLOITABILITY

Attack Origin (AO):

Captures whether the attack requires compromising a specific account.

Attack Cost (AC):

Captures the cost of exploiting the vulnerability incurred by the attacker relative to sending a single transaction on the relevant blockchain. Includes but is not limited to financial and computational cost.

Attack Complexity (AX):

Describes the conditions beyond the attacker’s control that must exist in order to exploit the vulnerability. Includes but is not limited to macro situation, available third-party liquidity and regulatory challenges.

Metrics:

EXPLOITABILITY METRIC ( $m_e$ )	METRIC VALUE	NUMERICAL VALUE
Attack Origin (AO)	Arbitrary (AO:A)	1
Attack Origin (AO)	Specific (AO:S)	0.2
Attack Cost (AC)	Low (AC:L)	1
	Medium (AC:M)	0.67
	High (AC:H)	0.33
Attack Complexity (AX)	Low (AX:L)	1
	Medium (AX:M)	0.67
	High (AX:H)	0.33

Exploitability

E

is calculated using the following formula:

$E = \prod m_e$

4.2 IMPACT

Confidentiality (C):

Measures the impact to the confidentiality of the information resources managed by the contract due to a successfully exploited vulnerability. Confidentiality refers to limiting access to authorized users only.

Integrity (I):

Measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of data stored and/or processed on-chain. Integrity impact directly affecting Deposit or Yield records is excluded.

Availability (A):

Measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability. This metric refers to smart contract features and functionality, not state. Availability impact directly affecting Deposit or Yield is excluded.

Deposit (D):

Measures the impact to the deposits made to the contract by either users or owners.

Yield (Y):

Measures the impact to the yield generated by the contract for either users or owners.

Metrics:

IMPACT METRIC ( $m_I$ )	METRIC VALUE	NUMERICAL VALUE
Confidentiality (C)	None (C:N)	0
	Low (C:L)	0.25
	Medium (C:M)	0.5
	High (C:H)	0.75
	Critical (C:C)	1
Integrity (I)	None (I:N)	0
	Low (I:L)	0.25
	Medium (I:M)	0.5
	High (I:H)	0.75
	Critical (I:C)	1
Availability (A)	None (A:N)	0
	Low (A:L)	0.25
	Medium (A:M)	0.5
	High (A:H)	0.75
	Critical (A:C)	1
Deposit (D)	None (D:N)	0
	Low (D:L)	0.25
	Medium (D:M)	0.5
	High (D:H)	0.75
	Critical (D:C)	1
Yield (Y)	None (Y:N)	0
	Low (Y:L)	0.25
	Medium (Y:M)	0.5
	High (Y:H)	0.75
	Critical (Y:C)	1

Impact

I

is calculated using the following formula:

$I = max(m_I) + \frac{\sum{m_I} - max(m_I)}{4}$

4.3 SEVERITY COEFFICIENT

Reversibility (R):

Describes the share of the exploited vulnerability effects that can be reversed. For upgradeable contracts, assume the contract private key is available.

Scope (S):

Captures whether a vulnerability in one vulnerable contract impacts resources in other contracts.

Metrics:

SEVERITY COEFFICIENT ( $C$ )	COEFFICIENT VALUE	NUMERICAL VALUE
Reversibility ( $r$ )	None (R:N)	1
	Partial (R:P)	0.5
	Full (R:F)	0.25
Scope ( $s$ )	Changed (S:C)	1.25
Scope ( $s$ )	Unchanged (S:U)	1

Severity Coefficient

C

is obtained by the following product:

$C = rs$

The Vulnerability Severity Score

S

is obtained by:

$S = min(10, EIC * 10)$

The score is rounded up to 1 decimal places.

Critical	High	Medium	Low	Informational
9 - 10	7 - 8.9	4.5 - 6.9	2 - 4.4	0 - 1.9

Scope#

(a) Repository:vault-contracts-v2

(b) Assessed Commit ID:25d820431b878d5235fd62f74b6a66991371ac67

49 files

contracts

49 files

access-control

4 files

AccessControlManager.sol

solidity

IAccessControlManager.sol

solidity

IAccessControlManagerErrors.sol

solidity

Roles.sol

solidity

configuration

5 files

Configurator.sol

solidity

ContractProvider.sol

solidity

IConfigurator.sol

solidity

IContractProvider.sol

solidity

IContractProviderErrors.sol

solidity

Out-of-Scope:Third party dependencies and economic attacks.

4d9b733e2bc8522a968441596635f04582bae3e6 04ba0175aa674202282fa431e4b42d1bb9dac852 15d7ec1e6e956c5a70f1ad5275977913580c620d 2d334b7bd26567c9a2a638627383969303234602 1169abb3bdb10feb973d7c4ff086165b12b36209 456581ae14bc3c6ed225a3a63280761540555d0a

Out-of-Scope: New features/implementations after the remediation commit IDs.

Assessment Summary & Findings Overview#

#	Title	Severity	Score	Status
HAL-01	Incorrect address used during sub vaults asset calculation	High	8.1	Solved07/29/2025
HAL-02	Share inflation attack possible in AllocatorVault with zero decimals offset	Medium	5.0	Risk Accepted08/07/2025
HAL-03	Potential value mismatch when adding ERC20 and native token deposits	Low	3.1	Solved07/29/2025
HAL-04	Zero address and zero ID insertion possible in IterableIdAddressSet	Low	2.5	Solved07/29/2025
HAL-05	Decimals mismatch between parent and subVaults could break accounting	Low	2.0	Solved08/06/2025
HAL-06	Insufficient input validation	Informational	1.5	Acknowledged07/30/2025
HAL-07	Inconsistent role ID derivation reduces maintainability	Informational	0.8	Solved07/29/2025
HAL-08	Unvalidated offset parameter in role address query	Informational	0.8	Solved07/29/2025
HAL-09	Duplicated logic between previewDeposit and _previewDeposit can lead to inconsistencies	Informational	0.8	Solved08/06/2025
HAL-10	Commented functionality	Informational	0.0	Solved07/29/2025
HAL-11	Inconsistent use of uint alias instead of uint256	Informational	0.0	Solved07/29/2025
HAL-12	Floating pragma	Informational	0.0	Solved07/29/2025
HAL-13	Suboptimal modifier ordering	Informational	0.0	Solved07/29/2025
HAL-14	Unused functionality	Informational	0.0	Solved08/05/2025
HAL-15	Use of revert strings instead of custom errors	Informational	0.0	Solved08/05/2025
HAL-16	Unnecessary casting between uint and int increases code complexity and risk of subtle bugs	Informational	0.0	Solved08/05/2025
HAL-17	Missing event	Informational	0.0	Solved08/05/2025
HAL-18	Unused components	Informational	0.0	Solved08/05/2025

Findings & Tech Details#

HAL-01Solved

Incorrect address used during sub vaults asset calculation

High

8.1AO:A/AC:L/AX:L/R:N/S:U/C:N/A:N/I:L/D:H/Y:NAO:A/AC:L/AX:L/R:N/S:U/C:N/A:N/I:L/D:H/Y:N

Description

Proof of Concept

Recommendation

Remediation Comment

Addressed in:

Remediation Comment

Addressed in:

04ba0175aa674202282fa431e4b42d1bb9dac852

HAL-05Solved

Decimals mismatch between parent and subVaults could break accounting

Low

2.0AO:S/AC:L/AX:L/R:N/S:U/C:N/A:N/I:N/D:C/Y:NAO:S/AC:L/AX:L/R:N/S:U/C:N/A:N/I:N/D:C/Y:N

Description

Recommendation

Remediation Comment

Addressed in:

15d7ec1e6e956c5a70f1ad5275977913580c620d

HAL-06Acknowledged

Insufficient input validation

Informational

1.5AO:S/AC:L/AX:L/R:N/S:U/C:N/A:N/I:H/D:N/Y:NAO:S/AC:L/AX:L/R:N/S:U/C:N/A:N/I:H/D:N/Y:N

Description

Recommendation

456581ae14bc3c6ed225a3a63280761540555d0a

8. Automated Testing#

Disclaimer#

Halborn strongly recommends conducting a follow-up assessment of the project either within six months or immediately following any material changes to the codebase, whichever comes first. This approach is crucial for maintaining the project’s integrity and addressing potential vulnerabilities introduced by code modifications.