Cardano Foundation looks forward to working with the security community to find security vulnerabilities in order to keep our businesses and customers safe. From this program, we aim to strengthen the Cardano brand through this public bug bounty program, covering essential items to access and manage crypto assets that are issued on the Cardano blockchain.

About the Cardano Foundation: The Cardano Foundation is an independent Swiss not-for-profit organization that oversees and supervises the advancement of Cardano and its ecosystem. The Foundation's core mission is to further advance Cardano and its ecosystem with a strong focus on sustainability and institutional adoption. As the custodian of the protocol, the Foundation works to enhance the quality and diversity of total on-chain activity, expand its connective infrastructure and tools, increase blockchain utility and resilience as well as shape legislation, and commercial standards. Find out more: www.CardanoFoundation.org

PLEASE NOTE: The scope of this bug bounty program is currently limited to the Cardano Node and Cardano Wallet Backend. For more details please read the Scope section below.

Response Targets

Cardano Foundation will make a best effort to meet the following response targets for hackers participating in our program:

| Type of Response | SLA in business days |

| ------------- | ------------- |

| First Response | 2 days |

| Time to Triage | 2 days |

| Time to Bounty | 14 days |

| Time to Resolution | depends on severity and complexity |

We’ll try to keep you informed about our progress throughout the process.

Disclosure Policy

• As this is a private program, please do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization.

• Follow HackerOne's disclosure guidelines.

Program Rules

• Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue will not be eligible for a reward.

• Submit one vulnerability per-report, unless you need to chain vulnerabilities to provide impact.

• When duplicates occur, we only award the first report that was received (provided that it can be fully reproduced).

• Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.

• Social engineering (e.g. phishing, vishing, smishing) is prohibited.

• Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service. Only interact with accounts you own or with the explicit permission of the account holder.

• All software within the scope of this programme must be run in testnet mode.

• Any type of connection to nodes other than the one run by the Hacker is prohibited.

• Testnet funds can be retrieved from the faucet and should be used sparingly.

Scope

The scope of the bug bounty program will not include any UI or general functionality bugs and is limited to the types of bugs listed below:

• Sensitive information leakage (e.g., private keys wallets, private staking keys, etc), public keys are excluded from this scope

• Transaction tampering (e.g., Changing the recipient address or amount)

• Transaction replay (e.g., double-spend)

• Bugs that cause the service to crash (e.g., Non-network-based DoS)

• Remote code execution vulnerabilities (proof of concept required)

• Attacks that result in harm to the quality of the blockchain or linked/neighbor nodes

• Effective non-network-bandwidth-flooding DDoS attacks (e.g., transaction hammering, etc)

• Wormable vulnerabilities

• If you discover any other areas which may be considered as an exploitable vulnerability or harm the integrity of the blockchain or cryptoasset, please reach out to tom_h1@wearehackerone.com and we will discuss on a case-by-case basis.

Test Plan

Cardano-Node

• https://github.com/input-output-hk/cardano-node

• The latest release of the node is the version that is in scope.

• There are multiple ways to get and run the Cardano Node (e.g. Pre-built binaries, build the node from source code, docker etc.).

• The preferred way is to either build from source or use the pre-built binaries.

• Build instructions can be found here: https://docs.cardano.org/getting-started/installing-the-cardano-node.

• When you build you can also build the command line interface(CLI) and the Submit Api, both of which can be used to interface with the node.

• The latest pre-built binaries for Cardano Node can be found here: https://hydra.iohk.io/jobset/Cardano/cardano-node

• Within the build versions there will be a job called “cardano-deployment”, within that there will be a report that contains the configuration files for connecting to the network, for example https://hydra.iohk.io/build/6782523/download/1/index.html

• The node can be executed as follows:

./cardano-node run --topology ./configFiles/testnet-topology.json --database-path ./state-testnet --port 3001 --config ./configFiles/testnet-config.json --socket-path ./cardano-testnet.socket

• Please alter the paths referenced above to match your folder structure. For windows the socket path should look like this “ \.\pipe\cardano-node”. The node can be run on Linux, Windows & MacOs. Only Linux is supported for Stake Pool activities, i.e. block production.

• The node will open up port 3001 and also a file socket.

• Communications protocols for the sockets are defined in the following document:

https://hydra.iohk.io/build/4314538/download/2/network-spec.pdf

• Details for getting Testnet Ada (tAda) are here:

https://testnets.cardano.org/en/testnets/cardano/tools/faucet/

Cardano-Wallet

• https://github.com/input-output-hk/cardano-wallet

• Cardano-Wallet exposes a REST api that allows wallet based functions like sending a transaction, delegation to a pool, list addresses and transactions etc.

• The API documentation can be found here: https://input-output-hk.github.io/cardano-wallet/api/edge/

• The latest release of Cardano-Wallet is the version that is in scope The node version in scope for testing wallet is the version that is included in the release assets, mentioned in the release notes.

• The preferred way is to either build from source or use the pre-built binaries that are included in the release. The wallet is built with the

• The wallet connects to the Cardano-Node via a file socket.

• The wallet can be executed as follows:

./cardano-wallet serve --node-socket ./cardano-testnet.socket --database ./wallet-db-testnet --listen-address 0.0.0.0 --testnet testnet/testnet-byron-genesis.json --port 8090

• The wallet supports both Byron (Legacy) wallets and addresses and Shelley (HD) wallets and addresses. * Details on wallet and address formats can be found here:

https://input-output-hk.github.io/adrestia/docs/key-concepts/hierarchical-deterministic-wallets/

https://input-output-hk.github.io/adrestia/docs/key-concepts/addresses-byron/

• Details for getting Testnet Ada (tAda) are here:

https://testnets.cardano.org/en/testnets/cardano/tools/faucet/

Known Issues

• All existing vulnerabilities/ bugs that are listed publicly on the Github issues for in scope items, are out of scope. These lists can be found: https://github.com/input-output-hk/cardano-node/issues and https://github.com/input-output-hk/cardano-wallet/issues

Out of scope vulnerabilities

When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug. The following issues are considered out of scope:

• Mainnet use of software is out of scope.

• Clickjacking on pages with no sensitive actions

• Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions

• Attacks requiring MITM or physical access to a user's device.

• Previously known vulnerable libraries without a working Proof of Concept.

• Comma Separated Values (CSV) injection without demonstrating a vulnerability.

• Missing best practices in SSL/TLS configuration.

• Any activity that could lead to the disruption of our service (DoS).

• Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS

• Rate limiting or bruteforce issues on non-authentication endpoints

• Missing best practices in Content Security Policy.

• Missing HttpOnly or Secure flags on cookies

• Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)

• Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]

• Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors).

• Public Zero-day vulnerabilities that have had an official patch for less than 1 month will be awarded on a case by case basis.

• Tabnabbing

• Open redirect - unless an additional security impact can be demonstrated

• Issues that require unlikely user interaction

Safe Harbor

Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you. If legal action is initiated by a third party against you in connection with activities conducted under this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.

Thank you for helping keep Cardano Foundation and our users safe!