CosmWasm Contracts - Oroswap


Prepared by:

Halborn Logo

HALBORN

Last Updated 08/26/2025

Date of Engagement: June 30th, 2025 - July 30th, 2025

Summary

100% of all REPORTED Findings have been addressed

All findings

19

Critical

0

High

0

Medium

1

Low

5

Informational

13


1. Introduction

Oroswap engaged Halborn to conduct a security assessment on their smart contracts beginning on June 30th, 2025 and ending on July 30th, 2025. The security assessment was scoped to the smart contracts provided to Halborn. Commit hashes and further details can be found in the Scope section of this report.

2. ASSESMENT SUMMARY


Halborn was provided with 4 weeks for this engagement and assigned 2 security engineers to review the security of the smart contracts in scope. The assigned engineers possess deep expertise in blockchain and smart contract security, including hands-on experience with multiple blockchain protocols.


The objectives of this assessment were to:

    • Identify potential security vulnerabilities within the smart contracts.

    • Ensure that the smart contracts function as intended.


In summary, Halborn identified several areas for improvement to reduce the likelihood and impact of security risks, which were mostly addressed by the Oroswap team. The main ones were:

    • Restrict collect to an authorised role or enforce an internal minimum limit per asset.

    • Cap the number of future schedules per pool or token.

    • Apply length-prefix encoding to each AssetInfo.as_bytes().

    • Store new decimal registrations as pending and require explicit owner approval.

    • Enforce that governance_cut + second_receiver_cut + dev_fund_cut ≤ 100%.

3. TEST APPROACH AND METHODOLOGY


Halborn performed a combination of manual and automated security testing to balance efficiency, timeliness, practicality, and accuracy in regard to the scope of the custom modules. While manual testing is recommended to uncover flaws in logic, process, and implementation; automated testing techniques help enhance coverage of structures and 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 and purpose.

    • Static Analysis of security for scoped repository, and imported functions.

    • Manual Assessment for discovering security vulnerabilities on the codebase.

    • Ensuring the correctness of the codebase.

    • Dynamic Analysis of files and modules in scope.


4. 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 (mem_e)METRIC VALUENUMERICAL VALUE
Attack Origin (AO)Arbitrary (AO:A)
Specific (AO:S)
1
0.2
Attack Cost (AC)Low (AC:L)
Medium (AC:M)
High (AC:H)
1
0.67
0.33
Attack Complexity (AX)Low (AX:L)
Medium (AX:M)
High (AX:H)
1
0.67
0.33
Exploitability EE is calculated using the following formula:

E=meE = \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 (mIm_I)METRIC VALUENUMERICAL VALUE
Confidentiality (C)None (C:N)
Low (C:L)
Medium (C:M)
High (C:H)
Critical (C:C)
0
0.25
0.5
0.75
1
Integrity (I)None (I:N)
Low (I:L)
Medium (I:M)
High (I:H)
Critical (I:C)
0
0.25
0.5
0.75
1
Availability (A)None (A:N)
Low (A:L)
Medium (A:M)
High (A:H)
Critical (A:C)
0
0.25
0.5
0.75
1
Deposit (D)None (D:N)
Low (D:L)
Medium (D:M)
High (D:H)
Critical (D:C)
0
0.25
0.5
0.75
1
Yield (Y)None (Y:N)
Low (Y:L)
Medium (Y:M)
High (Y:H)
Critical (Y:C)
0
0.25
0.5
0.75
1
Impact II is calculated using the following formula:

I=max(mI)+mImax(mI)4I = 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 (CC)COEFFICIENT VALUENUMERICAL VALUE
Reversibility (rr)None (R:N)
Partial (R:P)
Full (R:F)
1
0.5
0.25
Scope (ss)Changed (S:C)
Unchanged (S:U)
1.25
1
Severity Coefficient CC is obtained by the following product:

C=rsC = rs

The Vulnerability Severity Score SS is obtained by:

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

The score is rounded up to 1 decimal places.
SeverityScore Value Range
Critical9 - 10
High7 - 8.9
Medium4.5 - 6.9
Low2 - 4.4
Informational0 - 1.9

5. SCOPE

REPOSITORIES
(a) Repository: oroswap-core
(b) Assessed Commit ID: 59f095b
(c) Items in scope:
  • contracts/periphery/pool_initializer/src/error.rs
  • contracts/periphery/pool_initializer/src/lib.rs
  • contracts/periphery/pool_initializer/src/state.rs
↓ Expand ↓
(a) Repository: oroswap-core
(b) Assessed Commit ID: 9042989
(c) Items in scope:
  • contracts/periphery/tokenfactory_tracker/tests/tube-based-e2e.rs
  • contracts/periphery/tokenfactory_tracker/examples/tokenfactory_tracker_schema.rs
  • contracts/periphery/tokenfactory_tracker/src/error.rs
