Public Facing marketing Site for CryptoLife 

Baanx is a global leader in fintech payments and digital assets, specialising in crypto-as-a-service.

More information about Baanx products & services can be obtained from the following websites

baanx.com or withcl.com

Taking down the application/website

Retrieve sensitive data/files from a running server, such as:
- /etc/shadow
- database passwords
- blockchain keys (this does not include non-sensitive environment variables, open source code, or usernames)

Execute arbitrary system commands

Taking and/modifying authenticated actions (with or without blockchain state interaction) on behalf of other users without any interaction by that user, such as:
- Changing registration information
- Commenting
- Voting
- Making trades
- Withdrawals, etc.

Subdomain takeover with already-connected wallet interaction

Malicious interactions with an already-connected wallet, such as:
- Modifying transaction arguments or parameters
- Substituting contract addresses
- Submitting malicious transactions

Direct theft of user funds

Injecting/modifying the static content on the target application without JavaScript (persistent), such as:
- HTML injection without JavaScript
- Replacing existing text with arbitrary text
- Arbitrary file uploads, etc.

Changing sensitive details of other users (including modifying browser local storage) without already-connected wallet interaction and with up to one click of user interaction, such as:
- Email
- Password of the victim etc.

Improperly disclosing confidential user information, such as:
- Email address
- Phone number
- Physical address, etc.

Changing non-sensitive details of other users (including modifying browser local storage) without already-connected wallet interaction and with up to one click of user interaction, such as:
- Changing the first/last name of user
- Enabling/disabling notifications

Subdomain takeover without already-connected wallet interaction

Injecting/modifying the static content on the target application without JavaScript (reflected), such as:
- Reflected HTML Injection
- Loading external site data

Redirecting users to malicious websites (open redirect)

Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield

Permanent freezing of funds

Theft of unclaimed yield

Protocol insolvency

Permanent freezing of unclaimed yield

Temporary freezing of funds

Smart contract unable to operate due to lack of token funds

Theft of gas

Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)

Unbounded gas consumption

Contract fails to deliver promised returns, but doesn't lose value

Theoretical vulnerability where a user could conduct a Card/POS payment and withdraw funds from their wallet during the same on-chain transaction window (1 block). Compensating controls are in place, including back-end processor and database post-chain verification, to mitigate any potential impact

Email verification bypass during signup, allowing creation of accounts with unowned emails. This does not demonstrate taking or modifying authenticated actions on behalf of existing users without their interaction, such as changing registration information post-creation, making trades, withdrawals, or other in-scope impacts. Mitigating procedures are in place including back-end KYC and further verifications, and this is explicitly out of scope per program guidelines.

Known issue related to certain types of small transactions using aUSDC

Infrastructure related to card processing includes many third-party vendors including Visa, Mastercard, processors, and fraud-risk engines which protect the related infrastructure.  

Attacks on those third-party systems are out-of-scope, but any attack that bypasses fraud/risk checks, that are not caught by these fraud/risk systems, would be considered in-scope.

__Reward Calculation for Critical Level Reports__

For critical smart contract bugs, the reward amount is 10% of the funds directly affected up to a maximum of USD $50,000. The calculation of the amount of funds at risk is based on the time and date the bug report is submitted. However, a minimum reward of USD $10,000 is to be rewarded in order to incentivize security researchers against withholding a critical bug report.

For critical web and applications vulnerabilities, reports will be eligible for a reward of up to $50,000.  Many card vulnerabilities are mitigated at daily settlement with merchant, so any and all attacks related to user spending and infrastructure must focus on impact and  must demonstrate:
- loss of funds resulting from an attack that does not require user interaction or consent, collusion with a merchant or using that merchant to generate fraudulant transactions, and must result in unauthorized transfer of funds, misdirection of funds, unbounded spending beyond limits even following daily settlement, or exposure of transactional keys or encryption keys.

- Infrastructure breaches exposing cryptographic secret keys, personally identifiable information (PII) of multiple users beyond the reporter's own record, or scenarios enabling unauthorized spend or loss of funds affecting the platform or a user other than the currently authenticated individual.

- Unauthorized leakage of private keys or private key generation mechanisms, leading to direct access and compromise of user funds.

- Unbounded loss/spend of funds resulting from transactions which bypass  internal controls , merchant controls, and card/processor controls which over-spend users unsettled funds beyond daily acceptable risk threadsholds that are not detected by fraud or risk systems.

All other impacts that would be classified as Critical would be rewarded a flat amount of $5,000. The rest of the severity levels are paid out according to the Impact in Scope table.

__Repeatable Attack Limitations__

- If the smart contract where the vulnerability exists can be upgraded or paused, only the initial attack will be considered for a reward. 
- The amount of funds at risk will be calculated with the impact of the first attack being at 100% and then a reduction of 25% from the amount of the first attack for every [300 blocks] the attack needs for subsequent attacks from the first attack, rounded down.


__Reward Calculation for High Level Reports__

High vulnerabilities concerning theft/permanent freezing of unclaimed yield/royalties - when available on the platform - are rewarded within a range of $5,000 to $10,000 with the reward calculated based on 100% of the funds at risk, though capped at the maximum high reward. 

In the event of temporary freezing, the reward doubles from the full frozen value for every additional 24h that the funds are temporarily frozen, up until a max cap of the high reward.