{"id":21470529,"url":"https://github.com/manifoldfinance/security","last_synced_at":"2026-02-22T00:38:57.358Z","repository":{"id":103410948,"uuid":"330919831","full_name":"manifoldfinance/security","owner":"manifoldfinance","description":"security policy and reporting","archived":false,"fork":false,"pushed_at":"2023-07-18T03:52:33.000Z","size":27,"stargazers_count":0,"open_issues_count":0,"forks_count":0,"subscribers_count":0,"default_branch":"master","last_synced_at":"2026-01-15T17:03:30.602Z","etag":null,"topics":["bug-bounty","devops","gpg","infosec","pgp","security","vulnerability"],"latest_commit_sha":null,"homepage":"","language":null,"has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":null,"status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/manifoldfinance.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":null,"code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":".github/SECURITY.md","support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2021-01-19T08:57:39.000Z","updated_at":"2023-07-18T09:03:57.000Z","dependencies_parsed_at":null,"dependency_job_id":"cdf3b645-b391-42fa-a95c-bf04e6c4f0fe","html_url":"https://github.com/manifoldfinance/security","commit_stats":null,"previous_names":[],"tags_count":3,"template":false,"template_full_name":null,"purl":"pkg:github/manifoldfinance/security","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/manifoldfinance%2Fsecurity","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/manifoldfinance%2Fsecurity/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/manifoldfinance%2Fsecurity/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/manifoldfinance%2Fsecurity/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/manifoldfinance","download_url":"https://codeload.github.com/manifoldfinance/security/tar.gz/refs/heads/master","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/manifoldfinance%2Fsecurity/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":29701009,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-02-21T23:35:04.139Z","status":"ssl_error","status_checked_at":"2026-02-21T23:35:03.832Z","response_time":107,"last_error":"SSL_connect returned=1 errno=0 peeraddr=140.82.121.5:443 state=error: unexpected eof while reading","robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":false,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["bug-bounty","devops","gpg","infosec","pgp","security","vulnerability"],"created_at":"2024-11-23T09:28:07.136Z","updated_at":"2026-02-22T00:38:57.342Z","avatar_url":"https://github.com/manifoldfinance.png","language":null,"funding_links":[],"categories":[],"sub_categories":[],"readme":"# Vulnerability Disclosure Policy\n\nSecurity is core to our values, and we appreciate the input of security\nresearchers acting in good-faith to help us maintain a high standard for the\nsecurity and privacy of our users, which includes encouraging responsible\nvulnerability research and disclosure. This policy sets out our definition of\ngood-faith in the context of finding and reporting vulnerabilities, as well as\nwhat you can expect from us in return.\n\n## Encrypted Communication Methods\n\nPublic Key Info for `sam@manifoldfinance.com`\nPublic Fingerprint:\n\n```console\nEA82 E243 8E63 F4BD C4AB F453 F773 F8D6 A1A6 D802. \n```\nThis Fingerprint is unique to your public key. Share this so that your contacts can verify that they have the right key to encrypt for.\n\n[Encrypted Contact Page](https://flowcrypt.com/me/sammanifoldfinance)     \n[Public PGP Key](https://flowcrypt.com/pub/sam@manifoldfinance.com)\n\nFlowCrypt also provides an Attestation service, you can access that here: [https://flowcrypt.com/attester/](https://flowcrypt.com/attester/)\n\n### Defects and Reporting Information\n\n[see https://github.com/manifoldfinance/pki#security-bug-handling-process](https://github.com/manifoldfinance/pki#security-bug-handling-process)\n\n\n## Expectations\n\nWhen working with us, according to this policy, you can expect us to:\n\n- Extend Safe Harbor for your vulnerability research that is related to this\n  policy;\n- Work with you to understand and validate your report, including a timely\n  initial response to the submission; and\n- Work to remediate discovered vulnerabilities in a timely manner.\n\n## Official Channels\n\nAny vulnerability deemed to be in-scope, according to this policy, should be\nreported directly to this program through the Encrypted Communciations Methods listed above.\nAll communications between the researcher and program team regarding any reported\nvulnerability should be confined to the comments section of the corresponding\nreport.\n\n## Awards\n\n| Severity | Description                                                             | Examples                                                                                                 |\n| -------- | ----------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------- |\n| Critical | Systemic compromise                                                     | XXE Injection and SQL Injection with significant impact; \u003cbr/\u003eRCE and Vertical Authentication Bypass.    |\n| High     | Full access to other user's private data                                | IDOR, Stored XSS and CSRF with significant impact; \u003cbr/\u003eInternal SSRF and Lateral Authentication Bypass. |\n| Medium   | Limited access to other user's private data                             | IDOR, Reflective XSS and CSRF with impact.                                                               |\n| Low      | Configuration issues and other \u003cbr/\u003evulnerabilities with limited impact | SSL misconfigurations; \u003cbr/\u003eXSS and CSRF with limited impact.                                            |\n\nWe award vulnerability reports at our discretion. In order to be eligible for a\nbounty, your submission must be accepted as in-scope and valid.\n\nThe guidelines we use to determine the validity of reports are outlined below.\n\n### Reproducibility\n\nOur engineers must be able to reproduce the vulnerability you have reported.\nReports that include clearly written explanations and a working proof of concept\nare more likely to be awarded.\n\n### Severity and Priority\n\nGenerally, more impactful bugs will receive higher awards. Review the chart\nabove for examples of award levels for similar vulnerabilities.\n\n### Award Factors\n\nThe amount awarded may vary depending upon the severity of the vulnerability\nreported and quality of the report. If we receive multiple reports of the same\nvulnerability, the first clear, reproducible report will be awarded.\n\nWe may decide to award higher for clever or more impactful vulnerabilities,\ndecide to award lower for vulnerabilities that require unusual user interaction,\ndecide that a single report constitutes multiple bugs or that multiple reports\nare so closely related that they only warrant a single award.\n\n## Disclosure\n\n**Coordinated Disclosure:** Researchers may only share vulnerability details\nwith third parties after the vulnerability has been fixed and the Program has\nprovided permission to disclose OR 90 days after submission, whichever comes\nfirst.\n\nor\n\n**Discretionary Disclosure:** Researchers may only share vulnerability details\nwith third parties after requesting and receiving explicit permission from the\nProgram.\n\n## Guidelines\n\nTo encourage vulnerability research and to avoid any confusion between\nlegitimate research and malicious attack, we ask that you attempt, in good\nfaith, to:\n\n- **Play by the rules.** Adhere to this policy and any other relevant\n  agreements, e.g., Terms of Service;\n- Report any vulnerability you’ve discovered promptly;\n- Avoid violating the privacy of others, disrupting our systems, destroying\n  data, and/or harming user experience;\n- Use only the Official Channels to discuss vulnerability information with us;\n- Handle the confidentiality of details of any discovered vulnerabilities\n  according to our Disclosure Policy;\n- Perform testing only on in-scope systems, and respect systems and activities\n  which are out-of-scope;\n- If a vulnerability provides unintended access to user data, such as Personally\n  Identifiable Information (PII), Personal Healthcare Information (PHI), credit\n  card data, or proprietary information: Cease testing and submit a report\n  immediately;\n- Only interact with accounts you own unless given explicit permission by the\n  account holder;\n- Do not engage in extortion.\n- Be clear and succinct—a short proof-of-concept link is invaluable;\n- Never attempt non-technical attacks—such as social engineering, phishing, or\n  physical attacks—against our employees, users, or infrastructure; and\n- Do not view, alter, save, store, transfer, or otherwise access our data or the\n  data of our users without explicit permission.\n\nWe may modify the terms or terminate this program at any time.\n\n## In-Scope\n\nAny design or implementation issue that substantially affects the\nconfidentiality or integrity of user data is likely to be considered in-scope.\nCommon examples include:\n\n- Cross-site scripting.\n- Cross-site request forgery.\n- Mixed-content scripts.\n- Authentication or authorization flaws.\n- Server-side code execution bugs.\n- Circumvention of our permissions model.\n- SQL injection.\n- XML external entity attacks.\n\nWhile this list is reflective of the research we prioritize, it should not be\nconsidered exhaustive. Any report that concerns the possible compromise of\nsensitive user data or our systems is of interest. By extension, this includes\nthe reporting of serious security weaknesses in any dependency—such as open\nsource libraries, software, or third-party components—actively used in the\ndevelopment of our properties and/or products shared below.\n\n## Out-of-Scope\n\nThe following issues are explicitly outside the scope of this program:\n\n- Policies on presence/absence of SPF/DMARC records.\n- Password, email and account policies, such as email id verification, reset\n  link expiration, and password complexity.\n- Logout cross-site request forgery.\n- Attacks requiring physical access to a user's device.\n- XSS on any site other than those listed as 'in-scope'.\n- Attacks that require an exploitation tool to overlay on top of our app (e.g.,\n  tapjacking).\n- Vulnerabilities that require a potential victim to install non-standard\n  software or otherwise take active steps to make themselves susceptible.\n- Vulnerabilities affecting users of outdated browsers or platforms.\n- Social engineering of our employees or contractors.\n- Any physical attempts against our property or data centers.\n- Presence of autocomplete attribute on web forms.\n- Missing cookie flags on non-sensitive cookies.\n- Any access to data where the targeted user needs to be operating a rooted\n  mobile device.\n\nThe following issues are outside the scope of our program, unless they are\naccompanied by evidence of exploitability:\n\n- Use of a known-vulnerable library.\n- Missing best practices.\n- Insecure SSL/TLS ciphers.\n- Missing security headers, which do not directly lead to a vulnerability.\n- Lack of CSRF tokens, except when there is evidence of a sensitive user-action\n  not protected by a token.\n- Host header injections.\n- Reports from automated tools or scans that haven't been manually validated.\n- Presence of banner or version information, unless a vulnerable version.\n\n## Known Issues\n\nAny issues already known to us will be published as a separate Known Issues\nlist. These vulnerabilities are also considered out-of-scope, though new reports\nof a known issue may be accepted if the instances described were not previously\nobserved.\n\n## Safe Harbor\n\nWhen conducting vulnerability research according to this policy, we consider the\nresearch conducted under this policy to be:\n\n- Authorized in view of any applicable anti-hacking laws, and we will not\n  initiate or support legal action against you for accidental, good faith\n  violations of this policy;\n- Authorized in view of relevant anti-circumvention laws, and we will not bring\n  a claim against you for circumvention of technology controls;\n- Exempt from restrictions in our Acceptable Usage Policy that would interfere\n  with conducting security research, and we waive those restrictions on a limited\n  basis; and\n- Lawful, helpful to the overall security of the Internet, and conducted in good\n  faith.\n\nYou are expected, as always, to comply with all applicable laws. If legal action\nis initiated by a third party against you, and you have complied with this\npolicy, we will take steps to make it known that your actions were conducted in\ncompliance with this policy.\n\nIf at any time you have concerns or are uncertain whether your security research\nis consistent with this policy, please submit a report before going any further.\n\n## The Fine Print\n\nThis is not a competition, but rather an experimental and discretionary program.\n\nYou are solely responsible for any applicable taxes, transaction fees, or other\nwithholdings that arise from or relate to your participation in this program.\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fmanifoldfinance%2Fsecurity","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fmanifoldfinance%2Fsecurity","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fmanifoldfinance%2Fsecurity/lists"}