↓ Expand ↓
Out-of-Scope: Economic attacks and external dependencies.
Remediation Commit ID:
  • f756631
  • 57590dd
  • b427a96
  • c50f110
  • 2cb5a83
  • 308d8c6
  • 2fa02f9
  • 280739c
  • e44c386
  • 345aa61
  • 6be1833
  • c0560b6
  • 34806ab
  • 722b9d2
  • 29e87b6
Out-of-Scope: New features/implementations after the remediation commit IDs.

6. Assessment Summary & Findings Overview

Critical

0

High

0

Medium

1

Low

5

Informational

13

Security analysisRisk levelRemediation Date
Permissionless “Collect” enables fee-harvest griefingMediumSolved - 08/06/2025
Unbounded external-schedule spam could enable gas DoSLowSolved - 08/12/2025
Pair keys can collideLowSolved - 08/11/2025
Initial stake penalises first userLowSolved - 08/15/2025
Burning small xORO amounts can result in no redemptionLowSolved - 08/15/2025
Over-allocation revert distribution due to wrong fees percentagesLowSolved - 08/12/2025
Permissionless decimal spoofingInformationalAcknowledged - 08/17/2025
Missing guard against stale pending operationInformationalSolved - 08/25/2025
Owner can confiscate future reward tokens InformationalSolved - 08/15/2025
Missing balance validation when bypassing amount checkInformationalSolved - 08/15/2025
Schedule-limit bypass via improper length checkInformationalSolved - 08/15/2025
Vesting schedules bypass validation when end_point is missingInformationalSolved - 08/15/2025
Asset info deduplication ignores the font caseInformationalSolved - 08/11/2025
Formula deviation with reference contractsInformationalAcknowledged - 08/17/2025
Missing or incomplete instantiate attributesInformationalSolved - 08/12/2025
Unbounded pagination in query endpointsInformationalSolved - 08/12/2025
Malicious admin can seize all feesInformationalSolved - 08/12/2025
Vesting withdraw from active schedule leaves a single token unit in the scheduleInformationalSolved - 08/15/2025
Redundant branch after minimum fee enforcement in funds splittingInformationalSolved - 08/25/2025

7. Findings & Tech Details

7.1 Permissionless “Collect” enables fee-harvest griefing

//

Medium

Description
BVSS
Recommendation
Remediation Comment
Remediation Hash

7.2 Unbounded external-schedule spam could enable gas DoS

//

Low

Description
BVSS
Recommendation
Remediation Comment
Remediation Hash

7.3 Pair keys can collide

//

Low

Description
Proof of Concept
BVSS
Recommendation
Remediation Comment
Remediation Hash

7.4 Initial stake penalises first user

//

Low

Description
BVSS
Recommendation
Remediation Comment
Remediation Hash

7.5 Burning small xORO amounts can result in no redemption

//

Low

Description
BVSS
Recommendation
Remediation Comment
Remediation Hash

7.6 Over-allocation revert distribution due to wrong fees percentages

//

Low

Description
BVSS
Recommendation
Remediation Comment
Remediation Hash

7.7 Permissionless decimal spoofing

//

Informational

Description
BVSS
Recommendation
Remediation Comment

7.8 Missing guard against stale pending operation

//

Informational

Description
BVSS
Recommendation
Remediation Comment
Remediation Hash

7.9 Owner can confiscate future reward tokens

//

Informational

Description
BVSS
Recommendation
Remediation Comment
Remediation Hash

7.10 Missing balance validation when bypassing amount check

//

Informational

Description
BVSS
Recommendation
Remediation Comment
Remediation Hash

7.11 Schedule-limit bypass via improper length check

//

Informational

Description
BVSS
Recommendation
Remediation Comment
Remediation Hash

7.12 Vesting schedules bypass validation when end_point is missing

//

Informational

Description
BVSS
Recommendation
Remediation Comment
Remediation Hash

7.13 Asset info deduplication ignores the font case

//

Informational

Description
Proof of Concept
BVSS
Recommendation
Remediation Comment
Remediation Hash

7.14 Formula deviation with reference contracts

//

Informational

Description
BVSS
Recommendation
Remediation Comment
References

7.15 Missing or incomplete instantiate attributes

//

Informational

Description
BVSS
Recommendation
Remediation Comment
Remediation Hash

7.16 Unbounded pagination in query endpoints

//

Informational

Description
BVSS
Recommendation
Remediation Comment
Remediation Hash

7.17 Malicious admin can seize all fees

//

Informational

Description
BVSS
Recommendation
Remediation Comment
Remediation Hash

7.18 Vesting withdraw from active schedule leaves a single token unit in the schedule

//

Informational

Description
BVSS
Recommendation
Remediation Comment
Remediation Hash

7.19 Redundant branch after minimum fee enforcement in funds splitting

//

Informational

Description
BVSS
Recommendation
Remediation Comment
Remediation Hash

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.