Odra - Liquid Staking Audit | Casper Association

Summary

100% of all REPORTED Findings have been addressed

About this report

Assessment Type

Assurance Assessment

Date of Engagement

April 21st, 2025 - April 28th, 2025

Source Code

liquid-staking-contracts

Assessed Commit ID

3deeab6

Severity Breakdown

0Acknowledged
0Risk Accepted
10Solved
10All Findings

Critical0
High0
Medium1
- 1Solved
Low3
- 3Solved
Informational6
- 6Solved

Introduction#

Odra engaged Halborn to conduct a security assessment of the Liquid Staking contract, beginning on April 21st, 2025 and ending on April 28th, 2025. This security assessment was scoped to the smart contracts in the liquid-staking-contracts GitHub repository.

This project implements a Liquid Staking protocol for CSPR on the Casper blockchain. It allows users to stake CSPR and receive a fungible token, sCSPR, which represents their share of the staked assets and can be used freely while earning rewards.

Assessment Summary#

The team at Halborn assigned a full-time security engineer to verify the security of the smart contracts. The security engineer is a blockchain and smart-contract security expert with advanced penetration testing, smart-contract hacking, and deep knowledge of multiple blockchain protocols.

The purpose of this assessment is to:

Ensure that smart contract functions operate as intended.
Identify potential security issues with the smart contracts.

In summary, Halborn identified some improvements to reduce the likelihood and impact of risks, which were successfully addressed by the Odra team. The main ones were the following:

Ensure remove_validator calls collect_fee() before undelegation and updates last_recorded_delegated_amount after.
Expose a secure admin-only ownership transfer function, either via delegation or a custom wrapper.
Enforce a maximum fee_percentage (e.g., 20%) and revert in init() if it exceeds 10,000 basis points (100%).
Restrict withdraw_from_the_contract to only allow withdrawal of CSPR explicitly contributed by the add_to_the_pool function, and enforce automatic or mandatory re-delegation after any undelegation triggered by remove_validator or remove_from_the_pool.

Test Approach and Methodology#

Halborn performed a combination of the manual view of the code and automated security testing to balance efficiency, timeliness, practicality, and accuracy regarding the scope of the smart contract assessment. While manual testing is recommended to uncover flaws in logic, process, and implementation, automated testing techniques help enhance the coverage of smart contracts. They can quickly identify items that do not follow security best practices. The following phases and associated tools were used throughout the term of the assessment:

Research into architecture, purpose, and use of the platform.
Manual code read and walk through.
Manual Assessment of use and safety for the critical Rust variables and functions in scope to identify any arithmetic related vulnerability classes.
Cross contract call controls.
Architecture related logical controls.
Scanning of Rust files for vulnerabilities (cargo audit)
Test analysis using the BDD system deployed with Cucumber tool.

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:liquid-staking-contracts

(b) Assessed Commit ID:3deeab603b20d5b5c46002824ba3aef9f925bfa1

3 files

liquid-staking-contracts / src

3 files

events.rs

rust

lib.rs

rust

token.rs

rust

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

9833dc9bfe88d81ec575e2aa89344efdaec8e015 3be6cc9d3a5a1c47837fa29f29ba61789cf9c36e 4a615bcbb40044b91bd26c49e49a349c46324c3b caded3fc7579e0447bf05c85d9872fd574006005 5f2672a01500d180d46ae53024dda30947ec897d 02f1c0128f78eae3e838a17ddd829b0faf544441 8b15087b085e6d6a685cabe349896ccba00aecab a3c46f83562f287e7d3091e16b5a3cadbe7852ff 69fb922b45ac5cd090877fb947f683e2905b4579 45e00e99b3d35b145593d8965da02c58b3590591

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

Assessment Summary & Findings Overview#

#	Title	Severity	Score	Status
HAL-01	Validator removal bypasses fee collection and breaks delegation tracking	Medium	5.0	Solved05/21/2025
HAL-02	Admin can extract backed CSPR and devalue sCSPR through stake manipulation	Low	2.5	Solved05/14/2025
HAL-03	Contract lacks mechanism to transfer ownership after deployment	Low	2.0	Solved05/07/2025
HAL-04	Lack of validation on fee percentage allows inflation abuse	Low	2.0	Solved05/05/2025
HAL-05	Users can delegate CSPR without receiving sCSPR	Informational	1.6	Solved05/06/2025
HAL-06	Predictable validator selection due to weak randomness	Informational	0.0	Solved05/07/2025
HAL-07	Lack of error handling when adding an already registered validator	Informational	0.0	Solved05/05/2025
HAL-08	Unused constant MIN_STAKE and lack of validation allow unsafe initialization	Informational	0.0	Solved05/05/2025
HAL-09	Unmodifiable claim time prevents governance from adapting unstaking delays in the future	Informational	0.0	Solved05/05/2025
HAL-10	Incorrect sCSPR-to-CSPR conversion when no backing stake or supply exists	Informational	0.0	Solved05/06/2025

45e00e99b3d35b145593d8965da02c58b3590591

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.