[{"id":3765353,"new_policy":"Frontegg looks forward to working with the security community to find vulnerabilities in order to keep our businesses and customers safe.\n\nFrontegg is a comprehensive developer platform designed to empower teams with self-service capabilities, robust security features, and enterprise-ready tools through a rich user-management interface, freeing up creativity and differentiation. Unlike traditional user management platforms, integrating Frontegg into your app takes minutes, unlocking a whole new level of end-user experience.\n\nFrontegg's platform provides not only Authentication and SSO via an embeddable or hosted login box, but also a complete Admin Portal serving as the settings area for your users. The Admin Portal allows your users to control every aspect of their accounts: manage users and teams, define and assign roles and permissions, get visibility through audit logs, subscribe to webhooks, and much more. Frontegg’s interfaces are embedded as a UI layer within your app and become a customer-facing management interface for your end users, both on the personal and workspace levels. Frontegg also powers your backend through rich SDKs supported in various languages and frameworks.\n\nScope\nPLEASE MAKE SURE YOU USE ONLY THESE DOMAINS (other domains are not eligible for bounty):\nportal.au.frontegg.com\napi.au.frontegg.com\nImportant: please use an @wearehackerone.com email when signing up.\n\nResponse Targets\nFrontegg will make best efforts to meet the following SLAs for hackers participating in our program:\n\nType of Response\n\nSLA (Business Days)\n\nFirst Response\n\n2 days\n\nTime to Triage\n\n2 days\n\nTime to Bounty\n\n14 days\n\nTime to Resolution\n\nDepends on severity and complexity\n\nWe’ll try to keep you informed about our progress throughout the process.\n\nFocus Areas\nWe are most interested in critical vulnerabilities related to authentication and access:\n\nAccount takeover\n\nCross-tenant manipulation\n\nPrivilege escalation\n\nBypassing security features (e.g., MFA, restrictions, session management)\n\nDisclosure Policy\nFollow HackerOne's disclosure guidelines.\n\nInstructions\n\nSign up to Frontegg Portal and Complete Onboarding:\n\nSign up at https://portal.au.frontegg.com using your @wearehackerone.com email address.\n\nComplete the onboarding process.\n\nYou will receive a unique Frontegg base URL (e.g., https://xxxxxx.au.frontegg.com) and a client ID. Save these for later use.\n\nDownload and Set Up Your Frontegg App:\n\nClone: https://github.com/frontegg/testing-demo-app\n\nRun npm install or yarn install.\n\nOpen the codebase and update index.js with your Frontegg base URL and client ID.\n\nStart the app using npm start or yarn start.\n\nCustomize the App:\n\nGo to the \"Builder\" section at https://portal.au.frontegg.com.\n\nEnable/disable features for testing.\n\nSave and publish your changes.\n\nYou can also adjust settings under Environments -\u003e [Dev/Stg/Prod] -\u003e Authentication/Authorization.\n\nProgram Rules\n\nPlease provide detailed reports with clear, reproducible steps to demonstrate the issue. Incomplete reports are not eligible.\n\nSubmit one vulnerability per report unless chaining is required.\n\nThe first valid report is rewarded in case of duplicates.\n\nMultiple issues from one root cause may receive one bounty.\n\nAvoid privacy violations, data destruction, or service disruption.\n\nTest only within the listed domains.\n\nExclusions\n\nSocial engineering of any kind, including phishing or pretexting against Frontegg employees or users\n\nEmail configuration issues (e.g., SPF, DKIM, DMARC) configuration (SPF, DKIM, DMARC)\n\nVerbose error messages and minor headers issues\n\nClickjacking on non-sensitive pages\n\nBest practices only (e.g., weak TLS, missing HTTP headers)\n\nVulnerabilities requiring MITM or physical access\n\nKnown vulnerable libraries without PoC\n\nMinor UI issues or outdated browser impact only\n\nPublic 0-days with patch \u003c 30 days\n\nOpen redirect unless impactful\n\nExcessive role permissions (known issue)\n\nRatings/Rewards\nInitial vulnerability ratings are based on CVSS. Ratings may be adjusted based on real-world impact and exploitability. If a report is reprioritized, we will provide a clear explanation and allow the researcher to appeal. Adjustments may be made based on likelihood or impact. If a report is downgraded, we will provide an explanation and offer the opportunity to appeal.\n\nRequirements\n\nUse only your @wearehackerone.com email.\n\nAll testing must be done as a Frontegg customer.\n\nDo not access customer data or accounts.\n\nIf you discover a potential data leak, report it but do not exploit it.\n\nSafe Harbor\nActivities conducted within this policy are authorized. If legal action is initiated by a third party, we will confirm your actions were in accordance with this policy.\n\nThank you for helping keep Frontegg and our users safe!\n","has_open_scope":null,"pays_within_one_month":null,"protected_by_gold_standard_safe_harbor":null,"protected_by_ai_safe_harbor":null,"disclosure_declaration":null,"introduction":null,"platform_standards_exclusions":[],"exemplary_standards_exclusions":[],"scope_exclusions":["{\"category\":\"Token refresh\",\"details\":\"By default, JWT token refresh is set to 7 days by default.\\nReports token refresh that are less than 7 days will not be accepted.\"}"],"timestamp":"2025-10-30T12:11:16.242Z"},{"id":3756314,"new_policy":"Frontegg looks forward to working with the security community to find vulnerabilities in order to keep our businesses and customers safe.\n\nFrontegg is a comprehensive developer platform designed to empower teams with self-service capabilities, robust security features, and enterprise-ready tools through a rich user-management interface, freeing up creativity and differentiation. Unlike traditional user management platforms, integrating Frontegg into your app takes minutes, unlocking a whole new level of end-user experience.\n\nFrontegg's platform provides not only Authentication and SSO via an embeddable or hosted login box, but also a complete Admin Portal serving as the settings area for your users. The Admin Portal allows your users to control every aspect of their accounts: manage users and teams, define and assign roles and permissions, get visibility through audit logs, subscribe to webhooks, and much more. Frontegg’s interfaces are embedded as a UI layer within your app and become a customer-facing management interface for your end users, both on the personal and workspace levels. Frontegg also powers your backend through rich SDKs supported in various languages and frameworks.\n\nScope\nPLEASE MAKE SURE YOU USE ONLY THESE DOMAINS (other domains are not eligible for bounty):\nportal.au.frontegg.com\napi.au.frontegg.com\nImportant: please use an @wearehackerone.com email when signing up.\n\nResponse Targets\nFrontegg will make best efforts to meet the following SLAs for hackers participating in our program:\n\nType of Response\n\nSLA (Business Days)\n\nFirst Response\n\n2 days\n\nTime to Triage\n\n2 days\n\nTime to Bounty\n\n14 days\n\nTime to Resolution\n\nDepends on severity and complexity\n\nWe’ll try to keep you informed about our progress throughout the process.\n\nFocus Areas\nWe are most interested in critical vulnerabilities related to authentication and access:\n\nAccount takeover\n\nCross-tenant manipulation\n\nPrivilege escalation\n\nBypassing security features (e.g., MFA, restrictions, session management)\n\nDisclosure Policy\nFollow HackerOne's disclosure guidelines.\n\nInstructions\n\nSign up to Frontegg Portal and Complete Onboarding:\n\nSign up at https://portal.au.frontegg.com using your @wearehackerone.com email address.\n\nComplete the onboarding process.\n\nYou will receive a unique Frontegg base URL (e.g., https://xxxxxx.au.frontegg.com) and a client ID. Save these for later use.\n\nDownload and Set Up Your Frontegg App:\n\nClone: https://github.com/frontegg/testing-demo-app\n\nRun npm install or yarn install.\n\nOpen the codebase and update index.js with your Frontegg base URL and client ID.\n\nStart the app using npm start or yarn start.\n\nCustomize the App:\n\nGo to the \"Builder\" section at https://portal.au.frontegg.com.\n\nEnable/disable features for testing.\n\nSave and publish your changes.\n\nYou can also adjust settings under Environments -\u003e [Dev/Stg/Prod] -\u003e Authentication/Authorization.\n\nProgram Rules\n\nPlease provide detailed reports with clear, reproducible steps to demonstrate the issue. Incomplete reports are not eligible.\n\nSubmit one vulnerability per report unless chaining is required.\n\nThe first valid report is rewarded in case of duplicates.\n\nMultiple issues from one root cause may receive one bounty.\n\nAvoid privacy violations, data destruction, or service disruption.\n\nTest only within the listed domains.\n\nExclusions\n\nSocial engineering of any kind, including phishing or pretexting against Frontegg employees or users\n\nEmail configuration issues (e.g., SPF, DKIM, DMARC) configuration (SPF, DKIM, DMARC)\n\nVerbose error messages and minor headers issues\n\nClickjacking on non-sensitive pages\n\nBest practices only (e.g., weak TLS, missing HTTP headers)\n\nVulnerabilities requiring MITM or physical access\n\nKnown vulnerable libraries without PoC\n\nMinor UI issues or outdated browser impact only\n\nPublic 0-days with patch \u003c 30 days\n\nOpen redirect unless impactful\n\nExcessive role permissions (known issue)\n\nRatings/Rewards\nInitial vulnerability ratings are based on CVSS. Ratings may be adjusted based on real-world impact and exploitability. If a report is reprioritized, we will provide a clear explanation and allow the researcher to appeal. Adjustments may be made based on likelihood or impact. If a report is downgraded, we will provide an explanation and offer the opportunity to appeal.\n\nRequirements\n\nUse only your @wearehackerone.com email.\n\nAll testing must be done as a Frontegg customer.\n\nDo not access customer data or accounts.\n\nIf you discover a potential data leak, report it but do not exploit it.\n\nSafe Harbor\nActivities conducted within this policy are authorized. If legal action is initiated by a third party, we will confirm your actions were in accordance with this policy.\n\nThank you for helping keep Frontegg and our users safe!\n","has_open_scope":null,"pays_within_one_month":null,"protected_by_gold_standard_safe_harbor":null,"protected_by_ai_safe_harbor":null,"disclosure_declaration":null,"introduction":null,"platform_standards_exclusions":[],"exemplary_standards_exclusions":[],"scope_exclusions":[],"timestamp":"2025-05-26T06:50:46.011Z"},{"id":3709403,"new_policy":"Frontegg looks forward to working with the security community to find vulnerabilities in order to keep our businesses and customers safe.\n\nFrontegg is a developer platform that enables self-service, security and enterprise capabilities through a rich user-management interface, freeing up creativity and differentiation. Unlike traditional user management platforms, integrating Frontegg into your app takes minutes, unlocking a whole new level of end-user experience.\n \nFrontegg's platform doesn’t just provide you with Authentication \u0026 SSO via an embeddable or hosted login-box, but a complete Admin Portal serving as the Settings area for your users. The Admin Portal allows your users to control every aspect of their accounts: manage users \u0026 teams, define and assign roles \u0026 permissions, get visibility through audit logs, subscribe to webhooks, and much more. Frontegg’s interfaces are embedded as a UI layer within your app and become a customer-facing management interface for your end-users, both on the personal and workspace levels. Frontegg also powers up your backend through rich SDKs supported in various languages and frameworks.\n\n# Scope\nPLEASE MAKE SURE YOU USE ONLY THESE DOMAINS (other domains are not eligible for bounty):\nportal.au.frontegg.com\napi.au.frontegg.com\n\nImportant - please use @wearehackerone.com email when signing up\n\n# Response Targets\nFrontegg will make a best effort to meet the following SLAs for hackers participating in our program:\n\n| Type of Response | SLA in business days |\n| ------------- | ------------- |\n| First Response | 2 days |\n| Time to Triage | 2 days |\n| Time to Bounty | 14 days |\n| Time to Resolution | depends on severity and complexity |\n\nWe’ll try to keep you informed about our progress throughout the process.\n\nFocus areas\nWe are most interested in critical vulnerabilities related to authentication and access:\n- Account takeover\n- Cross tenants manipulations \n- Privilege escalation\n- Bypass security features (MFA, restrictions, session management)\n\n# Disclosure Policy\n* Follow HackerOne's [disclosure guidelines](https://www.hackerone.com/disclosure-guidelines).\n\n# Instructions\n1. Sign up to Frontegg Portal and Complete Onboarding:\n    * Sign up for an account on https://portal.au.frontegg.com and MAKE SURE YOU USE @wearehackerone.com mail address.\n    * Complete the onboarding process as instructed, providing any required information.\n    * After successful onboarding, you will receive your unique frontegg base url (https://xxxxxx.au.frontegg.com) and client ID. Make note of these details for later use\n2. Download and Setup your Frontegg app:\n    *  Clone the GitHub repository: https://github.com/frontegg/testing-demo-app.\n    *  Install the necessary dependencies for the application by running npm install or yarn install in the project directory.\n    *  Open the codebase in your preferred code editor.\n    *  Look for the index.js file\n    *  Find the placeholders for the frontegg base url and client ID and replace them with the values your received during the onboarding process\n    *   Start the React client by running npm start or yarn start.\n3. Customize the App:\n    *  Navigate to the \"Builder\" section within the Frontegg portal (https://portal.au.frontegg.com).\n    *  In the \"Builder\" section, you will find options to enable or disable various features of the downloaded React client app.\n    *  Modify the feature settings according to your testing requirements, enabling or disabling specific functionalities as needed.\n    *  Save the changes made to the feature settings and styling preferences.\n    * Don't forget to publish the changes from the builder into your working environment (development/production)\n    *  The customized settings will be applied to the React client app that you downloaded\n    * You can also change settings and configurations under the Environments -\u003e [Dev/Stg/Prod] -\u003e Authentication/Authorization pages\n\n# Program Rules\nPlease 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.\n* Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.\n* When duplicates occur, we only award the first report that was received (provided that it can be fully reproduced).\n* Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.\n* 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.\n\nAny domain/property of Frontegg not listed in this list is out of scope. \n\n#Exclusions\n* Social engineering of any kind against Frontegg employees or their users\n* Email configuration ie. SPF, DKIM, DMARC.\n* Error pages ie. verbose error messages, stack traces, invalid status codes.\n* Clickjacking ie. missing X-Frame-Options header.\n* Absent or misconfigured HTTP headers ie. Content-Security-Policy, Strict-Transport-Security, X-XSS-Protection, Cache-Control.\n* Configuration that is not directly exploitable ie. weak TLS ciphers, password policy, session expiration, certificate pinning.\n\n#Ratings/Rewards:\nFor the initial prioritization/rating of findings, this program will use CVSS. However, it is important to note that in some cases a vulnerability priority will be modified due to its likelihood or impact. In any instance where an issue is downgraded, a full, detailed explanation will be provided to the researcher - along with the opportunity to appeal, and make a case for a higher priority._\n\n\n# Out of scope vulnerabilities\n\n### When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug. The following issues are considered out of scope:\n\n\n* Denial of Service \u0026 Rate Limiting\n* Please do NOT use automated tooling when conducting testing on Frontegg assets.\n* Clickjacking on pages with no sensitive actions\n* Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions\n* Attacks requiring MITM or physical access to a user's device.\n* Previously known vulnerable libraries without a working Proof of Concept.\n* Comma Separated Values (CSV) injection without demonstrating a vulnerability.\n* Missing best practices in SSL/TLS configuration.\n* Any activity that could lead to the disruption of our service (DoS).\n* Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS\n* Rate limiting or bruteforce issues on non-authentication endpoints\n* Missing best practices in Content Security Policy.\n* Missing HttpOnly or Secure flags on cookies\n* Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)\n* Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]\n* Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors).\n* Public Zero-day vulnerabilities that have had an official patch for less than 1 month will be awarded on a case by case basis.\n* Tabnabbing\n* Open redirect - unless an additional security impact can be demonstrated\n* Issues that require unlikely user interaction\n* Frontegg is currently aware of permissions issues with different roles, therefore reports including roles' excessive permission will not be rewarded. Frontegg is currently working on solving these issues.\n\n# A Few Important Requirements for Frontegg:\n* All testing must be conducted using your @wearehackerone.com email ID only. If you fail to use your @wearehackerone.com email ID, you run the risk of getting blocked from accessing Frontegg applications.\n* All tests must be performed as a Frontegg customer. You can create an account using your @wearehackerone.com email ID. External scanning finding will not be counted as a valid finding\n* Frontegg’s customer instances are not to be accessed in any way (i.e. no customer data is accessed, customer credentials are not to be used or \"verified\")\n* If you believe you have found sensitive customer data (e.g., login credentials, API keys etc) or a way to access customer data (i.e. through a vulnerability) report it, but do not attempt to successfully validate if/that it works.\n\n# Safe Harbor\nAny 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.\n\nThank you for helping keep Frontegg and our users safe!\n\n\n \n\n\n\n\n\n\n \n \n \n\n \n \n\n \n\n","has_open_scope":null,"pays_within_one_month":null,"protected_by_gold_standard_safe_harbor":null,"protected_by_ai_safe_harbor":null,"disclosure_declaration":null,"introduction":null,"platform_standards_exclusions":[],"exemplary_standards_exclusions":[],"scope_exclusions":[],"timestamp":"2023-12-18T06:41:06.073Z"},{"id":3706287,"new_policy":"Frontegg looks forward to working with the security community to find vulnerabilities in order to keep our businesses and customers safe.\n\nFrontegg is a developer platform that enables self-service, security and enterprise capabilities through a rich user-management interface, freeing up creativity and differentiation. Unlike traditional user management platforms, integrating Frontegg into your app takes minutes, unlocking a whole new level of end-user experience.\n \nFrontegg's platform doesn’t just provide you with Authentication \u0026 SSO via an embeddable or hosted login-box, but a complete Admin Portal serving as the Settings area for your users. The Admin Portal allows your users to control every aspect of their accounts: manage users \u0026 teams, define and assign roles \u0026 permissions, get visibility through audit logs, subscribe to webhooks, and much more. Frontegg’s interfaces are embedded as a UI layer within your app and become a customer-facing management interface for your end-users, both on the personal and workspace levels. Frontegg also powers up your backend through rich SDKs supported in various languages and frameworks.\n\n# Scope\nPLEASE MAKE SURE YOU USE ONLY THESE DOMAINS (other domains are not eligible for bounty):\nportal.au.frontegg.com\napi.au.frontegg.com\n\nImportant - please use @wearehackerone.com email when signing up\n\n# Response Targets\nFrontegg will make a best effort to meet the following SLAs for hackers participating in our program:\n\n| Type of Response | SLA in business days |\n| ------------- | ------------- |\n| First Response | 2 days |\n| Time to Triage | 2 days |\n| Time to Bounty | 14 days |\n| Time to Resolution | depends on severity and complexity |\n\nWe’ll try to keep you informed about our progress throughout the process.\n\nFocus areas\nWe are most interested in critical vulnerabilities related to authentication and access:\n- Account takeover\n- Cross tenants manipulations \n- Privilege escalation\n- Bypass security features (MFA, restrictions, session management)\n\n# Disclosure Policy\n* Follow HackerOne's [disclosure guidelines](https://www.hackerone.com/disclosure-guidelines).\n\n# Instructions\n1. Sign up to Frontegg Portal and Complete Onboarding:\n    * Sign up for an account on https://portal.au.frontegg.com and MAKE SURE YOU USE @wearehackerone.com mail address.\n    * Complete the onboarding process as instructed, providing any required information.\n    * After successful onboarding, you will receive your unique frontegg base url (https://xxxxxx.au.frontegg.com) and client ID. Make note of these details for later use\n2. Download and Setup your Frontegg app:\n    *  Clone the GitHub repository: https://github.com/frontegg/testing-demo-app.\n    *  Install the necessary dependencies for the application by running npm install or yarn install in the project directory.\n    *  Open the codebase in your preferred code editor.\n    *  Look for the index.js file\n    *  Find the placeholders for the frontegg base url and client ID and replace them with the values your received during the onboarding process\n    *   Start the React client by running npm start or yarn start.\n3. Customize the App:\n    *  Navigate to the \"Builder\" section within the Frontegg portal (https://portal.au.frontegg.com).\n    *  In the \"Builder\" section, you will find options to enable or disable various features of the downloaded React client app.\n    *  Modify the feature settings according to your testing requirements, enabling or disabling specific functionalities as needed.\n    *  Save the changes made to the feature settings and styling preferences.\n    * Don't forget to publish the changes from the builder into your working environment (development/production)\n    *  The customized settings will be applied to the React client app that you downloaded\n    * You can also change settings and configurations under the Environments -\u003e [Dev/Stg/Prod] -\u003e Authentication/Authorization pages\n\n# Program Rules\nPlease 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.\n* Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.\n* When duplicates occur, we only award the first report that was received (provided that it can be fully reproduced).\n* Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.\n* 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.\n\nAny domain/property of Frontegg not listed in this list is out of scope. \n\n#Exclusions\n* Social engineering of any kind against Frontegg employees or their users\n* Email configuration ie. SPF, DKIM, DMARC.\n* Error pages ie. verbose error messages, stack traces, invalid status codes.\n* Clickjacking ie. missing X-Frame-Options header.\n* Absent or misconfigured HTTP headers ie. Content-Security-Policy, Strict-Transport-Security, X-XSS-Protection, Cache-Control.\n* Configuration that is not directly exploitable ie. weak TLS ciphers, password policy, session expiration, certificate pinning.\n\n#Ratings/Rewards:\nFor the initial prioritization/rating of findings, this program will use CVSS. However, it is important to note that in some cases a vulnerability priority will be modified due to its likelihood or impact. In any instance where an issue is downgraded, a full, detailed explanation will be provided to the researcher - along with the opportunity to appeal, and make a case for a higher priority._\n\n\n# Out of scope vulnerabilities\n\n### When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug. The following issues are considered out of scope:\n\n\n* Denial of Service \u0026 Rate Limiting\n* Please do NOT use automated tooling when conducting testing on Frontegg assets.\n* Clickjacking on pages with no sensitive actions\n* Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions\n* Attacks requiring MITM or physical access to a user's device.\n* Previously known vulnerable libraries without a working Proof of Concept.\n* Comma Separated Values (CSV) injection without demonstrating a vulnerability.\n* Missing best practices in SSL/TLS configuration.\n* Any activity that could lead to the disruption of our service (DoS).\n* Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS\n* Rate limiting or bruteforce issues on non-authentication endpoints\n* Missing best practices in Content Security Policy.\n* Missing HttpOnly or Secure flags on cookies\n* Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)\n* Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]\n* Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors).\n* Public Zero-day vulnerabilities that have had an official patch for less than 1 month will be awarded on a case by case basis.\n* Tabnabbing\n* Open redirect - unless an additional security impact can be demonstrated\n* Issues that require unlikely user interaction\n\n# A Few Important Requirements for Frontegg:\n* All testing must be conducted using your @wearehackerone.com email ID only. If you fail to use your @wearehackerone.com email ID, you run the risk of getting blocked from accessing Frontegg applications.\n* All tests must be performed as a Frontegg customer. You can create an account using your @wearehackerone.com email ID. External scanning finding will not be counted as a valid finding\n* Frontegg’s customer instances are not to be accessed in any way (i.e. no customer data is accessed, customer credentials are not to be used or \"verified\")\n* If you believe you have found sensitive customer data (e.g., login credentials, API keys etc) or a way to access customer data (i.e. through a vulnerability) report it, but do not attempt to successfully validate if/that it works.\n\n# Safe Harbor\nAny 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.\n\nThank you for helping keep Frontegg and our users safe!\n\n\n \n\n\n\n\n\n\n \n \n \n\n \n \n\n \n\n","has_open_scope":null,"pays_within_one_month":null,"protected_by_gold_standard_safe_harbor":null,"protected_by_ai_safe_harbor":null,"disclosure_declaration":null,"introduction":null,"platform_standards_exclusions":[],"exemplary_standards_exclusions":[],"scope_exclusions":[],"timestamp":"2023-11-01T11:28:30.736Z"},{"id":3706286,"new_policy":"Frontegg looks forward to working with the security community to find vulnerabilities in order to keep our businesses and customers safe.\n\nFrontegg is a developer platform that enables self-service, security and enterprise capabilities through a rich user-management interface, freeing up creativity and differentiation. Unlike traditional user management platforms, integrating Frontegg into your app takes minutes, unlocking a whole new level of end-user experience.\n \nFrontegg's platform doesn’t just provide you with Authentication \u0026 SSO via an embeddable or hosted login-box, but a complete Admin Portal serving as the Settings area for your users. The Admin Portal allows your users to control every aspect of their accounts: manage users \u0026 teams, define and assign roles \u0026 permissions, get visibility through audit logs, subscribe to webhooks, and much more. Frontegg’s interfaces are embedded as a UI layer within your app and become a customer-facing management interface for your end-users, both on the personal and workspace levels. Frontegg also powers up your backend through rich SDKs supported in various languages and frameworks.\n\n# Scope\nPLEASE MAKE SURE YOU USE ONLY THESE DOMAINS (other domains are not eligible for bounty):\nportal.au.frontegg.com\napi.au.frontegg.com\n\n# Response Targets\nFrontegg will make a best effort to meet the following SLAs for hackers participating in our program:\n\n| Type of Response | SLA in business days |\n| ------------- | ------------- |\n| First Response | 2 days |\n| Time to Triage | 2 days |\n| Time to Bounty | 14 days |\n| Time to Resolution | depends on severity and complexity |\n\nWe’ll try to keep you informed about our progress throughout the process.\n\nFocus areas\nWe are most interested in critical vulnerabilities related to authentication and access:\n- Account takeover\n- Cross tenants manipulations \n- Privilege escalation\n- Bypass security features (MFA, restrictions, session management)\n\n# Disclosure Policy\n* Follow HackerOne's [disclosure guidelines](https://www.hackerone.com/disclosure-guidelines).\n\n# Instructions\n1. Sign up to Frontegg Portal and Complete Onboarding:\n    * Sign up for an account on https://portal.au.frontegg.com.\n    * Complete the onboarding process as instructed, providing any required information.\n    * After successful onboarding, you will receive your unique frontegg base url (https://xxxxxx.au.frontegg.com) and client ID. Make note of these details for later use\n2. Download and Setup your Frontegg app:\n    *  Clone the GitHub repository: https://github.com/frontegg/testing-demo-app.\n    *  Install the necessary dependencies for the application by running npm install or yarn install in the project directory.\n    *  Open the codebase in your preferred code editor.\n    *  Look for the index.js file\n    *  Find the placeholders for the frontegg base url and client ID and replace them with the values your received during the onboarding process\n    *   Start the React client by running npm start or yarn start.\n3. Customize the App:\n    *  Navigate to the \"Builder\" section within the Frontegg portal (https://portal.au.frontegg.com).\n    *  In the \"Builder\" section, you will find options to enable or disable various features of the downloaded React client app.\n    *  Modify the feature settings according to your testing requirements, enabling or disabling specific functionalities as needed.\n    *  Save the changes made to the feature settings and styling preferences.\n    * Don't forget to publish the changes from the builder into your working environment (development/production)\n    *  The customized settings will be applied to the React client app that you downloaded\n    * You can also change settings and configurations under the Environments -\u003e [Dev/Stg/Prod] -\u003e Authentication/Authorization pages\n\n# Program Rules\nPlease 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.\n* Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.\n* When duplicates occur, we only award the first report that was received (provided that it can be fully reproduced).\n* Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.\n* 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.\n\nAny domain/property of Frontegg not listed in this list is out of scope. \n\n#Exclusions\n* Social engineering of any kind against Frontegg employees or their users\n* Email configuration ie. SPF, DKIM, DMARC.\n* Error pages ie. verbose error messages, stack traces, invalid status codes.\n* Clickjacking ie. missing X-Frame-Options header.\n* Absent or misconfigured HTTP headers ie. Content-Security-Policy, Strict-Transport-Security, X-XSS-Protection, Cache-Control.\n* Configuration that is not directly exploitable ie. weak TLS ciphers, password policy, session expiration, certificate pinning.\n\n#Ratings/Rewards:\nFor the initial prioritization/rating of findings, this program will use CVSS. However, it is important to note that in some cases a vulnerability priority will be modified due to its likelihood or impact. In any instance where an issue is downgraded, a full, detailed explanation will be provided to the researcher - along with the opportunity to appeal, and make a case for a higher priority._\n\n\n# Out of scope vulnerabilities\n\n### When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug. The following issues are considered out of scope:\n\n\n* Denial of Service \u0026 Rate Limiting\n* Please do NOT use automated tooling when conducting testing on Frontegg assets.\n* Clickjacking on pages with no sensitive actions\n* Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions\n* Attacks requiring MITM or physical access to a user's device.\n* Previously known vulnerable libraries without a working Proof of Concept.\n* Comma Separated Values (CSV) injection without demonstrating a vulnerability.\n* Missing best practices in SSL/TLS configuration.\n* Any activity that could lead to the disruption of our service (DoS).\n* Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS\n* Rate limiting or bruteforce issues on non-authentication endpoints\n* Missing best practices in Content Security Policy.\n* Missing HttpOnly or Secure flags on cookies\n* Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)\n* Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]\n* Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors).\n* Public Zero-day vulnerabilities that have had an official patch for less than 1 month will be awarded on a case by case basis.\n* Tabnabbing\n* Open redirect - unless an additional security impact can be demonstrated\n* Issues that require unlikely user interaction\n\n# A Few Important Requirements for Frontegg:\n* All testing must be conducted using your @wearehackerone.com email ID only. If you fail to use your @wearehackerone.com email ID, you run the risk of getting blocked from accessing Frontegg applications.\n* All tests must be performed as a Frontegg customer. You can create an account using your @wearehackerone.com email ID. External scanning finding will not be counted as a valid finding\n* Frontegg’s customer instances are not to be accessed in any way (i.e. no customer data is accessed, customer credentials are not to be used or \"verified\")\n* If you believe you have found sensitive customer data (e.g., login credentials, API keys etc) or a way to access customer data (i.e. through a vulnerability) report it, but do not attempt to successfully validate if/that it works.\n\n# Safe Harbor\nAny 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.\n\nThank you for helping keep Frontegg and our users safe!\n\n\n \n\n\n\n\n\n\n \n \n \n\n \n \n\n \n\n","has_open_scope":null,"pays_within_one_month":null,"protected_by_gold_standard_safe_harbor":null,"protected_by_ai_safe_harbor":null,"disclosure_declaration":null,"introduction":null,"platform_standards_exclusions":[],"exemplary_standards_exclusions":[],"scope_exclusions":[],"timestamp":"2023-11-01T11:21:51.701Z"},{"id":3706274,"new_policy":"Frontegg looks forward to working with the security community to find vulnerabilities in order to keep our businesses and customers safe.\n\nFrontegg is a developer platform that enables self-service, security and enterprise-capabilities through a rich user-management interface, freeing up creativity and differentiation. Unlike traditional user management platforms, integrating Frontegg into your app takes minutes, unlocking a whole new level of end-user experience.\n \nFrontegg's platform doesn’t just provide you with Authentication \u0026 SSO via an embeddable or hosted login-box, but a full Admin Portal serving as the Settings area for your users. The Admin Portal allows your users to control every aspect of their accounts: manage users \u0026 teams, define and assign roles \u0026 permissions, get visibility through audit logs, subscribe to webhooks and much more. Frontegg’s interfaces are embedded as a UI layer within your app and becomes a customer-facing management interface for your end-users, both on the personal and workspace levels. Frontegg also powers-up your backend through rich SDKs supported in various languages and frameworks.\n# Response Targets\nFrontegg will make a best effort to meet the following SLAs for hackers participating in our program:\n\n| Type of Response | SLA in business days |\n| ------------- | ------------- |\n| First Response | 2 days |\n| Time to Triage | 2 days |\n| Time to Bounty | 14 days |\n| Time to Resolution | depends on severity and complexity |\n\nWe’ll try to keep you informed about our progress throughout the process.\n\nFocus areas\nWe are most interested in critical vulnerabilities related to authentication and access:\n- Account takeover\n- Cross tenants manipulations \n- Privilege escalation\n- Bypass security features (MFA, restrictions, session management)\n\n# Disclosure Policy\n* Follow HackerOne's [disclosure guidelines](https://www.hackerone.com/disclosure-guidelines).\n\n# Instructions\n1. Sign up to Frontegg Portal and Complete Onboarding:\n    * Sign up for an account on https://portal.au.frontegg.com.\n    * Complete the onboarding process as instructed, providing any required information.\n    * After successful onboarding, you will receive your unique frontegg base url (https://xxxxxx.au.frontegg.com) and client ID. Make note of these details for later use\n2. Download and Setup your Frontegg app:\n    *  Clone the GitHub repository: https://github.com/frontegg/testing-demo-app.\n    *  Install the necessary dependencies for the application by running npm install or yarn install in the project directory.\n    *  Open the codebase in your preferred code editor.\n    *  Look for the index.js file\n    *  Find the placeholders for the frontegg base url and client ID and replace them with the values your received during the onboarding process\n    *   Start the React client by running npm start or yarn start.\n3. Customize the App:\n    *  Navigate to the \"Builder\" section within the Frontegg portal (https://portal.au.frontegg.com).\n    *  In the \"Builder\" section, you will find options to enable or disable various features of the downloaded React client app.\n    *  Modify the feature settings according to your testing requirements, enabling or disabling specific functionalities as needed.\n    *  Save the changes made to the feature settings and styling preferences.\n    * Don't forget to publish the changes from the builder into your working environment (development/production)\n    *  The customized settings will be applied to the React client app that you downloaded\n    * You can also change settings and configurations under the Environments -\u003e [Dev/Stg/Prod] -\u003e Authentication/Authorization pages\n\n# Program Rules\nPlease 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.\n* Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.\n* When duplicates occur, we only award the first report that was received (provided that it can be fully reproduced).\n* Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.\n* 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.\n\nOnly these domains are in the scope of the program: \nportal.au.frontegg.com\napi.au.frontegg.com\n\nAny domain/property of Frontegg not listed in this list is out of scope. \n\n#Exclusions\n* Social engineering of any kind against Frontegg employees or their users\n* Email configuration ie. SPF, DKIM, DMARC.\n* Error pages ie. verbose error messages, stack traces, invalid status codes.\n* Clickjacking ie. missing X-Frame-Options header.\n* Absent or misconfigured HTTP headers ie. Content-Security-Policy, Strict-Transport-Security, X-XSS-Protection, Cache-Control.\n* Configuration that is not directly exploitable ie. weak TLS ciphers, password policy, session expiration, certificate pinning.\n\n#Ratings/Rewards:\nFor the initial prioritization/rating of findings, this program will use CVSS. However, it is important to note that in some cases a vulnerability priority will be modified due to its likelihood or impact. In any instance where an issue is downgraded, a full, detailed explanation will be provided to the researcher - along with the opportunity to appeal, and make a case for a higher priority._\n\n\n# Out of scope vulnerabilities\n\n### When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug. The following issues are considered out of scope:\n\n\n* Denial of Service \u0026 Rate Limiting\n* Please do NOT use automated tooling when conducting testing on Frontegg assets.\n* Clickjacking on pages with no sensitive actions\n* Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions\n* Attacks requiring MITM or physical access to a user's device.\n* Previously known vulnerable libraries without a working Proof of Concept.\n* Comma Separated Values (CSV) injection without demonstrating a vulnerability.\n* Missing best practices in SSL/TLS configuration.\n* Any activity that could lead to the disruption of our service (DoS).\n* Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS\n* Rate limiting or bruteforce issues on non-authentication endpoints\n* Missing best practices in Content Security Policy.\n* Missing HttpOnly or Secure flags on cookies\n* Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)\n* Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]\n* Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors).\n* Public Zero-day vulnerabilities that have had an official patch for less than 1 month will be awarded on a case by case basis.\n* Tabnabbing\n* Open redirect - unless an additional security impact can be demonstrated\n* Issues that require unlikely user interaction\n\n# A Few Important Requirements for Frontegg:\n* All testing must be conducted using your @wearehackerone.com email ID only. If you fail to use your @wearehackerone.com email ID, you run the risk of getting blocked from accessing Frontegg applications.\n* All tests must be performed as a Frontegg customer. You can create an account using your @wearehackerone.com email ID. External scanning finding will not be counted as a valid finding\n* Frontegg’s customer instances are not to be accessed in any way (i.e. no customer data is accessed, customer credentials are not to be used or \"verified\")\n* If you believe you have found sensitive customer data (e.g., login credentials, API keys etc) or a way to access customer data (i.e. through a vulnerability) report it, but do not attempt to successfully validate if/that it works.\n\n# Safe Harbor\nAny 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.\n\nThank you for helping keep Frontegg and our users safe!\n\n\n \n\n\n\n\n\n\n \n \n \n\n \n \n\n \n\n","has_open_scope":null,"pays_within_one_month":null,"protected_by_gold_standard_safe_harbor":null,"protected_by_ai_safe_harbor":null,"disclosure_declaration":null,"introduction":null,"platform_standards_exclusions":[],"exemplary_standards_exclusions":[],"scope_exclusions":[],"timestamp":"2023-11-01T09:35:20.414Z"},{"id":3706273,"new_policy":"Frontegg looks forward to working with the security community to find vulnerabilities in order to keep our businesses and customers safe.\n\nFrontegg is a developer platform that enables self-service, security and enterprise-capabilities through a rich user-management interface, freeing up creativity and differentiation. Unlike traditional user management platforms, integrating Frontegg into your app takes minutes, unlocking a whole new level of end-user experience.\n \nFrontegg's platform doesn’t just provide you with Authentication \u0026 SSO via an embeddable or hosted login-box, but a full Admin Portal serving as the Settings area for your users. The Admin Portal allows your users to control every aspect of their accounts: manage users \u0026 teams, define and assign roles \u0026 permissions, get visibility through audit logs, subscribe to webhooks and much more. Frontegg’s interfaces are embedded as a UI layer within your app and becomes a customer-facing management interface for your end-users, both on the personal and workspace levels. Frontegg also powers-up your backend through rich SDKs supported in various languages and frameworks.\n# Response Targets\nFrontegg will make a best effort to meet the following SLAs for hackers participating in our program:\n\n| Type of Response | SLA in business days |\n| ------------- | ------------- |\n| First Response | 2 days |\n| Time to Triage | 2 days |\n| Time to Bounty | 14 days |\n| Time to Resolution | depends on severity and complexity |\n\nWe’ll try to keep you informed about our progress throughout the process.\n\nFocus areas\nWe are most interested in critical vulnerabilities related to authentication and access:\n- Account takeover\n- Cross tenants manipulations \n- Privilege escalation\n- Bypass security features (MFA, restrictions, session management)\n\n# Disclosure Policy\n* 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.\n* Follow HackerOne's [disclosure guidelines](https://www.hackerone.com/disclosure-guidelines).\n\n# Instructions\n1. Sign up to Frontegg Portal and Complete Onboarding:\n    * Sign up for an account on https://portal.au.frontegg.com.\n    * Complete the onboarding process as instructed, providing any required information.\n    * After successful onboarding, you will receive your unique frontegg base url (https://xxxxxx.au.frontegg.com) and client ID. Make note of these details for later use\n2. Download and Setup your Frontegg app:\n    *  Clone the GitHub repository: https://github.com/frontegg/testing-demo-app.\n    *  Install the necessary dependencies for the application by running npm install or yarn install in the project directory.\n    *  Open the codebase in your preferred code editor.\n    *  Look for the index.js file\n    *  Find the placeholders for the frontegg base url and client ID and replace them with the values your received during the onboarding process\n    *   Start the React client by running npm start or yarn start.\n3. Customize the App:\n    *  Navigate to the \"Builder\" section within the Frontegg portal (https://portal.au.frontegg.com).\n    *  In the \"Builder\" section, you will find options to enable or disable various features of the downloaded React client app.\n    *  Modify the feature settings according to your testing requirements, enabling or disabling specific functionalities as needed.\n    *  Save the changes made to the feature settings and styling preferences.\n    * Don't forget to publish the changes from the builder into your working environment (development/production)\n    *  The customized settings will be applied to the React client app that you downloaded\n    * You can also change settings and configurations under the Environments -\u003e [Dev/Stg/Prod] -\u003e Authentication/Authorization pages\n\n# Program Rules\nPlease 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.\n* Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.\n* When duplicates occur, we only award the first report that was received (provided that it can be fully reproduced).\n* Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.\n* 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.\n\nOnly these domains are in the scope of the program: \nportal.au.frontegg.com\napi.au.frontegg.com\n\nAny domain/property of Frontegg not listed in this list is out of scope. \n\n#Exclusions\n* Social engineering of any kind against Frontegg employees or their users\n* Email configuration ie. SPF, DKIM, DMARC.\n* Error pages ie. verbose error messages, stack traces, invalid status codes.\n* Clickjacking ie. missing X-Frame-Options header.\n* Absent or misconfigured HTTP headers ie. Content-Security-Policy, Strict-Transport-Security, X-XSS-Protection, Cache-Control.\n* Configuration that is not directly exploitable ie. weak TLS ciphers, password policy, session expiration, certificate pinning.\n\n#Ratings/Rewards:\nFor the initial prioritization/rating of findings, this program will use CVSS. However, it is important to note that in some cases a vulnerability priority will be modified due to its likelihood or impact. In any instance where an issue is downgraded, a full, detailed explanation will be provided to the researcher - along with the opportunity to appeal, and make a case for a higher priority._\n\n\n# Out of scope vulnerabilities\n\n### When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug. The following issues are considered out of scope:\n\n\n* Denial of Service \u0026 Rate Limiting\n* Please do NOT use automated tooling when conducting testing on Frontegg assets.\n* Clickjacking on pages with no sensitive actions\n* Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions\n* Attacks requiring MITM or physical access to a user's device.\n* Previously known vulnerable libraries without a working Proof of Concept.\n* Comma Separated Values (CSV) injection without demonstrating a vulnerability.\n* Missing best practices in SSL/TLS configuration.\n* Any activity that could lead to the disruption of our service (DoS).\n* Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS\n* Rate limiting or bruteforce issues on non-authentication endpoints\n* Missing best practices in Content Security Policy.\n* Missing HttpOnly or Secure flags on cookies\n* Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)\n* Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]\n* Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors).\n* Public Zero-day vulnerabilities that have had an official patch for less than 1 month will be awarded on a case by case basis.\n* Tabnabbing\n* Open redirect - unless an additional security impact can be demonstrated\n* Issues that require unlikely user interaction\n\n# A Few Important Requirements for Frontegg:\n* All testing must be conducted using your @wearehackerone.com email ID only. If you fail to use your @wearehackerone.com email ID, you run the risk of getting blocked from accessing Frontegg applications.\n* All tests must be performed as a Frontegg customer. You can create an account using your @wearehackerone.com email ID. External scanning finding will not be counted as a valid finding\n* Frontegg’s customer instances are not to be accessed in any way (i.e. no customer data is accessed, customer credentials are not to be used or \"verified\")\n* If you believe you have found sensitive customer data (e.g., login credentials, API keys etc) or a way to access customer data (i.e. through a vulnerability) report it, but do not attempt to successfully validate if/that it works.\n\n# Safe Harbor\nAny 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.\n\nThank you for helping keep Frontegg and our users safe!\n\n\n \n\n\n\n\n\n\n \n \n \n\n \n \n\n \n\n","has_open_scope":null,"pays_within_one_month":null,"protected_by_gold_standard_safe_harbor":null,"protected_by_ai_safe_harbor":null,"disclosure_declaration":null,"introduction":null,"platform_standards_exclusions":[],"exemplary_standards_exclusions":[],"scope_exclusions":[],"timestamp":"2023-11-01T09:33:53.983Z"}]