Solutions

Company

Resources

Blog

Contact

Login

    • Assurance

      Smart Contract Assessment

      Securing code integrity, protecting digital assets

      Blockchain Layer 1 Assessment

      Assessing protocols, securing blockchain foundations

      Code Security Audit

      Uncovering flaws, strengthening software integrity

      Web Application Penetration Testing

      Exposing weaknesses, fortifying digital defenses

      Cloud Infrastructure Penetration Testing

      Securing configurations, protecting critical environments

      Red Team Exercise

      Simulating real-world attacks, strengthening defenses

      AI Red Teaming

      Testing AI systems against real threats

      AI Security Assessment

      Securing AI models, data, and pipelines

    • Advisory

      AI Advisory

      Guiding secure, strategic AI adoption forward

      Risk Assessment

      From unknown threats to actionable insights

      Blockchain Architecture Assessment

      Optimizing architecture for tomorrow’s networks

      Compliance Readiness

      Stay ready as regulations evolve

      Custody and Key Management Assessment

      Securing the heart of digital custody

      Technical Due Diligence

      See the risks before you invest

      Technical Training

      Empower your teams to secure what matters

    • Who We Are

      The best security engineers in the world

      Careers

      Work with the elite

      Who Trusts Us

      The trusted security advisor for blockchain and financial services industries

      Brand

      Access official logos, fonts, and guidelines

      Service Commitments

      Committed to Protecting Your Data

    • Audits

      In-depth evaluations of smart contracts and blockchain infrastructures

      BVSS

      Blockchain Vulnerability Scoring System

      Disclosures

      All the latest vulnerabilities discovered by Halborn

      Case Studies

      How Halborn’s solutions have empowered clients to overcome security issues

      Reports

      Comprehensive reports and data

  • Blog

  • Contact

  • Login

THIS WEBSITE USES COOKIES

We use cookies to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners who may combine it with other information that you've provided to them or that they've collected from your use of their services. You consent to our cookies if you continue to use our website. Learn More.

STAY CURRENT WITH HALBORN

Subscribe to the monthly Halborn Digest for our top blogs and videos, major company announcements, new whitepapers, webinar and event invites, and one exclusive interview.

ADVISORY SERVICES

AI AdvisoryRisk AssessmentBlockchain Architecture AssessmentCompliance ReadinessCustody and Key Management AssessmentTechnical Due DiligenceTechnical Training

ASSURANCE SERVICES

AI Security AssessmentAI Red TeamingSmart Contract AssessmentBlockchain Layer 1 AssessmentCode Security AuditWeb Application Penetration TestingCloud Infrastructure Penetration TestingRed Team Exercise

COMPANY

Who We AreWho Trusts UsService CommitmentsCareersBrandBlogContact

RESOURCES

AuditsDisclosuresReportsBVSSCase Studies
Halborn Logo
Privacy PolicyTerms of UseVulnerability Disclosure Policy

© Halborn 2025. All rights reserved.

Background

// Security Assessment

12.23.2024 - 01.03.2025

Account Abstraction Schnorr MultiSig

InFlux

Halborn logotext
← Back to Audits

Account Abstraction Schnorr MultiSig - InFlux

Prepared by:

Halborn Logo

HALBORN

Last Updated Unknown date

Date of Engagement: December 23rd, 2024 - January 3rd, 2025

Summary

100% of all REPORTED Findings have been addressed

All findings

5

Critical

0

High

0

Medium

0

Low

2

Informational

3

Table of Contents

  • 1. Introduction
  • 2. Assessment summary
  • 3. Test approach and methodology
  • 4. Risk methodology
  • 5. Scope
  • 6. Assessment summary & findings overview
  • 7. Findings & Tech Details
    1. 7.1 Invalid time range can be returned by _intersecttimerange
    2. 7.2 Unbounded error message length in paymaster external calls creates gas unpredictability
    3. 7.3 Missing sanity check for entrypoint
    4. 7.4 Lack of account deployment verification can lead to unexpected revert behavior
    5. 7.5 Overly broad unchecked math blocks in entrypoint contract
  • 8. Automated Testing

1. Introduction

InFlux Technologies engaged Halborn to conduct a security assessment on their smart contracts revisions started on December 23th, 2024 and ending on January 3rd, 2025. The security assessment was scoped to the smart contracts provided to the Halborn team.

Commit hashes and further details can be found in the Scope section of this report.

2. Assessment Summary

The team at Halborn was provided 1 week and 2 days for the engagement and assigned a security engineer to evaluate the security of the smart contract.

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 mostly acknowledged by the InFlux Technologies team. The main ones were the following: 

    • Add some checks for invalid time range.

    • Limit message length return.

    • Add some sanity checks.

3. Test Approach and Methodology

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

    • Research into architecture and purpose.

    • Smart contract manual code review and walkthrough.

    • Graphing out functionality and contract logic/connectivity/functions. (solgraph,draw.io)

    • Manual assessment of use and safety for the critical Solidity variables and functions in scope to identify any arithmetic related vulnerability classes.

    • Manual testing by custom scripts.

    • Static Analysis of security for scoped contract, and imported functions. (Slither)

    • Testnet deployment. (Hardhat,Foundry)

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_eme​)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 EEE is calculated using the following formula:

E=∏meE = \prod m_eE=∏me​

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_ImI​)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 III is calculated using the following formula:

I=max(mI)+∑mI−max(mI)4I = max(m_I) + \frac{\sum{m_I} - max(m_I)}{4}I=max(mI​)+4∑mI​−max(mI​)​

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 (CCC)COEFFICIENT VALUENUMERICAL VALUE
Reversibility (rrr)None (R:N)
Partial (R:P)
Full (R:F)		1
0.5
0.25
Scope (sss)Changed (S:C)
Unchanged (S:U)		1.25
1
Severity Coefficient CCC is obtained by the following product:

C=rsC = rsC=rs

The Vulnerability Severity Score SSS is obtained by:

S=min(10,EIC∗10)S = min(10, EIC * 10)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

REPOSITORY
(a) Repository: account-abstraction
(b) Assessed Commit ID: 588c582
(c) Items in scope:
  • IMultiSigSmartAccount
  • IMultiSigSmartAccountFactory
  • interfaces/INonceManager
  • interfaces/IUserOperation
  • interfaces/IStakeManager
  • interfaces/IAggregator
  • interfaces/IPaymaster
  • interfaces/IEntryPoint
  • interfaces/IAccount
  • utils/Helpers
  • utils/Exec
  • utils/TokenCallbackHandler
  • core/EntryPoint
  • core/BaseAccount
  • core/SenderCreator
  • core/UserOperation
  • core/NonceManager
  • core/StakeManager
  • core/BasePaymaster
  • Schnorr
  • Schnorr
  • MultiSigSmartAccountFactory
  • MultiSigSmartAccount
  • IMultiSigSmartAccount
  • IMultiSigSmartAccountFactory
  • interfaces/INonceManager
↓ Expand ↓
Out-of-Scope: Third Party Dependencies., Economic Attacks.
Out-of-Scope: New features/implementations after the remediation commit IDs.

6. Assessment Summary & Findings Overview

Critical

0

High

0

Medium

0

Low

2

Informational

3

Security analysisRisk levelRemediation Date
Invalid Time Range can be returned by _intersectTimeRangeLowRisk Accepted - 01/07/2025
Unbounded Error Message Length in Paymaster External Calls Creates Gas UnpredictabilityLowNot Applicable
Missing sanity check for entryPointInformationalAcknowledged - 01/07/2025
Lack of Account Deployment Verification can lead to Unexpected Revert BehaviorInformationalAcknowledged - 01/07/2025
Overly Broad Unchecked Math Blocks in EntryPoint ContractInformationalAcknowledged - 01/07/2025

7. Findings & Tech Details

7.1 Invalid Time Range can be returned by _intersectTimeRange

//

Low

Description
Proof of Concept
BVSS
AO:A/AC:L/AX:L/C:N/I:L/A:N/D:N/Y:N/R:N/S:U (2.5)
Recommendation
Remediation Comment
References
RunOnFlux/account-abstraction/contracts/erc4337/utils/Helpers.sol#L38

7.2 Unbounded Error Message Length in Paymaster External Calls Creates Gas Unpredictability

//

Low

Description
BVSS
AO:A/AC:L/AX:L/C:N/I:N/A:L/D:N/Y:N/R:N/S:U (2.5)
Recommendation
Remediation Comment
References
RunOnFlux/account-abstraction/contracts/erc4337/core/EntryPoint.sol#L625
RunOnFlux/account-abstraction/contracts/erc4337/core/EntryPoint.sol#L476

7.3 Missing sanity check for entryPoint

//

Informational

Description
BVSS
AO:A/AC:L/AX:L/C:N/I:N/A:N/D:N/Y:N/R:N/S:U (0.0)
Recommendation
Remediation Comment
References
RunOnFlux/account-abstraction/contracts/erc4337/core/BasePaymaster.sol#L19

7.4 Lack of Account Deployment Verification can lead to Unexpected Revert Behavior

//

Informational

Description
BVSS
AO:A/AC:L/AX:L/C:N/I:N/A:N/D:N/Y:N/R:N/S:C (0.0)
Recommendation
Remediation Comment
References
RunOnFlux/account-abstraction/contracts/erc4337/core/EntryPoint.sol#L426

7.5 Overly Broad Unchecked Math Blocks in EntryPoint Contract

//

Informational

Description
BVSS
AO:A/AC:L/AX:L/C:N/I:N/A:N/D:N/Y:N/R:N/S:C (0.0)
Recommendation
Remediation Comment
References
RunOnFlux/account-abstraction/contracts/erc4337/core/EntryPoint.sol#L426
RunOnFlux/account-abstraction/contracts/erc4337/core/EntryPoint.sol#L476

8. Automated Testing

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.

Table of Contents

  • 1. Introduction
  • 2. Assessment summary
  • 3. Test approach and methodology
  • 4. Risk methodology
  • 5. Scope
  • 6. Assessment summary & findings overview
  • 7. Findings & Tech Details
    1. 7.1 Invalid time range can be returned by _intersecttimerange
    2. 7.2 Unbounded error message length in paymaster external calls creates gas unpredictability
    3. 7.3 Missing sanity check for entrypoint
    4. 7.4 Lack of account deployment verification can lead to unexpected revert behavior
    5. 7.5 Overly broad unchecked math blocks in entrypoint contract
  • 8. Automated Testing

// Download the full report

Account Abstraction Schnorr MultiSig

* Use Google Chrome for best results

** Check "Background Graphics" in the print settings if needed