[{"id":3766328,"new_policy":"We take security seriously at Eternal and are committed to protecting our community. If you are a security researcher or expert and believe you've identified a security-related issue with any of Eternal’s key verticals - Zomato, Blinkit, Hyperpure, or District websites or apps, we encourage you to report it to us responsibly.\n\nOur team is committed to addressing all security reports in a timely and responsible manner. We kindly ask the security community to give us the opportunity to investigate and resolve any issues before making them public. Please include a detailed description of the issue and the steps to reproduce it in your submission.\nWe appreciate the efforts of the security community in helping us safeguard our users’ data and privacy.\n\n\n\n# Disclosure Policy\n* Let us know as soon as possible upon discovery of a potential security issue, and we'll make every effort to quickly resolve the issue.\n* Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party.\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\n# Test Plan\nPlease include a header `X-Hackerone: \u003ch1_username\u003e` when you test so we can identify your requests easily.\n\n# Scope\nThe scope of issues is limited to technical vulnerabilities in the Eternal website or mobile apps. Please do not attempt to compromise the safety or privacy of our users (so please use test accounts), or the availability of Eternal through DoS attacks or spam. We also request you not to use vulnerability testing tools that generate a significant volume of traffic.\n\nCertain vulnerabilities with a working proof of concept on some of our Android mobile app(s) may qualify for an additional bounty through the [Google Play Security Rewards Program] (https://hackerone.com/googleplay). To see which apps and vulnerabilities may qualify for a bounty, please refer to the [Google Play Security Rewards Program’s Scope and Vulnerability Criteria] (https://hackerone.com/googleplay).\n\n# Rewards\nWe will reward reports according to the severity of their impact on a case-by-case basis as determined by our security team. We may pay more for unique, hard-to-find bugs; we may also pay less for bugs with complex prerequisites that lower the risk of exploitation. \n\nBelow, you can find examples of vulnerabilities and their impacts grouped by our severity ranking. This is not an exhaustive list and it is designed to give you insight on how we rate vulnerabilities. \n\n# Critical \n* Remote Code Execution (RCE) - able to execute arbitrary commands on a remote device\n* SQL Injection - able to read Personally Identifiable Information (PII) or other sensitive data / full read/write access to a database\n* Server-Side Request Forgery (SSRF) - able to pivot to internal application and/or access credentials (not blind)\n* Information Disclosure - mass PII leaks including data such as names, emails, phone numbers and addresses (Combined) \n\n# High \n* Stored Cross-Site Scripting (XSS) - stored XSS with access to non HttpOnly cookies\n* Information Disclosure - leaked credentials\n* Subdomain Takeover - If a proper PoC is provided that can demonstrate an attacker geting access to confidential user data and able to perform unauthorized operations without leveraging phishing attack vectors.\n* Cross-Site Request Forgery (CSRF) - leading to account takeover\n* Account Takeover (ATO) - with no or minimal user interaction\n* Insecure Direct Object Reference (IDOR) - read or write access to sensitive data or important fields that you do not have permission to\n* SQL Injection - able to perform queries with a limited access user\n\n# Medium \n* CSRF - able to modify important information (authenticated) \n* ATO - required user interaction\n* IDOR - write access to modify objects that you do not have permission to\n* XSS - reflected/DOM XSS with access to cookies\n\n# Low \n* Directory listings \n* XSS - Without access to cookies/Auth Data\n* XSS - POST based XSS (with CSRF bypass)\n* Lack of HTTPS on dynamic pages (judged on a case-by-case basis)\n* Server information page (no credentials)\n* Subdomain Takeover - on an unused subdomain\n\n# Eligibility and Responsible Disclosure\nTo promote the discovery and reporting of vulnerabilities and increase user safety, we ask that you:\n* Give us a reasonable time to respond to the issue before making any information about it public.\n* Not access or modify data without the explicit permission of the owner.\n* Act in good faith not to degrade the performance of our services (including denial of service).\n \nWe only reward the first reporter of a vulnerability. Public disclosure of the vulnerability prior to resolution will result in disqualification from the program. You must report a qualifying vulnerability through the HackerOne reporting tool to be eligible for a monetary reward.\n\n# Non-qualifying vulnerabilities / Known Issues\n\nWhen reporting vulnerabilities, please consider (1) attack scenario/exploitability, and (2) the security impact of the bug. The following issues are considered out of scope:\n \n##Informative Bugs\n* Broken Link Hijacking issues are categorized as low severity and are not eligible for rewards.\n* Credential leakage reports are considered informational if two-factor authentication (2FA) is in place\n* SSL Pinning/Root Detection Bypass\n* Security issues related to Zomato Legends are considered informational and are not eligible for rewards, regardless of whether the issue is resolved by the team\n\n------- \n\u0026nbsp;\n\n##Policy for Leaked Credentials\n\n* We offer $50-$150 (depending on the asset tier) per report. Multiple credentials for the same user, or multiple employee accounts exposed in the same source, are treated as one finding. Reports involving administrative accounts or access to sensitive systems - such as production environments or large volumes of personal information - may qualify for higher rewards based on impact.\n* Only the first valid, non-duplicate report for a given leak is eligible for a reward. If the same credentials appear across multiple sources, they will still be counted as a single finding.\nEach application and source is evaluated independently.\n* Submissions must include proof of validity, leak origin, and confirmation that credentials were not misused.\n* Researchers should submit the leaked credentials to the program and should NOT test their validity beyond authenticating and then immediately deauthenticating - without exercising any functionality.\n* Such reports will be evaluated on a case-by-case basis to determine an appropriate reward amount.\n* Employee personal accounts, customer accounts, and merchant accounts are not in scope.\n\n\n--------- \n\u0026nbsp;\n\n## Data Protection Program \n\nAs data protection and trust becomes critical, we are introducing a new area of research for our bug bounty program. \nWe aim to strengthen the overall ecosystem of business that is touched by Eternal. \n\nThis program is complementary to our existing bug bounty program in that it *\"follows the data\"* even if the root cause isn't a security flaw in Eternal’s code or Infrastructure. \"External agents can accidentally compromise or leak Eternal’s data, even when no security vulnerabilities exist. This program is intended to protect against that abuse.\"\nThis program is focused on passive monitoring and recon of our data and doesn’t permit/allow for active hunting or testing.\n\nThough we cannot guarantee legal protection from third parties. We strongly recommend \nresearchers understand the legal risks in their jurisdiction.\n\n    ### What is allowed (Data Protection Program):\n Observing publicly accessible data exposure (e.g., unsecured S3 buckets, public APIs returning customer data)\n Monitoring websites/apps for exposed information\n Using publicly leaked credentials to verify access to Eternal data\n Accessing external  systems using credentials found through passive reconnaissance (e.g., exposed in GitHub, paste sites,   breach compilations)\n Documenting the extent of data accessible through compromised credentials\n Scanning for exposed configuration files, API keys, or access tokens\n\n  ### What is not allowed (Data Protection Program):\n\n Active hunting or testing on any of our partners without their prior approval is NOT allowed. Apart from this, all the program  conditions and policies still apply, when in doubt you can raise a scope request or email us at bugbounty@eternal.com for  clarifications.\n\n\n* Active exploitation or vulnerability testing on external systems\n* Brute forcing, credential stuffing, or password spraying attacks\n* Creating test accounts or transactions to probe external systems\n* Social engineering.\n* Lateral movement within any external systems beyond verifying Eternal data access\n* Modifying, deleting, or exfiltrating large volumes of data\n* Any actions beyond read-only verification of Eternal data exposure\n\n\n ### Credential Usage Guidelines (Data Protection Program):\n\n * When Using Found Credentials:\n * Only access systems to verify Eternal data exposure\n * Limit access to the minimum necessary to document the issue\n * Do not access, modify, or delete data belonging to other customers\n * Do not perform actions that could alert or trigger the security systems\n * Document your access but do not download bulk data\n * Report immediately after verification\n * Do not share credentials with others\n\n While we permit credential-based access verification under this program, \n researchers should be aware that:\n -  External agents may pursue legal action independently\n - Laws vary by jurisdiction regarding unauthorized access\n - We will advocate on your behalf but cannot guarantee legal immunity\n - Document your methodology carefully to demonstrate good faith\n - Consider consulting legal counsel before accessing systems with found credentials\n\n\n ### Bounty structure (Data Protection Program):\n\n As this is a pilot program, rewards currently range from $100 to $500 USD, depending on the severity and impact of the  reported exposure.\n\n We determine reward amounts based on a variety of factors, including:\n\n * Sensitivity of exposed data (payment info, PII, credentials)\n * Volume of customer records affected\n * Ease of discovery and access\n * Duration of exposure\n * Impact on privacy\n * Quality and completeness of your report\n\n The amount of any reward is entirely up to our discretion. We will review and potentially increase reward amounts based on the program's success and community response during the pilot phase. \n\n----------- \n\n\u0026nbsp;\n\n\n## Not Applicable  \u0026 Out of Scope Bugs\n\n* Issues related to Way Back Machine/Web Archive (e.g., leaked invoices or contract documents) will be marked as Not Applicable or (Spam - if reported repeatedly) \n* Google Maps API Keys Leakage\n* HTML Injection \u0026 Context Spoofing(Closed as NA) \n* Cache Poisoning DoS\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/DDoS).\n* Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS\n* Rate limiting or brute force issues\n* Invalidation/expiry on CDN assets\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 implication can be demonstrated \n* Self XSS\n* Promo code abuse (e.g. ordering multiple times using the same promo code)\n* We're aware of Promotion offers/Cash backs Issues (e.g: logic issues in cash back reversing/applying) \n* Abuse of our promotional offers and referral codes\n* CSRF on www.zomato.com/php/* and www.zomato.com/clients*/\n* Promo code enumeration, abuse of our promotional offers and referral codes.\n* Able to retrieve user's public information.\n* Username / email enumeration\n\n# Consequences of complying with this policy\n\nWe will not pursue a civil action or initiate a complaint to law enforcement for accidental, good faith violations of this policy. We consider activities conducted consistent with this policy to constitute “authorized” conduct under the Computer Fraud and Abuse Act (CFAA). We will not bring a DMCA claim against you for circumventing the technological measures we have used to protect the applications in scope.\n\nIf legal action is initiated by a third party against you and you have complied with Eternal's bug bounty policy, Eternal will take steps to make it known that your actions were conducted in compliance with this policy.\n\nPlease submit a [HackerOne report](https://hackerone.com/zomato) to us before engaging in conduct that may be inconsistent with or unaddressed by this policy.\n\nThank you for helping keep @Eternal safe for the community!\nEternal Security Team\n","has_open_scope":null,"pays_within_one_month":true,"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-11-19T07:18:43.667Z"},{"id":3765105,"new_policy":"We take security seriously at Eternal and are committed to protecting our community. If you are a security researcher or expert and believe you've identified a security-related issue with any of Eternal’s key verticals - Zomato, Blinkit, Hyperpure, or District websites or apps, we encourage you to report it to us responsibly.\n\nOur team is committed to addressing all security reports in a timely and responsible manner. We kindly ask the security community to give us the opportunity to investigate and resolve any issues before making them public. Please include a detailed description of the issue and the steps to reproduce it in your submission.\nWe appreciate the efforts of the security community in helping us safeguard our users’ data and privacy.\n\n# Disclosure Policy\n* Let us know as soon as possible upon discovery of a potential security issue, and we'll make every effort to quickly resolve the issue.\n* Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party.\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\n# Test Plan\nPlease include a header `X-Hackerone: \u003ch1_username\u003e` when you test so we can identify your requests easily.\n\n# Scope\nThe scope of issues is limited to technical vulnerabilities in the Eternal website or mobile apps. Please do not attempt to compromise the safety or privacy of our users (so please use test accounts), or the availability of Eternal through DoS attacks or spam. We also request you not to use vulnerability testing tools that generate a significant volume of traffic.\n\nCertain vulnerabilities with a working proof of concept on some of our Android mobile app(s) may qualify for an additional bounty through the [Google Play Security Rewards Program] (https://hackerone.com/googleplay). To see which apps and vulnerabilities may qualify for a bounty, please refer to the [Google Play Security Rewards Program’s Scope and Vulnerability Criteria] (https://hackerone.com/googleplay).\n\n# Rewards\nWe will reward reports according to the severity of their impact on a case-by-case basis as determined by our security team. We may pay more for unique, hard-to-find bugs; we may also pay less for bugs with complex prerequisites that lower the risk of exploitation. \n\nBelow, you can find examples of vulnerabilities and their impacts grouped by our severity ranking. This is not an exhaustive list and it is designed to give you insight on how we rate vulnerabilities. \n\n# Critical \n* Remote Code Execution (RCE) - able to execute arbitrary commands on a remote device\n* SQL Injection - able to read Personally Identifiable Information (PII) or other sensitive data / full read/write access to a database\n* Server-Side Request Forgery (SSRF) - able to pivot to internal application and/or access credentials (not blind)\n* Information Disclosure - mass PII leaks including data such as names, emails, phone numbers and addresses (Combined) \n\n# High \n* Stored Cross-Site Scripting (XSS) - stored XSS with access to non HttpOnly cookies\n* Information Disclosure - leaked credentials\n* Subdomain Takeover - If a proper PoC is provided that can demonstrate an attacker geting access to confidential user data and able to perform unauthorized operations without leveraging phishing attack vectors.\n* Cross-Site Request Forgery (CSRF) - leading to account takeover\n* Account Takeover (ATO) - with no or minimal user interaction\n* Insecure Direct Object Reference (IDOR) - read or write access to sensitive data or important fields that you do not have permission to\n* SQL Injection - able to perform queries with a limited access user\n\n# Medium \n* CSRF - able to modify important information (authenticated) \n* ATO - required user interaction\n* IDOR - write access to modify objects that you do not have permission to\n* XSS - reflected/DOM XSS with access to cookies\n\n# Low \n* Directory listings \n* XSS - Without access to cookies/Auth Data\n* XSS - POST based XSS (with CSRF bypass)\n* Lack of HTTPS on dynamic pages (judged on a case-by-case basis)\n* Server information page (no credentials)\n* Subdomain Takeover - on an unused subdomain\n\n# Eligibility and Responsible Disclosure\nTo promote the discovery and reporting of vulnerabilities and increase user safety, we ask that you:\n* Give us a reasonable time to respond to the issue before making any information about it public.\n* Not access or modify data without the explicit permission of the owner.\n* Act in good faith not to degrade the performance of our services (including denial of service).\n \nWe only reward the first reporter of a vulnerability. Public disclosure of the vulnerability prior to resolution will result in disqualification from the program. You must report a qualifying vulnerability through the HackerOne reporting tool to be eligible for a monetary reward.\n\n# Non-qualifying vulnerabilities / Known Issues\n\nWhen reporting vulnerabilities, please consider (1) attack scenario/exploitability, and (2) the security impact of the bug. The following issues are considered out of scope:\n \n##Informative Bugs\n* Broken Link Hijacking issues are categorized as low severity and are not eligible for rewards.\n* Credential leakage reports are considered informational if two-factor authentication (2FA) is in place\n* SSL Pinning/Root Detection Bypass\n* Security issues related to Zomato Legends are considered informational and are not eligible for rewards, regardless of whether the issue is resolved by the team\n\n##Policy for Leaked Credentials\n* We offer $50-$150 (depending on the asset tier) per report. Multiple credentials for the same user, or multiple employee accounts exposed in the same source, are treated as one finding. Reports involving administrative accounts or access to sensitive systems - such as production environments or large volumes of personal information - may qualify for higher rewards based on impact.\n* Only the first valid, non-duplicate report for a given leak is eligible for a reward. If the same credentials appear across multiple sources, they will still be counted as a single finding.\nEach application and source is evaluated independently.\n* Submissions must include proof of validity, leak origin, and confirmation that credentials were not misused.\n* Researchers should submit the leaked credentials to the program and should NOT test their validity beyond authenticating and then immediately deauthenticating - without exercising any functionality.\n* Such reports will be evaluated on a case-by-case basis to determine an appropriate reward amount.\n* Employee personal accounts, customer accounts, and merchant accounts are not in scope.\n\n\n## Not Applicable  \u0026 Out of Scope Bugs\n\n* Issues related to Way Back Machine/Web Archive (e.g., leaked invoices or contract documents) will be marked as Not Applicable or (Spam - if reported repeatedly) \n* Google Maps API Keys Leakage\n* HTML Injection \u0026 Context Spoofing(Closed as NA) \n* Cache Poisoning DoS\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/DDoS).\n* Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS\n* Rate limiting or brute force issues\n* Invalidation/expiry on CDN assets\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 implication can be demonstrated \n* Self XSS\n* Promo code abuse (e.g. ordering multiple times using the same promo code)\n* We're aware of Promotion offers/Cash backs Issues (e.g: logic issues in cash back reversing/applying) \n* Abuse of our promotional offers and referral codes\n* CSRF on www.zomato.com/php/* and www.zomato.com/clients*/\n* Promo code enumeration, abuse of our promotional offers and referral codes.\n* Able to retrieve user's public information.\n* Username / email enumeration\n\n# Consequences of complying with this policy\n\nWe will not pursue a civil action or initiate a complaint to law enforcement for accidental, good faith violations of this policy. We consider activities conducted consistent with this policy to constitute “authorized” conduct under the Computer Fraud and Abuse Act (CFAA). We will not bring a DMCA claim against you for circumventing the technological measures we have used to protect the applications in scope.\n\nIf legal action is initiated by a third party against you and you have complied with Eternal's bug bounty policy, Eternal will take steps to make it known that your actions were conducted in compliance with this policy.\n\nPlease submit a [HackerOne report](https://hackerone.com/zomato) to us before engaging in conduct that may be inconsistent with or unaddressed by this policy.\n\nThank you for helping keep @Eternal safe for the community!\nEternal Security Team\n","has_open_scope":null,"pays_within_one_month":true,"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-10-24T12:23:42.813Z"},{"id":3757317,"new_policy":"We take security seriously at Eternal and are committed to protecting our community. If you are a security researcher or expert and believe you've identified a security-related issue with any of Eternal’s key verticals - Zomato, Blinkit, Hyperpure, or District websites or apps, we encourage you to report it to us responsibly.\n\nOur team is committed to addressing all security reports in a timely and responsible manner. We kindly ask the security community to give us the opportunity to investigate and resolve any issues before making them public. Please include a detailed description of the issue and the steps to reproduce it in your submission.\nWe appreciate the efforts of the security community in helping us safeguard our users’ data and privacy.\n\n# Disclosure Policy\n* Let us know as soon as possible upon discovery of a potential security issue, and we'll make every effort to quickly resolve the issue.\n* Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party.\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\n# Test Plan\nPlease include a header `X-Hackerone: \u003ch1_username\u003e` when you test so we can identify your requests easily.\n\n# Scope\nThe scope of issues is limited to technical vulnerabilities in the Eternal website or mobile apps. Please do not attempt to compromise the safety or privacy of our users (so please use test accounts), or the availability of Eternal through DoS attacks or spam. We also request you not to use vulnerability testing tools that generate a significant volume of traffic.\n\nCertain vulnerabilities with a working proof of concept on some of our Android mobile app(s) may qualify for an additional bounty through the [Google Play Security Rewards Program] (https://hackerone.com/googleplay). To see which apps and vulnerabilities may qualify for a bounty, please refer to the [Google Play Security Rewards Program’s Scope and Vulnerability Criteria] (https://hackerone.com/googleplay).\n\n# Rewards\nWe will reward reports according to the severity of their impact on a case-by-case basis as determined by our security team. We may pay more for unique, hard-to-find bugs; we may also pay less for bugs with complex prerequisites that lower the risk of exploitation. \n\nBelow, you can find examples of vulnerabilities and their impacts grouped by our severity ranking. This is not an exhaustive list and it is designed to give you insight on how we rate vulnerabilities. \n\n# Critical \n* Remote Code Execution (RCE) - able to execute arbitrary commands on a remote device\n* SQL Injection - able to read Personally Identifiable Information (PII) or other sensitive data / full read/write access to a database\n* Server-Side Request Forgery (SSRF) - able to pivot to internal application and/or access credentials (not blind)\n* Information Disclosure - mass PII leaks including data such as names, emails, phone numbers and addresses (Combined) \n\n# High \n* Stored Cross-Site Scripting (XSS) - stored XSS with access to non HttpOnly cookies\n* Information Disclosure - leaked credentials\n* Subdomain Takeover - If a proper PoC is provided that can demonstrate an attacker geting access to confidential user data and able to perform unauthorized operations without leveraging phishing attack vectors.\n* Cross-Site Request Forgery (CSRF) - leading to account takeover\n* Account Takeover (ATO) - with no or minimal user interaction\n* Insecure Direct Object Reference (IDOR) - read or write access to sensitive data or important fields that you do not have permission to\n* SQL Injection - able to perform queries with a limited access user\n\n# Medium \n* CSRF - able to modify important information (authenticated) \n* ATO - required user interaction\n* IDOR - write access to modify objects that you do not have permission to\n* XSS - reflected/DOM XSS with access to cookies\n\n# Low \n* Directory listings \n* XSS - Without access to cookies/Auth Data\n* XSS - POST based XSS (with CSRF bypass)\n* Lack of HTTPS on dynamic pages (judged on a case-by-case basis)\n* Server information page (no credentials)\n* Subdomain Takeover - on an unused subdomain\n\n# Eligibility and Responsible Disclosure\nTo promote the discovery and reporting of vulnerabilities and increase user safety, we ask that you:\n* Give us a reasonable time to respond to the issue before making any information about it public.\n* Not access or modify data without the explicit permission of the owner.\n* Act in good faith not to degrade the performance of our services (including denial of service).\n \nWe only reward the first reporter of a vulnerability. Public disclosure of the vulnerability prior to resolution will result in disqualification from the program. You must report a qualifying vulnerability through the HackerOne reporting tool to be eligible for a monetary reward.\n\n# Non-qualifying vulnerabilities / Known Issues\n\nWhen reporting vulnerabilities, please consider (1) attack scenario/exploitability, and (2) the security impact of the bug. The following issues are considered out of scope:\n \n##Informative Bugs\n* Broken Link Hijacking issues are categorized as low severity and are not eligible for rewards.\n* Credential leakage reports are considered informational if two-factor authentication (2FA) is in place\n* SSL Pinning/Root Detection Bypass\n* Security issues related to Zomato Legends are considered informational and are not eligible for rewards, regardless of whether the issue is resolved by the team\n\n\n## Not Applicable  \u0026 Out of Scope Bugs\n\n* Issues related to Way Back Machine/Web Archive (e.g., leaked invoices or contract documents) will be marked as Not Applicable or (Spam - if reported repeatedly) \n* Google Maps API Keys Leakage\n* HTML Injection \u0026 Context Spoofing(Closed as NA) \n* Cache Poisoning DoS\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/DDoS).\n* Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS\n* Rate limiting or brute force issues\n* Invalidation/expiry on CDN assets\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 implication can be demonstrated \n* Self XSS\n* Promo code abuse (e.g. ordering multiple times using the same promo code)\n* We're aware of Promotion offers/Cash backs Issues (e.g: logic issues in cash back reversing/applying) \n* Abuse of our promotional offers and referral codes\n* CSRF on www.zomato.com/php/* and www.zomato.com/clients*/\n* Promo code enumeration, abuse of our promotional offers and referral codes.\n* Able to retrieve user's public information.\n* Username / email enumeration\n\n# Consequences of complying with this policy\n\nWe will not pursue a civil action or initiate a complaint to law enforcement for accidental, good faith violations of this policy. We consider activities conducted consistent with this policy to constitute “authorized” conduct under the Computer Fraud and Abuse Act (CFAA). We will not bring a DMCA claim against you for circumventing the technological measures we have used to protect the applications in scope.\n\nIf legal action is initiated by a third party against you and you have complied with Eternal's bug bounty policy, Eternal will take steps to make it known that your actions were conducted in compliance with this policy.\n\nPlease submit a [HackerOne report](https://hackerone.com/zomato) to us before engaging in conduct that may be inconsistent with or unaddressed by this policy.\n\nThank you for helping keep @Eternal safe for the community!\nEternal Security Team\n","has_open_scope":null,"pays_within_one_month":true,"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-06-11T11:17:15.800Z"},{"id":3756766,"new_policy":"We take security seriously at Eternal and are committed to protecting our community. If you are a security researcher or expert and believe you've identified a security-related issue with any of Eternal’s key verticals - Zomato, Blinkit, Hyperpure, or District websites or apps, we encourage you to report it to us responsibly.\n\nOur team is committed to addressing all security reports in a timely and responsible manner. We kindly ask the security community to give us the opportunity to investigate and resolve any issues before making them public. Please include a detailed description of the issue and the steps to reproduce it in your submission.\nWe appreciate the efforts of the security community in helping us safeguard our users’ data and privacy.\n\n# Disclosure Policy\n* Let us know as soon as possible upon discovery of a potential security issue, and we'll make every effort to quickly resolve the issue.\n* Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party.\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\n# Test Plan\nPlease include a header `X-Hackerone: \u003ch1_username\u003e` when you test so we can identify your requests easily.\n\n# Scope\nThe scope of issues is limited to technical vulnerabilities in the Eternal website or mobile apps. Please do not attempt to compromise the safety or privacy of our users (so please use test accounts), or the availability of Eternal through DoS attacks or spam. We also request you not to use vulnerability testing tools that generate a significant volume of traffic.\n\nCertain vulnerabilities with a working proof of concept on some of our Android mobile app(s) may qualify for an additional bounty through the [Google Play Security Rewards Program] (https://hackerone.com/googleplay). To see which apps and vulnerabilities may qualify for a bounty, please refer to the [Google Play Security Rewards Program’s Scope and Vulnerability Criteria] (https://hackerone.com/googleplay).\n\n# Rewards\nWe will reward reports according to the severity of their impact on a case-by-case basis as determined by our security team. We may pay more for unique, hard-to-find bugs; we may also pay less for bugs with complex prerequisites that lower the risk of exploitation. \n\nBelow, you can find examples of vulnerabilities and their impacts grouped by our severity ranking. This is not an exhaustive list and it is designed to give you insight on how we rate vulnerabilities. \n\n# Critical \n* Remote Code Execution (RCE) - able to execute arbitrary commands on a remote device\n* SQL Injection - able to read Personally Identifiable Information (PII) or other sensitive data / full read/write access to a database\n* Server-Side Request Forgery (SSRF) - able to pivot to internal application and/or access credentials (not blind)\n* Information Disclosure - mass PII leaks including data such as names, emails, phone numbers and addresses (Combined) \n\n# High \n* Stored Cross-Site Scripting (XSS) - stored XSS with access to non HttpOnly cookies\n* Information Disclosure - leaked credentials\n* Subdomain Takeover - If a proper PoC is provided that can demonstrate an attacker geting access to confidential user data and able to perform unauthorized operations without leveraging phishing attack vectors.\n* Cross-Site Request Forgery (CSRF) - leading to account takeover\n* Account Takeover (ATO) - with no or minimal user interaction\n* Insecure Direct Object Reference (IDOR) - read or write access to sensitive data or important fields that you do not have permission to\n* SQL Injection - able to perform queries with a limited access user\n\n# Medium \n* CSRF - able to modify important information (authenticated) \n* ATO - required user interaction\n* IDOR - write access to modify objects that you do not have permission to\n* XSS - reflected/DOM XSS with access to cookies\n\n# Low \n* Directory listings \n* XSS - Without access to cookies/Auth Data\n* XSS - POST based XSS (with CSRF bypass)\n* Lack of HTTPS on dynamic pages (judged on a case-by-case basis)\n* Server information page (no credentials)\n* Subdomain Takeover - on an unused subdomain\n\n# Eligibility and Responsible Disclosure\nTo promote the discovery and reporting of vulnerabilities and increase user safety, we ask that you:\n* Give us a reasonable time to respond to the issue before making any information about it public.\n* Not access or modify data without the explicit permission of the owner.\n* Act in good faith not to degrade the performance of our services (including denial of service).\n \nWe only reward the first reporter of a vulnerability. Public disclosure of the vulnerability prior to resolution will result in disqualification from the program. You must report a qualifying vulnerability through the HackerOne reporting tool to be eligible for a monetary reward.\n\n# Non-qualifying vulnerabilities / Known Issues\n\nWhen reporting vulnerabilities, please consider (1) attack scenario/exploitability, and (2) the security impact of the bug. The following issues are considered out of scope:\n \n##Informative Bugs\n* Broken Link Hijacking issues are categorized as low severity and are not eligible for rewards.\n* Credential leakage reports are considered informational if two-factor authentication (2FA) is in place\n* SSL Pinning/Root Detection Bypass\n* Security issues related to Zomato Legends are considered informational and are not eligible for rewards, regardless of whether the issue is resolved by the team\n\n\n## Not Applicable  \u0026 Out of Scope Bugs\n\n* Issues related to Way Back Machine/Web Archive (e.g., leaked invoices or contract documents) will be marked as Not Applicable or (Spam - if reported repeatedly) \n* Google Maps API Keys Leakage\n* HTML Injection \u0026 Context Spoofing(Closed as NA) \n* Cache Poisoning DoS\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/DDoS).\n* Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS\n* Rate limiting or brute force issues\n* Invalidation/expiry on CDN assets\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 implication can be demonstrated \n* Self XSS\n* Promo code abuse (e.g. ordering multiple times using the same promo code)\n* We're aware of Promotion offers/Cash backs Issues (e.g: logic issues in cash back reversing/applying) \n* Abuse of our promotional offers and referral codes\n* CSRF on www.zomato.com/php/* and www.zomato.com/clients*/\n* Promo code enumeration, abuse of our promotional offers and referral codes.\n* Able to retrieve user's public information.\n* Username / email enumeration\n\n# Consequences of complying with this policy\n\nWe will not pursue a civil action or initiate a complaint to law enforcement for accidental, good faith violations of this policy. We consider activities conducted consistent with this policy to constitute “authorized” conduct under the Computer Fraud and Abuse Act (CFAA). We will not bring a DMCA claim against you for circumventing the technological measures we have used to protect the applications in scope.\n\nIf legal action is initiated by a third party against you and you have complied with Eternal's bug bounty policy, Eternal will take steps to make it known that your actions were conducted in compliance with this policy.\n\nPlease submit a [HackerOne report](https://hackerone.com/zomato) to us before engaging in conduct that may be inconsistent with or unaddressed by this policy.\n\nThank you for helping keep @Zomato safe for the community!\nEternal Security Team\n","has_open_scope":null,"pays_within_one_month":true,"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-06-03T10:04:02.525Z"},{"id":3756763,"new_policy":"We take security seriously at Eternal and are committed to protecting our community. If you are a security researcher or expert and believe you've identified a security-related issue with any of Eternal’s key verticals - Zomato, Blinkit, Hyperpure, or District websites or apps, we encourage you to report it to us responsibly.\n\nOur team is committed to addressing all security reports in a timely and responsible manner. We kindly ask the security community to give us the opportunity to investigate and resolve any issues before making them public. Please include a detailed description of the issue and the steps to reproduce it in your submission.\nWe appreciate the efforts of the security community in helping us safeguard our users’ data and privacy.\n\n# Disclosure Policy\n* Let us know as soon as possible upon discovery of a potential security issue, and we'll make every effort to quickly resolve the issue.\n* Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party.\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\n# Test Plan\nPlease include a header `X-Hackerone: \u003ch1_username\u003e` when you test so we can identify your requests easily.\n\n# Scope\nThe scope of issues is limited to technical vulnerabilities in the Eternal website or mobile apps. Please do not attempt to compromise the safety or privacy of our users (so please use test accounts), or the availability of Eternal through DoS attacks or spam. We also request you not to use vulnerability testing tools that generate a significant volume of traffic.\n\nCertain vulnerabilities with a working proof of concept on some of our Android mobile app(s) may qualify for an additional bounty through the [Google Play Security Rewards Program] (https://hackerone.com/googleplay). To see which apps and vulnerabilities may qualify for a bounty, please refer to the [Google Play Security Rewards Program’s Scope and Vulnerability Criteria] (https://hackerone.com/googleplay).\n\n# Rewards\nWe will reward reports according to the severity of their impact on a case-by-case basis as determined by our security team. We may pay more for unique, hard-to-find bugs; we may also pay less for bugs with complex prerequisites that lower the risk of exploitation. \n\nBelow, you can find examples of vulnerabilities and their impacts grouped by our severity ranking. This is not an exhaustive list and it is designed to give you insight on how we rate vulnerabilities. \n\n# Critical \n* Remote Code Execution (RCE) - able to execute arbitrary commands on a remote device\n* SQL Injection - able to read Personally Identifiable Information (PII) or other sensitive data / full read/write access to a database\n* Server-Side Request Forgery (SSRF) - able to pivot to internal application and/or access credentials (not blind)\n* Information Disclosure - mass PII leaks including data such as names, emails, phone numbers and addresses (Combined) \n\n# High \n* Stored Cross-Site Scripting (XSS) - stored XSS with access to non HttpOnly cookies\n* Information Disclosure - leaked credentials\n* Subdomain Takeover - If a proper PoC is provided that can demonstrate an attacker geting access to confidential user data and able to perform unauthorized operations without leveraging phishing attack vectors.\n* Cross-Site Request Forgery (CSRF) - leading to account takeover\n* Account Takeover (ATO) - with no or minimal user interaction\n* Insecure Direct Object Reference (IDOR) - read or write access to sensitive data or important fields that you do not have permission to\n* SQL Injection - able to perform queries with a limited access user\n\n# Medium \n* CSRF - able to modify important information (authenticated) \n* ATO - required user interaction\n* IDOR - write access to modify objects that you do not have permission to\n* XSS - reflected/DOM XSS with access to cookies\n\n# Low \n* Directory listings \n* XSS - Without access to cookies/Auth Data\n* XSS - POST based XSS (with CSRF bypass)\n* Lack of HTTPS on dynamic pages (judged on a case-by-case basis)\n* Server information page (no credentials)\n* Subdomain Takeover - on an unused subdomain\n\n# Eligibility and Responsible Disclosure\nTo promote the discovery and reporting of vulnerabilities and increase user safety, we ask that you:\n* Give us a reasonable time to respond to the issue before making any information about it public.\n* Not access or modify data without the explicit permission of the owner.\n* Act in good faith not to degrade the performance of our services (including denial of service).\n \nWe only reward the first reporter of a vulnerability. Public disclosure of the vulnerability prior to resolution will result in disqualification from the program. You must report a qualifying vulnerability through the HackerOne reporting tool to be eligible for a monetary reward.\n\n# Non-qualifying vulnerabilities / Known Issues\n\nWhen reporting vulnerabilities, please consider (1) attack scenario/exploitability, and (2) the security impact of the bug. The following issues are considered out of scope:\n \n##Informative Bugs\n* Broken Link Hijacking issues are categorized as low severity and are not eligible for rewards.\n* Credential leakage reports are considered informational if two-factor authentication (2FA) is in place\n* SSL Pinning/Root Detection Bypass\n* Security issues related to Zomato Legends are considered informational and are not eligible for rewards, regardless of whether the issue is resolved by the team\n\n\n## Not Applicable  \u0026 Out of Scope Bugs\n\n* Issues related to Way Back Machine/Web Archive (e.g., leaked invoices or contract documents) will be marked as Not Applicable or (Spam - if reported repeatedly) \n* Google Maps API Keys Leakage\n* HTML Injection \u0026 Context Spoofing(Closed as NA) \n* Cache Poisoning DoS\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/DDoS).\n* Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS\n* Rate limiting or brute force issues\n* Invalidation/expiry on CDN assets\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 implication can be demonstrated \n* Self XSS\n* Promo code abuse (e.g. ordering multiple times using the same promo code)\n* We're aware of Promotion offers/Cash backs Issues (e.g: logic issues in cash back reversing/applying) \n* Abuse of our promotional offers and referral codes\n* CSRF on www.zomato.com/php/* and www.zomato.com/clients*/\n* Promo code enumeration, abuse of our promotional offers and referral codes.\n* Able to retrieve user's public information.\n* Username / email enumeration\n\n# Consequences of complying with this policy\n\nWe will not pursue a civil action or initiate a complaint to law enforcement for accidental, good faith violations of this policy. We consider activities conducted consistent with this policy to constitute “authorized” conduct under the Computer Fraud and Abuse Act (CFAA). We will not bring a DMCA claim against you for circumventing the technological measures we have used to protect the applications in scope.\n\nIf legal action is initiated by a third party against you and you have complied with Eternal's bug bounty policy, Eternal will take steps to make it known that your actions were conducted in compliance with this policy.\n\nPlease submit a [HackerOne report](https://hackerone.com/zomato) to us before engaging in conduct that may be inconsistent with or unaddressed by this policy.\n\nThank you for helping keep @Zomato safe for the community!\nEternal Security Team\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-06-03T09:44:57.325Z"},{"id":3756762,"new_policy":"We take security seriously at Eternal and are committed to protecting our community. If you are a security researcher or expert and believe you've identified a security-related issue with any of Eternal’s key verticals - Zomato, Blinkit, Hyperpure, or District websites or apps, we encourage you to report it to us responsibly.\n\nOur team is committed to addressing all security reports in a timely and responsible manner. We kindly ask the security community to give us the opportunity to investigate and resolve any issues before making them public. Please include a detailed description of the issue and the steps to reproduce it in your submission.\nWe appreciate the efforts of the security community in helping us safeguard our users’ data and privacy.\n\n# Disclosure Policy\n* Let us know as soon as possible upon discovery of a potential security issue, and we'll make every effort to quickly resolve the issue.\n* Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party.\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\n# Test Plan\nPlease include a header `X-Hackerone: \u003ch1_username\u003e` when you test so we can identify your requests easily.\n\n# Scope\nThe scope of issues is limited to technical vulnerabilities in the Zomato website or mobile apps. Please do not attempt to compromise the safety or privacy of our users (so please use test accounts), or the availability of Zomato through DoS attacks or spam. We also request you not to use vulnerability testing tools that generate a significant volume of traffic.\n\nCertain vulnerabilities with a working proof of concept on some of our Android mobile app(s) may qualify for an additional bounty through the [Google Play Security Rewards Program] (https://hackerone.com/googleplay). To see which apps and vulnerabilities may qualify for a bounty, please refer to the [Google Play Security Rewards Program’s Scope and Vulnerability Criteria] (https://hackerone.com/googleplay).\n\n# Rewards\nWe will reward reports according to the severity of their impact on a case-by-case basis as determined by our security team. We may pay more for unique, hard-to-find bugs; we may also pay less for bugs with complex prerequisites that lower the risk of exploitation. \n\nBelow, you can find examples of vulnerabilities and their impacts grouped by our severity ranking. This is not an exhaustive list and it is designed to give you insight on how we rate vulnerabilities. \n\n# Critical \n* Remote Code Execution (RCE) - able to execute arbitrary commands on a remote device\n* SQL Injection - able to read Personally Identifiable Information (PII) or other sensitive data / full read/write access to a database\n* Server-Side Request Forgery (SSRF) - able to pivot to internal application and/or access credentials (not blind)\n* Information Disclosure - mass PII leaks including data such as names, emails, phone numbers and addresses (Combined) \n\n# High \n* Stored Cross-Site Scripting (XSS) - stored XSS with access to non HttpOnly cookies\n* Information Disclosure - leaked credentials\n* Subdomain Takeover - If a proper PoC is provided that can demonstrate an attacker geting access to confidential user data and able to perform unauthorized operations without leveraging phishing attack vectors.\n* Cross-Site Request Forgery (CSRF) - leading to account takeover\n* Account Takeover (ATO) - with no or minimal user interaction\n* Insecure Direct Object Reference (IDOR) - read or write access to sensitive data or important fields that you do not have permission to\n* SQL Injection - able to perform queries with a limited access user\n\n# Medium \n* CSRF - able to modify important information (authenticated) \n* ATO - required user interaction\n* IDOR - write access to modify objects that you do not have permission to\n* XSS - reflected/DOM XSS with access to cookies\n\n# Low \n* Directory listings \n* XSS - Without access to cookies/Auth Data\n* XSS - POST based XSS (with CSRF bypass)\n* Lack of HTTPS on dynamic pages (judged on a case-by-case basis)\n* Server information page (no credentials)\n* Subdomain Takeover - on an unused subdomain\n\n# Eligibility and Responsible Disclosure\nTo promote the discovery and reporting of vulnerabilities and increase user safety, we ask that you:\n* Give us a reasonable time to respond to the issue before making any information about it public.\n* Not access or modify data without the explicit permission of the owner.\n* Act in good faith not to degrade the performance of our services (including denial of service).\n \nWe only reward the first reporter of a vulnerability. Public disclosure of the vulnerability prior to resolution will result in disqualification from the program. You must report a qualifying vulnerability through the HackerOne reporting tool to be eligible for a monetary reward.\n\n# Non-qualifying vulnerabilities / Known Issues\n\nWhen reporting vulnerabilities, please consider (1) attack scenario/exploitability, and (2) the security impact of the bug. The following issues are considered out of scope:\n \n##Informative Bugs\n* Broken Link Hijacking issues are categorized as low severity and are not eligible for rewards.\n* Credential leakage reports are considered informational if two-factor authentication (2FA) is in place\n* SSL Pinning/Root Detection Bypass\n* Security issues related to Zomato Legends are considered informational and are not eligible for rewards, regardless of whether the issue is resolved by the team\n\n\n## Not Applicable  \u0026 Out of Scope Bugs\n\n* Issues related to Way Back Machine/Web Archive (e.g., leaked invoices or contract documents) will be marked as Not Applicable or (Spam - if reported repeatedly) \n* Google Maps API Keys Leakage\n* HTML Injection \u0026 Context Spoofing(Closed as NA) \n* Cache Poisoning DoS\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/DDoS).\n* Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS\n* Rate limiting or brute force issues\n* Invalidation/expiry on CDN assets\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 implication can be demonstrated \n* Self XSS\n* Promo code abuse (e.g. ordering multiple times using the same promo code)\n* We're aware of Promotion offers/Cash backs Issues (e.g: logic issues in cash back reversing/applying) \n* Abuse of our promotional offers and referral codes\n* CSRF on www.zomato.com/php/* and www.zomato.com/clients*/\n* Promo code enumeration, abuse of our promotional offers and referral codes.\n* Able to retrieve user's public information.\n* Username / email enumeration\n\n# Consequences of complying with this policy\n\nWe will not pursue a civil action or initiate a complaint to law enforcement for accidental, good faith violations of this policy. We consider activities conducted consistent with this policy to constitute “authorized” conduct under the Computer Fraud and Abuse Act (CFAA). We will not bring a DMCA claim against you for circumventing the technological measures we have used to protect the applications in scope.\n\nIf legal action is initiated by a third party against you and you have complied with Zomato's bug bounty policy, Zomato will take steps to make it known that your actions were conducted in compliance with this policy.\n\nPlease submit a [HackerOne report](https://hackerone.com/zomato) to us before engaging in conduct that may be inconsistent with or unaddressed by this policy.\n\nThank you for helping keep @Zomato safe for the community!\nZomato Security Team\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-06-03T09:42:11.812Z"},{"id":3752141,"new_policy":"We take security seriously at Zomato, and we’re committed to protecting our community. If you are a security researcher or expert and believe you’ve identified security-related issues with Zomato’s website or apps, we would appreciate you disclosing it to us responsibly. \n\nOur team is committed to addressing all security issues in a responsible and timely manner, and we ask the security community to give us the opportunity to do so before disclosing them publicly. Please submit a detailed description of the issue to us, along with the steps to reproduce it. We trust the security community to make every effort to protect our users’ data and privacy. \n\n# Disclosure Policy\n* Let us know as soon as possible upon discovery of a potential security issue, and we'll make every effort to quickly resolve the issue.\n* Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party.\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\n# Test Plan\nPlease include a header `X-Hackerone: \u003ch1_username\u003e` when you test so we can identify your requests easily.\n\n# Scope\nThe scope of issues is limited to technical vulnerabilities in the Zomato website or mobile apps. Please do not attempt to compromise the safety or privacy of our users (so please use test accounts), or the availability of Zomato through DoS attacks or spam. We also request you not to use vulnerability testing tools that generate a significant volume of traffic.\n\nCertain vulnerabilities with a working proof of concept on some of our Android mobile app(s) may qualify for an additional bounty through the [Google Play Security Rewards Program] (https://hackerone.com/googleplay). To see which apps and vulnerabilities may qualify for a bounty, please refer to the [Google Play Security Rewards Program’s Scope and Vulnerability Criteria] (https://hackerone.com/googleplay).\n\n# Rewards\nWe will reward reports according to the severity of their impact on a case-by-case basis as determined by our security team. We may pay more for unique, hard-to-find bugs; we may also pay less for bugs with complex prerequisites that lower the risk of exploitation. \n\nBelow, you can find examples of vulnerabilities and their impacts grouped by our severity ranking. This is not an exhaustive list and it is designed to give you insight on how we rate vulnerabilities. \n\n# Critical \n* Remote Code Execution (RCE) - able to execute arbitrary commands on a remote device\n* SQL Injection - able to read Personally Identifiable Information (PII) or other sensitive data / full read/write access to a database\n* Server-Side Request Forgery (SSRF) - able to pivot to internal application and/or access credentials (not blind)\n* Information Disclosure - mass PII leaks including data such as names, emails, phone numbers and addresses (Combined) \n\n# High \n* Stored Cross-Site Scripting (XSS) - stored XSS with access to non HttpOnly cookies\n* Information Disclosure - leaked credentials\n* Subdomain Takeover - If a proper PoC is provided that can demonstrate an attacker geting access to confidential user data and able to perform unauthorized operations without leveraging phishing attack vectors.\n* Cross-Site Request Forgery (CSRF) - leading to account takeover\n* Account Takeover (ATO) - with no or minimal user interaction\n* Insecure Direct Object Reference (IDOR) - read or write access to sensitive data or important fields that you do not have permission to\n* SQL Injection - able to perform queries with a limited access user\n\n# Medium \n* CSRF - able to modify important information (authenticated) \n* ATO - required user interaction\n* IDOR - write access to modify objects that you do not have permission to\n* XSS - reflected/DOM XSS with access to cookies\n\n# Low \n* Directory listings \n* XSS - Without access to cookies/Auth Data\n* XSS - POST based XSS (with CSRF bypass)\n* Lack of HTTPS on dynamic pages (judged on a case-by-case basis)\n* Server information page (no credentials)\n* Subdomain Takeover - on an unused subdomain\n\n# Eligibility and Responsible Disclosure\nTo promote the discovery and reporting of vulnerabilities and increase user safety, we ask that you:\n* Give us a reasonable time to respond to the issue before making any information about it public.\n* Not access or modify data without the explicit permission of the owner.\n* Act in good faith not to degrade the performance of our services (including denial of service).\n \nWe only reward the first reporter of a vulnerability. Public disclosure of the vulnerability prior to resolution will result in disqualification from the program. You must report a qualifying vulnerability through the HackerOne reporting tool to be eligible for a monetary reward.\n\n# Non-qualifying vulnerabilities / Known Issues\n\nWhen reporting vulnerabilities, please consider (1) attack scenario/exploitability, and (2) the security impact of the bug. The following issues are considered out of scope:\n \n##Informative Bugs\n* Broken Link Hijacking issues are categorized as low severity and are not eligible for rewards.\n* Credential leakage reports are considered informational if two-factor authentication (2FA) is in place\n* SSL Pinning/Root Detection Bypass\n* Security issues related to Zomato Legends are considered informational and are not eligible for rewards, regardless of whether the issue is resolved by the team\n\n\n## Not Applicable  \u0026 Out of Scope Bugs\n\n* Issues related to Way Back Machine/Web Archive (e.g., leaked invoices or contract documents) will be marked as Not Applicable or (Spam - if reported repeatedly) \n* Google Maps API Keys Leakage\n* HTML Injection \u0026 Context Spoofing(Closed as NA) \n* Cache Poisoning DoS\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/DDoS).\n* Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS\n* Rate limiting or brute force issues\n* Invalidation/expiry on CDN assets\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 implication can be demonstrated \n* Self XSS\n* Promo code abuse (e.g. ordering multiple times using the same promo code)\n* We're aware of Promotion offers/Cash backs Issues (e.g: logic issues in cash back reversing/applying) \n* Abuse of our promotional offers and referral codes\n* CSRF on www.zomato.com/php/* and www.zomato.com/clients*/\n* Promo code enumeration, abuse of our promotional offers and referral codes.\n* Able to retrieve user's public information.\n* Username / email enumeration\n\n# Consequences of complying with this policy\n\nWe will not pursue a civil action or initiate a complaint to law enforcement for accidental, good faith violations of this policy. We consider activities conducted consistent with this policy to constitute “authorized” conduct under the Computer Fraud and Abuse Act (CFAA). We will not bring a DMCA claim against you for circumventing the technological measures we have used to protect the applications in scope.\n\nIf legal action is initiated by a third party against you and you have complied with Zomato's bug bounty policy, Zomato will take steps to make it known that your actions were conducted in compliance with this policy.\n\nPlease submit a [HackerOne report](https://hackerone.com/zomato) to us before engaging in conduct that may be inconsistent with or unaddressed by this policy.\n\nThank you for helping keep @Zomato safe for the community!\nZomato Security Team\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-03-20T06:57:16.189Z"},{"id":3749007,"new_policy":"We take security seriously at Zomato, and we’re committed to protecting our community. If you are a security researcher or expert and believe you’ve identified security-related issues with Zomato’s website or apps, we would appreciate you disclosing it to us responsibly. \n\nOur team is committed to addressing all security issues in a responsible and timely manner, and we ask the security community to give us the opportunity to do so before disclosing them publicly. Please submit a detailed description of the issue to us, along with the steps to reproduce it. We trust the security community to make every effort to protect our users’ data and privacy. \n\n# Disclosure Policy\n* Let us know as soon as possible upon discovery of a potential security issue, and we'll make every effort to quickly resolve the issue.\n* Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party.\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\n# Test Plan\nPlease include a header `X-Hackerone: \u003ch1_username\u003e` when you test so we can identify your requests easily.\n\n# Scope\nThe scope of issues is limited to technical vulnerabilities in the Zomato website or mobile apps. Please do not attempt to compromise the safety or privacy of our users (so please use test accounts), or the availability of Zomato through DoS attacks or spam. We also request you not to use vulnerability testing tools that generate a significant volume of traffic.\n\nCertain vulnerabilities with a working proof of concept on some of our Android mobile app(s) may qualify for an additional bounty through the [Google Play Security Rewards Program] (https://hackerone.com/googleplay). To see which apps and vulnerabilities may qualify for a bounty, please refer to the [Google Play Security Rewards Program’s Scope and Vulnerability Criteria] (https://hackerone.com/googleplay).\n\n# Rewards\nWe will reward reports according to the severity of their impact on a case-by-case basis as determined by our security team. We may pay more for unique, hard-to-find bugs; we may also pay less for bugs with complex prerequisites that lower the risk of exploitation. \n\nBelow, you can find examples of vulnerabilities and their impacts grouped by our severity ranking. This is not an exhaustive list and it is designed to give you insight on how we rate vulnerabilities. \n\n# Critical \n* Remote Code Execution (RCE) - able to execute arbitrary commands on a remote device\n* SQL Injection - able to read Personally Identifiable Information (PII) or other sensitive data / full read/write access to a database\n* Server-Side Request Forgery (SSRF) - able to pivot to internal application and/or access credentials (not blind)\n* Information Disclosure - mass PII leaks including data such as names, emails, phone numbers and addresses (Combined) \n\n# High \n* Stored Cross-Site Scripting (XSS) - stored XSS with access to non HttpOnly cookies\n* Information Disclosure - leaked credentials\n* Subdomain Takeover - on a domain that sees heavy traffic or would be a convincing candidate for a phishing attack\n* Cross-Site Request Forgery (CSRF) - leading to account takeover\n* Account Takeover (ATO) - with no or minimal user interaction\n* Insecure Direct Object Reference (IDOR) - read or write access to sensitive data or important fields that you do not have permission to\n* SQL Injection - able to perform queries with a limited access user\n\n# Medium \n* CSRF - able to modify important information (authenticated) \n* ATO - required user interaction\n* IDOR - write access to modify objects that you do not have permission to\n* XSS - reflected/DOM XSS with access to cookies\n\n# Low \n* Directory listings \n* XSS - Without access to cookies/Auth Data\n* XSS - POST based XSS (with CSRF bypass)\n* Lack of HTTPS on dynamic pages (judged on a case-by-case basis)\n* Server information page (no credentials)\n* Subdomain Takeover - on an unused subdomain\n\n# Eligibility and Responsible Disclosure\nTo promote the discovery and reporting of vulnerabilities and increase user safety, we ask that you:\n* Give us a reasonable time to respond to the issue before making any information about it public.\n* Not access or modify data without the explicit permission of the owner.\n* Act in good faith not to degrade the performance of our services (including denial of service).\n \nWe only reward the first reporter of a vulnerability. Public disclosure of the vulnerability prior to resolution will result in disqualification from the program. You must report a qualifying vulnerability through the HackerOne reporting tool to be eligible for a monetary reward.\n\n# Non-qualifying vulnerabilities / Known Issues\n\nWhen reporting vulnerabilities, please consider (1) attack scenario/exploitability, and (2) the security impact of the bug. The following issues are considered out of scope:\n \n##Informative Bugs\n* Broken Link Hijacking issues are categorized as low severity and are not eligible for rewards.\n* Credential leakage reports are considered informational if two-factor authentication (2FA) is in place\n* SSL Pinning/Root Detection Bypass\n* Security issues related to Zomato Legends are considered informational and are not eligible for rewards, regardless of whether the issue is resolved by the team\n\n\n## Not Applicable  \u0026 Out of Scope Bugs\n\n* Issues related to Way Back Machine/Web Archive (e.g., leaked invoices or contract documents) will be marked as Not Applicable or (Spam - if reported repeatedly) \n* Google Maps API Keys Leakage\n* HTML Injection \u0026 Context Spoofing(Closed as NA) \n* Cache Poisoning DoS\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/DDoS).\n* Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS\n* Rate limiting or brute force issues\n* Invalidation/expiry on CDN assets\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 implication can be demonstrated \n* Self XSS\n* Promo code abuse (e.g. ordering multiple times using the same promo code)\n* We're aware of Promotion offers/Cash backs Issues (e.g: logic issues in cash back reversing/applying) \n* Abuse of our promotional offers and referral codes\n* CSRF on www.zomato.com/php/* and www.zomato.com/clients*/\n* Promo code enumeration, abuse of our promotional offers and referral codes.\n* Able to retrieve user's public information.\n* Username / email enumeration\n\n# Consequences of complying with this policy\n\nWe will not pursue a civil action or initiate a complaint to law enforcement for accidental, good faith violations of this policy. We consider activities conducted consistent with this policy to constitute “authorized” conduct under the Computer Fraud and Abuse Act (CFAA). We will not bring a DMCA claim against you for circumventing the technological measures we have used to protect the applications in scope.\n\nIf legal action is initiated by a third party against you and you have complied with Zomato's bug bounty policy, Zomato will take steps to make it known that your actions were conducted in compliance with this policy.\n\nPlease submit a [HackerOne report](https://hackerone.com/zomato) to us before engaging in conduct that may be inconsistent with or unaddressed by this policy.\n\nThank you for helping keep @Zomato safe for the community!\nZomato Security Team\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-01-29T11:33:23.004Z"},{"id":3745642,"new_policy":"We take security seriously at Zomato, and we’re committed to protecting our community. If you are a security researcher or expert and believe you’ve identified security-related issues with Zomato’s website or apps, we would appreciate you disclosing it to us responsibly. \n\nOur team is committed to addressing all security issues in a responsible and timely manner, and we ask the security community to give us the opportunity to do so before disclosing them publicly. Please submit a detailed description of the issue to us, along with the steps to reproduce it. We trust the security community to make every effort to protect our users’ data and privacy. \n\n# Disclosure Policy\n* Let us know as soon as possible upon discovery of a potential security issue, and we'll make every effort to quickly resolve the issue.\n* Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party.\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\n# Test Plan\nPlease include a header `X-Hackerone: \u003ch1_username\u003e` when you test so we can identify your requests easily.\n\n# Scope\nThe scope of issues is limited to technical vulnerabilities in the Zomato website or mobile apps. Please do not attempt to compromise the safety or privacy of our users (so please use test accounts), or the availability of Zomato through DoS attacks or spam. We also request you not to use vulnerability testing tools that generate a significant volume of traffic.\n\nCertain vulnerabilities with a working proof of concept on some of our Android mobile app(s) may qualify for an additional bounty through the [Google Play Security Rewards Program] (https://hackerone.com/googleplay). To see which apps and vulnerabilities may qualify for a bounty, please refer to the [Google Play Security Rewards Program’s Scope and Vulnerability Criteria] (https://hackerone.com/googleplay).\n\n# Rewards\nWe will reward reports according to the severity of their impact on a case-by-case basis as determined by our security team. We may pay more for unique, hard-to-find bugs; we may also pay less for bugs with complex prerequisites that lower the risk of exploitation. \n\nBelow, you can find examples of vulnerabilities and their impacts grouped by our severity ranking. This is not an exhaustive list and it is designed to give you insight on how we rate vulnerabilities. \n\n# Critical \n* Remote Code Execution (RCE) - able to execute arbitrary commands on a remote device\n* SQL Injection - able to read Personally Identifiable Information (PII) or other sensitive data / full read/write access to a database\n* Server-Side Request Forgery (SSRF) - able to pivot to internal application and/or access credentials (not blind)\n* Information Disclosure - mass PII leaks including data such as names, emails, phone numbers and addresses (Combined) \n\n# High \n* Stored Cross-Site Scripting (XSS) - stored XSS with access to non HttpOnly cookies\n* Information Disclosure - leaked credentials\n* Subdomain Takeover - on a domain that sees heavy traffic or would be a convincing candidate for a phishing attack\n* Cross-Site Request Forgery (CSRF) - leading to account takeover\n* Account Takeover (ATO) - with no or minimal user interaction\n* Insecure Direct Object Reference (IDOR) - read or write access to sensitive data or important fields that you do not have permission to\n* SQL Injection - able to perform queries with a limited access user\n\n# Medium \n* CSRF - able to modify important information (authenticated) \n* ATO - required user interaction\n* IDOR - write access to modify objects that you do not have permission to\n* XSS - reflected/DOM XSS with access to cookies\n\n# Low \n* Directory listings \n* XSS - POST based XSS (with CSRF bypass)\n* Lack of HTTPS on dynamic pages (judged on a case-by-case basis)\n* Server information page (no credentials)\n* Subdomain Takeover - on an unused subdomain\n\n# Eligibility and Responsible Disclosure\nTo promote the discovery and reporting of vulnerabilities and increase user safety, we ask that you:\n* Give us a reasonable time to respond to the issue before making any information about it public.\n* Not access or modify data without the explicit permission of the owner.\n* Act in good faith not to degrade the performance of our services (including denial of service).\n \nWe only reward the first reporter of a vulnerability. Public disclosure of the vulnerability prior to resolution will result in disqualification from the program. You must report a qualifying vulnerability through the HackerOne reporting tool to be eligible for a monetary reward.\n\n# Non-qualifying vulnerabilities / Known Issues\n\nWhen reporting vulnerabilities, please consider (1) attack scenario/exploitability, and (2) the security impact of the bug. The following issues are considered out of scope:\n \n##Informative Bugs\n* Broken Link Hijacking issues are categorized as low severity and are not eligible for rewards.\n* Credential leakage reports are considered informational if two-factor authentication (2FA) is in place\n* Security issues related to Zomato Legends are considered informational and are not eligible for rewards, regardless of whether the issue is resolved by the team\n\n\n## Not Applicable  \u0026 Out of Scope Bugs\n\n* Google Maps API Keys Leakage\n* HTML Injection \u0026 Context Spoofing(Closed as NA) \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 brute force issues\n* Invalidation/expiry on CDN assets\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 implication can be demonstrated \n* Self XSS\n* Promo code abuse (e.g. ordering multiple times using the same promo code)\n* We're aware of Promotion offers/Cash backs Issues (e.g: logic issues in cash back reversing/applying) \n* Abuse of our promotional offers and referral codes\n* CSRF on www.zomato.com/php/* and www.zomato.com/clients*/\n* Promo code enumeration, abuse of our promotional offers and referral codes.\n* Able to retrieve user's public information.\n* Username / email enumeration\n\n# Consequences of complying with this policy\n\nWe will not pursue a civil action or initiate a complaint to law enforcement for accidental, good faith violations of this policy. We consider activities conducted consistent with this policy to constitute “authorized” conduct under the Computer Fraud and Abuse Act (CFAA). We will not bring a DMCA claim against you for circumventing the technological measures we have used to protect the applications in scope.\n\nIf legal action is initiated by a third party against you and you have complied with Zomato's bug bounty policy, Zomato will take steps to make it known that your actions were conducted in compliance with this policy.\n\nPlease submit a [HackerOne report](https://hackerone.com/zomato) to us before engaging in conduct that may be inconsistent with or unaddressed by this policy.\n\nThank you for helping keep @Zomato safe for the community!\nZomato Security Team\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":"2024-12-03T06:57:43.609Z"},{"id":3743071,"new_policy":"We take security seriously at Zomato, and we’re committed to protecting our community. If you are a security researcher or expert and believe you’ve identified security-related issues with Zomato’s website or apps, we would appreciate you disclosing it to us responsibly. \n\nOur team is committed to addressing all security issues in a responsible and timely manner, and we ask the security community to give us the opportunity to do so before disclosing them publicly. Please submit a detailed description of the issue to us, along with the steps to reproduce it. We trust the security community to make every effort to protect our users’ data and privacy. \n\n# Disclosure Policy\n* Let us know as soon as possible upon discovery of a potential security issue, and we'll make every effort to quickly resolve the issue.\n* Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party.\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\n# Test Plan\nPlease include a header `X-Hackerone: \u003ch1_username\u003e` when you test so we can identify your requests easily.\n\n# Scope\nThe scope of issues is limited to technical vulnerabilities in the Zomato website or mobile apps. Please do not attempt to compromise the safety or privacy of our users (so please use test accounts), or the availability of Zomato through DoS attacks or spam. We also request you not to use vulnerability testing tools that generate a significant volume of traffic.\n\nCertain vulnerabilities with a working proof of concept on some of our Android mobile app(s) may qualify for an additional bounty through the [Google Play Security Rewards Program] (https://hackerone.com/googleplay). To see which apps and vulnerabilities may qualify for a bounty, please refer to the [Google Play Security Rewards Program’s Scope and Vulnerability Criteria] (https://hackerone.com/googleplay).\n\n# Rewards\nWe will reward reports according to the severity of their impact on a case-by-case basis as determined by our security team. We may pay more for unique, hard-to-find bugs; we may also pay less for bugs with complex prerequisites that lower the risk of exploitation. \n\nBelow, you can find examples of vulnerabilities and their impacts grouped by our severity ranking. This is not an exhaustive list and it is designed to give you insight on how we rate vulnerabilities. \n\n# Critical \n* Remote Code Execution (RCE) - able to execute arbitrary commands on a remote device\n* SQL Injection - able to read Personally Identifiable Information (PII) or other sensitive data / full read/write access to a database\n* Server-Side Request Forgery (SSRF) - able to pivot to internal application and/or access credentials (not blind)\n* Information Disclosure - mass PII leaks including data such as names, emails, phone numbers and addresses (Combined) \n\n# High \n* Stored Cross-Site Scripting (XSS) - stored XSS with access to non HttpOnly cookies\n* Information Disclosure - leaked credentials\n* Subdomain Takeover - on a domain that sees heavy traffic or would be a convincing candidate for a phishing attack\n* Cross-Site Request Forgery (CSRF) - leading to account takeover\n* Account Takeover (ATO) - with no or minimal user interaction\n* Insecure Direct Object Reference (IDOR) - read or write access to sensitive data or important fields that you do not have permission to\n* SQL Injection - able to perform queries with a limited access user\n\n# Medium \n* CSRF - able to modify important information (authenticated) \n* ATO - required user interaction\n* IDOR - write access to modify objects that you do not have permission to\n* XSS - reflected/DOM XSS with access to cookies\n\n# Low \n* Directory listings \n* XSS - POST based XSS (with CSRF bypass)\n* Lack of HTTPS on dynamic pages (judged on a case-by-case basis)\n* Server information page (no credentials)\n* Subdomain Takeover - on an unused subdomain\n\n# Eligibility and Responsible Disclosure\nTo promote the discovery and reporting of vulnerabilities and increase user safety, we ask that you:\n* Give us a reasonable time to respond to the issue before making any information about it public.\n* Not access or modify data without the explicit permission of the owner.\n* Act in good faith not to degrade the performance of our services (including denial of service).\n \nWe only reward the first reporter of a vulnerability. Public disclosure of the vulnerability prior to resolution will result in disqualification from the program. You must report a qualifying vulnerability through the HackerOne reporting tool to be eligible for a monetary reward.\n\n# Non-qualifying vulnerabilities / Known Issues\n\nWhen reporting vulnerabilities, please consider (1) attack scenario/exploitability, and (2) the security impact of the bug. The following issues are considered out of scope:\n \n##Informative Bugs\n* Broken Link Hijacking issues are categorized as low severity and are not eligible for rewards.\n* Credential leakage reports are considered informational if two-factor authentication (2FA) is in place\n* Security issues related to Zomato Legends are considered informational and are not eligible for rewards, regardless of whether the issue is resolved by the team\n\n\n## Not Applicable  \u0026 Out of Scope Bugs\n\n* Google Maps API Keys Leakage\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 brute force issues\n* Invalidation/expiry on CDN assets\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 implication can be demonstrated \n* Self XSS\n* Promo code abuse (e.g. ordering multiple times using the same promo code)\n* We're aware of Promotion offers/Cash backs Issues (e.g: logic issues in cash back reversing/applying) \n* Abuse of our promotional offers and referral codes\n* CSRF on www.zomato.com/php/* and www.zomato.com/clients*/\n* Promo code enumeration, abuse of our promotional offers and referral codes.\n* Able to retrieve user's public information.\n* Username / email enumeration\n\n# Consequences of complying with this policy\n\nWe will not pursue a civil action or initiate a complaint to law enforcement for accidental, good faith violations of this policy. We consider activities conducted consistent with this policy to constitute “authorized” conduct under the Computer Fraud and Abuse Act (CFAA). We will not bring a DMCA claim against you for circumventing the technological measures we have used to protect the applications in scope.\n\nIf legal action is initiated by a third party against you and you have complied with Zomato's bug bounty policy, Zomato will take steps to make it known that your actions were conducted in compliance with this policy.\n\nPlease submit a [HackerOne report](https://hackerone.com/zomato) to us before engaging in conduct that may be inconsistent with or unaddressed by this policy.\n\nThank you for helping keep @Zomato safe for the community!\nZomato Security Team\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":"2024-10-28T06:00:41.075Z"},{"id":3737147,"new_policy":"We take security seriously at Zomato, and we’re committed to protecting our community. If you are a security researcher or expert and believe you’ve identified security-related issues with Zomato’s website or apps, we would appreciate you disclosing it to us responsibly. \n\nOur team is committed to addressing all security issues in a responsible and timely manner, and we ask the security community to give us the opportunity to do so before disclosing them publicly. Please submit a detailed description of the issue to us, along with the steps to reproduce it. We trust the security community to make every effort to protect our users’ data and privacy. \n\n# Disclosure Policy\n* Let us know as soon as possible upon discovery of a potential security issue, and we'll make every effort to quickly resolve the issue.\n* Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party.\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\n# Test Plan\nPlease include a header `X-Hackerone: \u003ch1_username\u003e` when you test so we can identify your requests easily.\n\n# Scope\nThe scope of issues is limited to technical vulnerabilities in the Zomato website or mobile apps. Please do not attempt to compromise the safety or privacy of our users (so please use test accounts), or the availability of Zomato through DoS attacks or spam. We also request you not to use vulnerability testing tools that generate a significant volume of traffic.\n\nCertain vulnerabilities with a working proof of concept on some of our Android mobile app(s) may qualify for an additional bounty through the [Google Play Security Rewards Program] (https://hackerone.com/googleplay). To see which apps and vulnerabilities may qualify for a bounty, please refer to the [Google Play Security Rewards Program’s Scope and Vulnerability Criteria] (https://hackerone.com/googleplay).\n\n# Rewards\nWe will reward reports according to the severity of their impact on a case-by-case basis as determined by our security team. We may pay more for unique, hard-to-find bugs; we may also pay less for bugs with complex prerequisites that lower the risk of exploitation. \n\nBelow, you can find examples of vulnerabilities and their impacts grouped by our severity ranking. This is not an exhaustive list and it is designed to give you insight on how we rate vulnerabilities. \n\n# Critical \n* Remote Code Execution (RCE) - able to execute arbitrary commands on a remote device\n* SQL Injection - able to read Personally Identifiable Information (PII) or other sensitive data / full read/write access to a database\n* Server-Side Request Forgery (SSRF) - able to pivot to internal application and/or access credentials (not blind)\n* Information Disclosure - mass PII leaks including data such as names, emails, phone numbers and addresses (Combined) \n\n# High \n* Stored Cross-Site Scripting (XSS) - stored XSS with access to non HttpOnly cookies\n* Information Disclosure - leaked credentials\n* Subdomain Takeover - on a domain that sees heavy traffic or would be a convincing candidate for a phishing attack\n* Cross-Site Request Forgery (CSRF) - leading to account takeover\n* Account Takeover (ATO) - with no or minimal user interaction\n* Insecure Direct Object Reference (IDOR) - read or write access to sensitive data or important fields that you do not have permission to\n* SQL Injection - able to perform queries with a limited access user\n\n# Medium \n* CSRF - able to modify important information (authenticated) \n* ATO - required user interaction\n* IDOR - write access to modify objects that you do not have permission to\n* XSS - reflected/DOM XSS with access to cookies\n\n# Low \n* Directory listings \n* XSS - POST based XSS (with CSRF bypass)\n* Lack of HTTPS on dynamic pages (judged on a case-by-case basis)\n* Server information page (no credentials)\n* Subdomain Takeover - on an unused subdomain\n\n# Eligibility and Responsible Disclosure\nTo promote the discovery and reporting of vulnerabilities and increase user safety, we ask that you:\n* Give us a reasonable time to respond to the issue before making any information about it public.\n* Not access or modify data without the explicit permission of the owner.\n* Act in good faith not to degrade the performance of our services (including denial of service).\n \nWe only reward the first reporter of a vulnerability. Public disclosure of the vulnerability prior to resolution will result in disqualification from the program. You must report a qualifying vulnerability through the HackerOne reporting tool to be eligible for a monetary reward.\n\n# Non-qualifying vulnerabilities / Known Issues\n\nWhen reporting vulnerabilities, please consider (1) attack scenario/exploitability, and (2) the security impact of the bug. The following issues are considered out of scope:\n \n##Informative Bugs\n* Broken Link Hijacking issues are categorized as low severity and are not eligible for rewards.\n* Credential leakage reports are considered informational if two-factor authentication (2FA) is in place\n* Security issues related to Zomato Legends are considered informational and are not eligible for rewards, regardless of whether the issue is resolved by the team\n\n\n## Not Applicable  \u0026 Out of Scope Bugs\n\n* Google Maps API Keys Leakage\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 brute force issues\n* Invalidation/expiry on CDN assets\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 implication can be demonstrated \n* Self XSS\n* Promo code abuse (e.g. ordering multiple times using the same promo code)\n* Abuse of our promotional offers and referral codes\n* CSRF on www.zomato.com/php/* and www.zomato.com/clients*/\n* Promo code enumeration, abuse of our promotional offers and referral codes.\n* Able to retrieve user's public information.\n* Username / email enumeration\n\n# Consequences of complying with this policy\n\nWe will not pursue a civil action or initiate a complaint to law enforcement for accidental, good faith violations of this policy. We consider activities conducted consistent with this policy to constitute “authorized” conduct under the Computer Fraud and Abuse Act (CFAA). We will not bring a DMCA claim against you for circumventing the technological measures we have used to protect the applications in scope.\n\nIf legal action is initiated by a third party against you and you have complied with Zomato's bug bounty policy, Zomato will take steps to make it known that your actions were conducted in compliance with this policy.\n\nPlease submit a [HackerOne report](https://hackerone.com/zomato) to us before engaging in conduct that may be inconsistent with or unaddressed by this policy.\n\nThank you for helping keep @Zomato safe for the community!\nZomato Security Team\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":"2024-08-27T04:07:38.570Z"},{"id":3713359,"new_policy":"We take security seriously at Zomato, and we’re committed to protecting our community. If you are a security researcher or expert and believe you’ve identified security-related issues with Zomato’s website or apps, we would appreciate you disclosing it to us responsibly. \n\nOur team is committed to addressing all security issues in a responsible and timely manner, and we ask the security community to give us the opportunity to do so before disclosing them publicly. Please submit a detailed description of the issue to us, along with the steps to reproduce it. We trust the security community to make every effort to protect our users’ data and privacy. \n\n# Disclosure Policy\n* Let us know as soon as possible upon discovery of a potential security issue, and we'll make every effort to quickly resolve the issue.\n* Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party.\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\n# Test Plan\nPlease include a header `X-Hackerone: \u003ch1_username\u003e` when you test so we can identify your requests easily.\n\n# Scope\nThe scope of issues is limited to technical vulnerabilities in the Zomato website or mobile apps. Please do not attempt to compromise the safety or privacy of our users (so please use test accounts), or the availability of Zomato through DoS attacks or spam. We also request you not to use vulnerability testing tools that generate a significant volume of traffic.\n\nCertain vulnerabilities with a working proof of concept on some of our Android mobile app(s) may qualify for an additional bounty through the [Google Play Security Rewards Program] (https://hackerone.com/googleplay). To see which apps and vulnerabilities may qualify for a bounty, please refer to the [Google Play Security Rewards Program’s Scope and Vulnerability Criteria] (https://hackerone.com/googleplay).\n\n# Rewards\nWe will reward reports according to the severity of their impact on a case-by-case basis as determined by our security team. We may pay more for unique, hard-to-find bugs; we may also pay less for bugs with complex prerequisites that lower the risk of exploitation. \n\nBelow, you can find examples of vulnerabilities and their impacts grouped by our severity ranking. This is not an exhaustive list and it is designed to give you insight on how we rate vulnerabilities. \n\n# Critical \n* Remote Code Execution (RCE) - able to execute arbitrary commands on a remote device\n* SQL Injection - able to read Personally Identifiable Information (PII) or other sensitive data / full read/write access to a database\n* Server-Side Request Forgery (SSRF) - able to pivot to internal application and/or access credentials (not blind)\n* Information Disclosure - mass PII leaks including data such as names, emails, phone numbers and addresses\n\n# High \n* Stored Cross-Site Scripting (XSS) - stored XSS with access to non HttpOnly cookies\n* Information Disclosure - leaked credentials\n* Subdomain Takeover - on a domain that sees heavy traffic or would be a convincing candidate for a phishing attack\n* Cross-Site Request Forgery (CSRF) - leading to account takeover\n* Account Takeover (ATO) - with no or minimal user interaction\n* Insecure Direct Object Reference (IDOR) - read or write access to sensitive data or important fields that you do not have permission to\n* SQL Injection - able to perform queries with a limited access user\n\n# Medium \n* CSRF - able to modify important information (authenticated) \n* ATO - required user interaction\n* IDOR - write access to modify objects that you do not have permission to\n* XSS - reflected/DOM XSS with access to cookies\n\n# Low \n* Directory listings \n* XSS - POST based XSS (with CSRF bypass)\n* Lack of HTTPS on dynamic pages (judged on a case-by-case basis)\n* Server information page (no credentials)\n* Subdomain Takeover - on an unused subdomain\n\n# Eligibility and Responsible Disclosure\nTo promote the discovery and reporting of vulnerabilities and increase user safety, we ask that you:\n* Give us a reasonable time to respond to the issue before making any information about it public.\n* Not access or modify data without the explicit permission of the owner.\n* Act in good faith not to degrade the performance of our services (including denial of service).\n \nWe only reward the first reporter of a vulnerability. Public disclosure of the vulnerability prior to resolution will result in disqualification from the program. You must report a qualifying vulnerability through the HackerOne reporting tool to be eligible for a monetary reward.\n\n# Non-qualifying vulnerabilities / Known Issues\n\nWhen reporting vulnerabilities, please consider (1) attack scenario/exploitability, and (2) the security impact of the bug. The following issues are considered out of scope:\n \n* Broken Link Hijacking issues are categorized as low severity and are not eligible for rewards.\n* Google Maps API Keys Leakage\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 brute force issues\n* Invalidation/expiry on CDN assets\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 implication can be demonstrated \n* Self XSS\n* Promo code abuse (e.g. ordering multiple times using the same promo code)\n* Abuse of our promotional offers and referral codes\n* CSRF on www.zomato.com/php/* and www.zomato.com/clients*/\n* Promo code enumeration, abuse of our promotional offers and referral codes.\n* Able to retrieve user's public information.\n* Username / email enumeration\n\n# Consequences of complying with this policy\n\nWe will not pursue a civil action or initiate a complaint to law enforcement for accidental, good faith violations of this policy. We consider activities conducted consistent with this policy to constitute “authorized” conduct under the Computer Fraud and Abuse Act (CFAA). We will not bring a DMCA claim against you for circumventing the technological measures we have used to protect the applications in scope.\n\nIf legal action is initiated by a third party against you and you have complied with Zomato's bug bounty policy, Zomato will take steps to make it known that your actions were conducted in compliance with this policy.\n\nPlease submit a [HackerOne report](https://hackerone.com/zomato) to us before engaging in conduct that may be inconsistent with or unaddressed by this policy.\n\nThank you for helping keep @Zomato safe for the community!\nZomato Security Team\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":"2024-02-28T12:08:20.151Z"},{"id":3706902,"new_policy":"We take security seriously at Zomato, and we’re committed to protecting our community. If you are a security researcher or expert and believe you’ve identified security-related issues with Zomato’s website or apps, we would appreciate you disclosing it to us responsibly. \n\nOur team is committed to addressing all security issues in a responsible and timely manner, and we ask the security community to give us the opportunity to do so before disclosing them publicly. Please submit a detailed description of the issue to us, along with the steps to reproduce it. We trust the security community to make every effort to protect our users’ data and privacy. \n\n# Disclosure Policy\n* Let us know as soon as possible upon discovery of a potential security issue, and we'll make every effort to quickly resolve the issue.\n* Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party.\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\n# Test Plan\nPlease include a header `X-Hackerone: \u003ch1_username\u003e` when you test so we can identify your requests easily.\n\n# Scope\nThe scope of issues is limited to technical vulnerabilities in the Zomato website or mobile apps. Please do not attempt to compromise the safety or privacy of our users (so please use test accounts), or the availability of Zomato through DoS attacks or spam. We also request you not to use vulnerability testing tools that generate a significant volume of traffic.\n\nCertain vulnerabilities with a working proof of concept on some of our Android mobile app(s) may qualify for an additional bounty through the [Google Play Security Rewards Program] (https://hackerone.com/googleplay). To see which apps and vulnerabilities may qualify for a bounty, please refer to the [Google Play Security Rewards Program’s Scope and Vulnerability Criteria] (https://hackerone.com/googleplay).\n\n# Rewards\nWe will reward reports according to the severity of their impact on a case-by-case basis as determined by our security team. We may pay more for unique, hard-to-find bugs; we may also pay less for bugs with complex prerequisites that lower the risk of exploitation. \n\nBelow, you can find examples of vulnerabilities and their impacts grouped by our severity ranking. This is not an exhaustive list and it is designed to give you insight on how we rate vulnerabilities. \n\n# Critical \n* Remote Code Execution (RCE) - able to execute arbitrary commands on a remote device\n* SQL Injection - able to read Personally Identifiable Information (PII) or other sensitive data / full read/write access to a database\n* Server-Side Request Forgery (SSRF) - able to pivot to internal application and/or access credentials (not blind)\n* Information Disclosure - mass PII leaks including data such as names, emails, phone numbers and addresses\n\n# High \n* Stored Cross-Site Scripting (XSS) - stored XSS with access to non HttpOnly cookies\n* Information Disclosure - leaked credentials\n* Subdomain Takeover - on a domain that sees heavy traffic or would be a convincing candidate for a phishing attack\n* Cross-Site Request Forgery (CSRF) - leading to account takeover\n* Account Takeover (ATO) - with no or minimal user interaction\n* Insecure Direct Object Reference (IDOR) - read or write access to sensitive data or important fields that you do not have permission to\n* SQL Injection - able to perform queries with a limited access user\n\n# Medium \n* CSRF - able to modify important information (authenticated) \n* ATO - required user interaction\n* IDOR - write access to modify objects that you do not have permission to\n* XSS - reflected/DOM XSS with access to cookies\n\n# Low \n* Directory listings \n* XSS - POST based XSS (with CSRF bypass)\n* Lack of HTTPS on dynamic pages (judged on a case-by-case basis)\n* Server information page (no credentials)\n* Subdomain Takeover - on an unused subdomain\n\n# Eligibility and Responsible Disclosure\nTo promote the discovery and reporting of vulnerabilities and increase user safety, we ask that you:\n* Give us a reasonable time to respond to the issue before making any information about it public.\n* Not access or modify data without the explicit permission of the owner.\n* Act in good faith not to degrade the performance of our services (including denial of service).\n \nWe only reward the first reporter of a vulnerability. Public disclosure of the vulnerability prior to resolution will result in disqualification from the program. You must report a qualifying vulnerability through the HackerOne reporting tool to be eligible for a monetary reward.\n\n# Non-qualifying vulnerabilities / Known Issues\n\nWhen reporting vulnerabilities, please consider (1) attack scenario/exploitability, and (2) the security impact of the bug. The following issues are considered out of scope:\n \n* Google Maps API Keys Leakage\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 brute force issues\n* Invalidation/expiry on CDN assets\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 implication can be demonstrated \n* Self XSS\n* Promo code abuse (e.g. ordering multiple times using the same promo code)\n* Abuse of our promotional offers and referral codes\n* CSRF on www.zomato.com/php/* and www.zomato.com/clients*/\n* Promo code enumeration, abuse of our promotional offers and referral codes.\n* Able to retrieve user's public information.\n* Username / email enumeration\n\n# Consequences of complying with this policy\n\nWe will not pursue a civil action or initiate a complaint to law enforcement for accidental, good faith violations of this policy. We consider activities conducted consistent with this policy to constitute “authorized” conduct under the Computer Fraud and Abuse Act (CFAA). We will not bring a DMCA claim against you for circumventing the technological measures we have used to protect the applications in scope.\n\nIf legal action is initiated by a third party against you and you have complied with Zomato's bug bounty policy, Zomato will take steps to make it known that your actions were conducted in compliance with this policy.\n\nPlease submit a [HackerOne report](https://hackerone.com/zomato) to us before engaging in conduct that may be inconsistent with or unaddressed by this policy.\n\nThank you for helping keep @Zomato safe for the community!\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-10T05:36:18.325Z"},{"id":3667748,"new_policy":"We take security seriously at Zomato, and we’re committed to protecting our community. If you are a security researcher or expert and believe you’ve identified security-related issues with Zomato’s website or apps, we would appreciate you disclosing it to us responsibly. \n\nOur team is committed to addressing all security issues in a responsible and timely manner, and we ask the security community to give us the opportunity to do so before disclosing them publicly. Please submit a detailed description of the issue to us, along with the steps to reproduce it. We trust the security community to make every effort to protect our users’ data and privacy. \n\n# Disclosure Policy\n* Let us know as soon as possible upon discovery of a potential security issue, and we'll make every effort to quickly resolve the issue.\n* Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party.\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\n# Test Plan\nPlease include a header `X-Hackerone: \u003ch1_username\u003e` when you test so we can identify your requests easily.\n\n# Scope\nThe scope of issues is limited to technical vulnerabilities in the Zomato website or mobile apps. Please do not attempt to compromise the safety or privacy of our users (so please use test accounts), or the availability of Zomato through DoS attacks or spam. We also request you not to use vulnerability testing tools that generate a significant volume of traffic.\n\nCertain vulnerabilities with a working proof of concept on some of our Android mobile app(s) may qualify for an additional bounty through the [Google Play Security Rewards Program] (https://hackerone.com/googleplay). To see which apps and vulnerabilities may qualify for a bounty, please refer to the [Google Play Security Rewards Program’s Scope and Vulnerability Criteria] (https://hackerone.com/googleplay).\n\n# Rewards\nWe will reward reports according to the severity of their impact on a case-by-case basis as determined by our security team. We may pay more for unique, hard-to-find bugs; we may also pay less for bugs with complex prerequisites that lower the risk of exploitation. \n\nBelow, you can find examples of vulnerabilities and their impacts grouped by our severity ranking. This is not an exhaustive list and it is designed to give you insight on how we rate vulnerabilities. \n\n# Critical \n* Remote Code Execution (RCE) - able to execute arbitrary commands on a remote device\n* SQL Injection - able to read Personally Identifiable Information (PII) or other sensitive data / full read/write access to a database\n* Server-Side Request Forgery (SSRF) - able to pivot to internal application and/or access credentials (not blind)\n* Information Disclosure - mass PII leaks including data such as names, emails, phone numbers and addresses\n\n# High \n* Stored Cross-Site Scripting (XSS) - stored XSS with access to non HttpOnly cookies\n* Information Disclosure - leaked credentials\n* Subdomain Takeover - on a domain that sees heavy traffic or would be a convincing candidate for a phishing attack\n* Cross-Site Request Forgery (CSRF) - leading to account takeover\n* Account Takeover (ATO) - with no or minimal user interaction\n* Insecure Direct Object Reference (IDOR) - read or write access to sensitive data or important fields that you do not have permission to\n* SQL Injection - able to perform queries with a limited access user\n\n# Medium \n* CSRF - able to modify important information (authenticated) \n* ATO - required user interaction\n* IDOR - write access to modify objects that you do not have permission to\n* XSS - reflected/DOM XSS with access to cookies\n\n# Low \n* Directory listings \n* XSS - POST based XSS (with CSRF bypass)\n* Lack of HTTPS on dynamic pages (judged on a case-by-case basis)\n* Server information page (no credentials)\n* Subdomain Takeover - on an unused subdomain\n\n# Eligibility and Responsible Disclosure\nTo promote the discovery and reporting of vulnerabilities and increase user safety, we ask that you:\n* Give us a reasonable time to respond to the issue before making any information about it public.\n* Not access or modify data without the explicit permission of the owner.\n* Act in good faith not to degrade the performance of our services (including denial of service).\n \nWe only reward the first reporter of a vulnerability. Public disclosure of the vulnerability prior to resolution will result in disqualification from the program. You must report a qualifying vulnerability through the HackerOne reporting tool to be eligible for a monetary reward.\n\n# Non-qualifying vulnerabilities / Known Issues\n\nWhen reporting vulnerabilities, please consider (1) attack scenario/exploitability, and (2) the security impact of the bug. The following issues are considered out of scope:\n \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 brute force issues\n* Invalidation/expiry on CDN assets\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 implication can be demonstrated \n* Self XSS\n* Promo code abuse (e.g. ordering multiple times using the same promo code)\n* Abuse of our promotional offers and referral codes\n* CSRF on www.zomato.com/php/* and www.zomato.com/clients*/\n* Promo code enumeration, abuse of our promotional offers and referral codes.\n* Able to retrieve user's public information.\n* Username / email enumeration\n\n# Consequences of complying with this policy\n\nWe will not pursue a civil action or initiate a complaint to law enforcement for accidental, good faith violations of this policy. We consider activities conducted consistent with this policy to constitute “authorized” conduct under the Computer Fraud and Abuse Act (CFAA). We will not bring a DMCA claim against you for circumventing the technological measures we have used to protect the applications in scope.\n\nIf legal action is initiated by a third party against you and you have complied with Zomato's bug bounty policy, Zomato will take steps to make it known that your actions were conducted in compliance with this policy.\n\nPlease submit a [HackerOne report](https://hackerone.com/zomato) to us before engaging in conduct that may be inconsistent with or unaddressed by this policy.\n\nThank you for helping keep @Zomato safe for the community!\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":"2022-03-08T10:52:21.344Z"},{"id":3653096,"new_policy":"We take security seriously at Zomato, and we’re committed to protecting our community. If you are a security researcher or expert and believe you’ve identified security-related issues with Zomato’s website or apps, we would appreciate you disclosing it to us responsibly. \n\nOur team is committed to addressing all security issues in a responsible and timely manner, and we ask the security community to give us the opportunity to do so before disclosing them publicly. Please submit a detailed description of the issue to us, along with the steps to reproduce it. We trust the security community to make every effort to protect our users’ data and privacy. \n\n# Disclosure Policy\n* Let us know as soon as possible upon discovery of a potential security issue, and we'll make every effort to quickly resolve the issue.\n* Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party.\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\n# Test Plan\nPlease include a header `X-Hackerone: \u003ch1_username\u003e` when you test so we can identify your requests easily.\n\n# Scope\nThe scope of issues is limited to technical vulnerabilities in the Zomato website or mobile apps. Please do not attempt to compromise the safety or privacy of our users (so please use test accounts), or the availability of Zomato through DoS attacks or spam. We also request you not to use vulnerability testing tools that generate a significant volume of traffic.\n\nCertain vulnerabilities with a working proof of concept on some of our Android mobile app(s) may qualify for an additional bounty through the [Google Play Security Rewards Program] (https://hackerone.com/googleplay). To see which apps and vulnerabilities may qualify for a bounty, please refer to the [Google Play Security Rewards Program’s Scope and Vulnerability Criteria] (https://hackerone.com/googleplay).\n\n# Rewards\nWe will reward reports according to the severity of their impact on a case-by-case basis as determined by our security team. We may pay more for unique, hard-to-find bugs; we may also pay less for bugs with complex prerequisites that lower the risk of exploitation. \n\nBelow, you can find examples of vulnerabilities and their impacts grouped by our severity ranking. This is not an exhaustive list and it is designed to give you insight on how we rate vulnerabilities. \n\n# Critical \n* Remote Code Execution (RCE) - able to execute arbitrary commands on a remote device\n* SQL Injection - able to read Personally Identifiable Information (PII) or other sensitive data / full read/write access to a database\n* Server-Side Request Forgery (SSRF) - able to pivot to internal application and/or access credentials (not blind)\n* Information Disclosure - mass PII leaks including data such as names, emails, phone numbers and addresses\n\n# High \n* Stored Cross-Site Scripting (XSS) - stored XSS with access to non HttpOnly cookies\n* Information Disclosure - leaked credentials\n* Subdomain Takeover - on a domain that sees heavy traffic or would be a convincing candidate for a phishing attack\n* Cross-Site Request Forgery (CSRF) - leading to account takeover\n* Account Takeover (ATO) - with no or minimal user interaction\n* Insecure Direct Object Reference (IDOR) - read or write access to sensitive data or important fields that you do not have permission to\n* SQL Injection - able to perform queries with a limited access user\n\n# Medium \n* CSRF - able to modify important information (authenticated) \n* ATO - required user interaction\n* IDOR - write access to modify objects that you do not have permission to\n* XSS - reflected/DOM XSS with access to cookies\n\n# Low \n* Directory listings \n* XSS - POST based XSS (with CSRF bypass)\n* Lack of HTTPS on dynamic pages (judged on a case-by-case basis)\n* Server information page (no credentials)\n* Subdomain Takeover - on an unused subdomain\n\n# Eligibility and Responsible Disclosure\nTo promote the discovery and reporting of vulnerabilities and increase user safety, we ask that you:\n* Give us a reasonable time to respond to the issue before making any information about it public.\n* Not access or modify data without the explicit permission of the owner.\n* Act in good faith not to degrade the performance of our services (including denial of service).\n \nWe only reward the first reporter of a vulnerability. Public disclosure of the vulnerability prior to resolution will result in disqualification from the program. You must report a qualifying vulnerability through the HackerOne reporting tool to be eligible for a monetary reward.\n\n# Non-qualifying vulnerabilities / Known Issues\n\nWhen reporting vulnerabilities, please consider (1) attack scenario/exploitability, and (2) the security impact of the bug. The following issues are considered out of scope:\n \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 brute force 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 implication can be demonstrated \n* Self XSS\n* Promo code abuse (e.g. ordering multiple times using the same promo code)\n* Abuse of our promotional offers and referral codes\n* CSRF on www.zomato.com/php/* and www.zomato.com/clients*/\n* Promo code enumeration, abuse of our promotional offers and referral codes.\n* Able to retrieve user's public information.\n* Username / email enumeration\n\n# Consequences of complying with this policy\n\nWe will not pursue a civil action or initiate a complaint to law enforcement for accidental, good faith violations of this policy. We consider activities conducted consistent with this policy to constitute “authorized” conduct under the Computer Fraud and Abuse Act (CFAA). We will not bring a DMCA claim against you for circumventing the technological measures we have used to protect the applications in scope.\n\nIf legal action is initiated by a third party against you and you have complied with Zomato's bug bounty policy, Zomato will take steps to make it known that your actions were conducted in compliance with this policy.\n\nPlease submit a [HackerOne report](https://hackerone.com/zomato) to us before engaging in conduct that may be inconsistent with or unaddressed by this policy.\n\nThank you for helping keep @Zomato safe for the community!\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":"2021-06-07T09:22:07.022Z"},{"id":3649938,"new_policy":"We take security seriously at Zomato, and we’re committed to protecting our community. If you are a security researcher or expert and believe you’ve identified security-related issues with Zomato’s website or apps, we would appreciate you disclosing it to us responsibly. \n\nOur team is committed to addressing all security issues in a responsible and timely manner, and we ask the security community to give us the opportunity to do so before disclosing them publicly. Please submit a detailed description of the issue to us, along with the steps to reproduce it. We trust the security community to make every effort to protect our users’ data and privacy. \n\n# Disclosure Policy\n* Let us know as soon as possible upon discovery of a potential security issue, and we'll make every effort to quickly resolve the issue.\n* Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party.\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\n# Test Plan\nPlease include a header `X-Hackerone: \u003ch1_username\u003e` when you test so we can identify your requests easily.\n\n# Scope\nThe scope of issues is limited to technical vulnerabilities in the Zomato website or mobile apps. Please do not attempt to compromise the safety or privacy of our users (so please use test accounts), or the availability of Zomato through DoS attacks or spam. We also request you not to use vulnerability testing tools that generate a significant volume of traffic.\n\nCertain vulnerabilities with a working proof of concept on some of our Android mobile app(s) may qualify for an additional bounty through the [Google Play Security Rewards Program] (https://hackerone.com/googleplay). To see which apps and vulnerabilities may qualify for a bounty, please refer to the [Google Play Security Rewards Program’s Scope and Vulnerability Criteria] (https://hackerone.com/googleplay).\n\n# Rewards\nWe will reward reports according to the severity of their impact on a case-by-case basis as determined by our security team. We may pay more for unique, hard-to-find bugs; we may also pay less for bugs with complex prerequisites that lower the risk of exploitation. \n\nBelow, you can find examples of vulnerabilities and their impacts grouped by our severity ranking. This is not an exhaustive list and it is designed to give you insight on how we rate vulnerabilities. \n\n# Critical \n* Remote Code Execution (RCE) - able to execute arbitrary commands on a remote device\n* SQL Injection - able to read Personally Identifiable Information (PII) or other sensitive data / full read/write access to a database\n* Server-Side Request Forgery (SSRF) - able to pivot to internal application and/or access credentials (not blind)\n* Information Disclosure - mass PII leaks including data such as names, emails, phone numbers and addresses\n\n# High \n* Stored Cross-Site Scripting (XSS) - stored XSS with access to non HttpOnly cookies\n* Information Disclosure - leaked credentials\n* Subdomain Takeover - on a domain that sees heavy traffic or would be a convincing candidate for a phishing attack\n* Cross-Site Request Forgery (CSRF) - leading to account takeover\n* Account Takeover (ATO) - with no or minimal user interaction\n* Insecure Direct Object Reference (IDOR) - read or write access to sensitive data or important fields that you do not have permission to\n* SQL Injection - able to perform queries with a limited access user\n\n# Medium \n* CSRF - able to modify important information (authenticated) \n* ATO - required user interaction\n* IDOR - write access to modify objects that you do not have permission to\n* XSS - reflected/DOM XSS with access to cookies\n\n# Low \n* Directory listings \n* XSS - POST based XSS (with CSRF bypass)\n* Lack of HTTPS on dynamic pages (judged on a case-by-case basis)\n* Server information page (no credentials)\n* Subdomain Takeover - on an unused subdomain\n\n# Eligibility and Responsible Disclosure\nTo promote the discovery and reporting of vulnerabilities and increase user safety, we ask that you:\n* Give us a reasonable time to respond to the issue before making any information about it public.\n* Not access or modify data without the explicit permission of the owner.\n* Act in good faith not to degrade the performance of our services (including denial of service).\n \nWe only reward the first reporter of a vulnerability. Public disclosure of the vulnerability prior to resolution will result in disqualification from the program. You must report a qualifying vulnerability through the HackerOne reporting tool to be eligible for a monetary reward.\n\n# Non-qualifying vulnerabilities / Known Issues\n\nWhen reporting vulnerabilities, please consider (1) attack scenario/exploitability, and (2) the security impact of the bug. The following issues are considered out of scope:\n \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 brute force 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 implication can be demonstrated \n* Self XSS\n* Promo code abuse (e.g. ordering multiple times using the same promo code)\n* Abuse of our promotional offers and referral codes\n* CSRF on www.zomato.com/php/* and www.zomato.com/clients*/\n* Promo code enumeration, abuse of our promotional offers and referral codes.\n* Able to retrieve user's public information.\n* Username / email enumeration\n\n# Consequences of complying with this policy\n\nWe will not pursue a civil action or initiate a complaint to law enforcement for accidental, good faith violations of this policy. We consider activities conducted consistent with this policy to constitute “authorized” conduct under the Computer Fraud and Abuse Act (CFAA). We will not bring a DMCA claim against you for circumventing the technological measures we have used to protect the applications in scope.\n\nIf legal action is initiated by a third party against you and you have complied with Zomato's bug bounty policy, Zomato will take steps to make it known that your actions were conducted in compliance with this policy.\n\nPlease submit a [HackerOne report] (https://hackerone.com/zomato) to us before engaging in conduct that may be inconsistent with or unaddressed by this policy.\n\nThank you for helping keep @Zomato safe for the community!\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":"2021-03-16T08:08:53.204Z"},{"id":3647659,"new_policy":"We take security seriously at Zomato, and we’re committed to protecting our community. If you are a security researcher or expert, and believe you’ve identified security-related issues with Zomato’s website or apps, we would appreciate you disclosing it to us responsibly. \n\nOur team is committed to addressing all security issues in a responsible and timely manner, and we ask the security community to give us the opportunity to do so before disclosing them publicly. Please submit a detailed description of the issue to us, along with the steps to reproduce it. We trust the security community to make every effort to protect our users’ data and privacy. \n\n# Disclosure Policy\n* Let us know as soon as possible upon discovery of a potential security issue, and we'll make every effort to quickly resolve the issue.\n* Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party.\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\n# Scope\nThe scope of issues is limited to technical vulnerabilities in the Zomato website or mobile apps. Please do not attempt to compromise the safety or privacy of our users (so please use test accounts), or the availability of Zomato through DoS attacks or spam. We also request you not to use vulnerability testing tools that generate a significant volume of traffic.\n\nCertain vulnerabilities with a working proof of concept on some of our Android mobile app(s) may qualify for an additional bounty through the [Google Play Security Rewards Program] (https://hackerone.com/googleplay). To see which apps and vulnerabilities may qualify for a bounty, please refer to the [Google Play Security Rewards Program’s Scope and Vulnerability Criteria] (https://hackerone.com/googleplay).\n\n# Rewards\nWe will reward reports according to the severity of their impact on a case-by-case basis as determined by our security team. We may pay more for unique, hard-to-find bugs; we may also pay less for bugs with complex prerequisites that lower the risk of exploitation. \n\nBelow, you can find examples of vulnerabilities and their impacts grouped by our severity ranking. This is not an exhaustive list and it is designed to give you insight on how we rate vulnerabilities. \n\n# Critical \n* Remote Code Execution (RCE) - able to execute arbitrary commands on a remote device\n* SQL Injection - able to read Personally Identifiable Information (PII) or other sensitive data / full read/write access to a database\n* Server-Side Request Forgery (SSRF) - able to pivot to internal application and/or access credentials (not blind)\n* Information Disclosure - mass PII leaks including data such as names, emails, phone numbers and addresses\n\n# High \n* Stored Cross-Site Scripting (XSS) - stored XSS with access to non HttpOnly cookies\n* Information Disclosure - leaked credentials\n* Subdomain Takeover - on a domain that sees heavy traffic or would be a convincing candidate for a phishing attack\n* Cross-Site Request Forgery (CSRF) - leading to account takeover\n* Account Takeover (ATO) - with no or minimal user interaction\n* Insecure Direct Object Reference (IDOR) - read or write access to sensitive data or important fields that you do not have permission to\n* SQL Injection - able to perform queries with a limited access user\n\n# Medium \n* CSRF - able to modify important information (authenticated) \n* ATO - required user interaction\n* IDOR - write access to modify objects that you do not have permission to\n* XSS - reflected/DOM XSS with access to cookies\n\n# Low \n* Directory listings \n* XSS - POST based XSS (with CSRF bypass)\n* Lack of HTTPS on dynamic pages (judged on a case-by-case basis)\n* Server information page (no credentials)\n* Subdomain Takeover - on an unused subdomain\n\n# Eligibility and Responsible Disclosure\nTo promote the discovery and reporting of vulnerabilities and increase user safety, we ask that you:\n* Give us a reasonable time to respond to the issue before making any information about it public.\n* Not access or modify data without the explicit permission of the owner.\n* Act in good faith not to degrade the performance of our services (including denial of service).\n \nWe only reward the first reporter of a vulnerability. Public disclosure of the vulnerability prior to resolution will result in disqualification from the program. You must report a qualifying vulnerability through the HackerOne reporting tool to be eligible for a monetary reward.\n\n# Non-qualifying vulnerabilities / Known Issues\n\nWhen reporting vulnerabilities, please consider (1) attack scenario/exploitability, and (2) the security impact of the bug. The following issues are considered out of scope:\n \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 brute force 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 implication can be demonstrated \n* Self XSS\n* Promo code abuse (e.g. ordering multiple times using the same promo code)\n* Abuse of our promotional offers and referral codes\n* CSRF on www.zomato.com/php/* and www.zomato.com/clients*/\n* Promo code enumeration, abuse of our promotional offers and referral codes.\n* Able to retrieve user's public information.\n* Username / email enumeration\n\n# Consequences of complying with this policy\n\nWe will not pursue a civil action or initiate a complaint to law enforcement for accidental, good faith violations of this policy. We consider activities conducted consistent with this policy to constitute “authorized” conduct under the Computer Fraud and Abuse Act (CFAA). We will not bring a DMCA claim against you for circumventing the technological measures we have used to protect the applications in scope.\n\nIf legal action is initiated by a third party against you and you have complied with Zomato's bug bounty policy, Zomato will take steps to make it known that your actions were conducted in compliance with this policy.\n\nPlease submit a [HackerOne report] (https://hackerone.com/zomato) to us before engaging in conduct that may be inconsistent with or unaddressed by this policy.\n\nThank you for helping keep @Zomato safe for the community!\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":"2021-01-11T17:19:37.634Z"},{"id":3636362,"new_policy":"We take security seriously at Zomato, and we’re committed to protecting our community. If you are a security researcher or expert, and believe you’ve identified security-related issues with Zomato’s website or apps, we would appreciate you disclosing it to us responsibly. \n\nOur team is committed to addressing all security issues in a responsible and timely manner, and we ask the security community to give us the opportunity to do so before disclosing them publicly. Please submit a detailed description of the issue to us, along with the steps to reproduce it. We trust the security community to make every effort to protect our users’ data and privacy. \n\n# Disclosure Policy\n* Let us know as soon as possible upon discovery of a potential security issue, and we'll make every effort to quickly resolve the issue.\n* Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party.\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\n# Scope\nThe scope of issues is limited to technical vulnerabilities in the Zomato website or mobile apps. Please do not attempt to compromise the safety or privacy of our users (so please use test accounts), or the availability of Zomato through DoS attacks or spam. We also request you not to use vulnerability testing tools that generate a significant volume of traffic.\n\nCertain vulnerabilities with a working proof of concept on some of our Android mobile app(s) may qualify for an additional bounty through the [Google Play Security Rewards Program] (https://hackerone.com/googleplay). To see which apps and vulnerabilities may qualify for a bounty, please refer to the [Google Play Security Rewards Program’s Scope and Vulnerability Criteria] (https://hackerone.com/googleplay).\n\n# Rewards\nWe will reward reports according to the severity of their impact on a case-by-case basis as determined by our security team. We may pay more for unique, hard-to-find bugs; we may also pay less for bugs with complex prerequisites that lower the risk of exploitation. \n\nBelow, you can find examples of vulnerabilities and their impacts grouped by our severity ranking. This is not an exhaustive list and it is designed to give you insight on how we rate vulnerabilities. \n\n# Critical \n* Remote Code Execution (RCE) - able to execute arbitrary commands on a remote device\n* SQL Injection - able to read Personally Identifiable Information (PII) or other sensitive data / full read/write access to a database\n* Server-Side Request Forgery (SSRF) - able to pivot to internal application and/or access credentials (not blind)\n* Information Disclosure - mass PII leaks including data such as names, phone numbers and addresses\n\n# High \n* Stored Cross-Site Scripting (XSS) - stored XSS with access to non HttpOnly cookies\n* Information Disclosure - leaked credentials\n* Subdomain Takeover - on a domain that sees heavy traffic or would be a convincing candidate for a phishing attack\n* Cross-Site Request Forgery (CSRF) - leading to account takeover\n* Account Takeover (ATO) - with no or minimal user interaction\n* Insecure Direct Object Reference (IDOR) - read or write access to sensitive data or important fields that you do not have permission to\n* SQL Injection - able to perform queries with a limited access user\n\n# Medium \n* CSRF - able to modify important information (authenticated) \n* ATO - required user interaction\n* IDOR - write access to modify objects that you do not have permission to\n* XSS - reflected/DOM XSS with access to cookies\n\n# Low \n* Directory listings \n* XSS - POST based XSS (with CSRF bypass)\n* Lack of HTTPS on dynamic pages (judged on a case-by-case basis)\n* Server information page (no credentials)\n* Subdomain Takeover - on an unused subdomain\n\n# Eligibility and Responsible Disclosure\nTo promote the discovery and reporting of vulnerabilities and increase user safety, we ask that you:\n* Give us a reasonable time to respond to the issue before making any information about it public.\n* Not access or modify data without explicit permission of the owner.\n* Act in good faith not to degrade the performance of our services (including denial of service).\n \nWe only reward the first reporter of a vulnerability. Public disclosure of the vulnerability prior to resolution will result in disqualification from the program. You must report a qualifying vulnerability through the HackerOne reporting tool to be eligible for a monetary reward.\n\n# Non-qualifying vulnerabilities / Known Issues\n\nWhen 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* 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 brute force 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 implication can be demonstrated \n* Self XSS\n* Promo code abuse (e.g. ordering multiple times using the same promo code)\n* Abuse of our promotional offers and referral codes\n* CSRF on www.zomato.com/php/* and www.zomato.com/clients*/\n* Promo code enumeration, abuse of our promotional offers and referral codes.\n* Able to retrieve user's public information.\n* Username / email enumeration\n\n# Consequences of complying with this policy\n\nWe will not pursue a civil action or initiate a complaint to law enforcement for accidental, good faith violations of this policy. We consider activities conducted consistent with this policy to constitute “authorized” conduct under the Computer Fraud and Abuse Act (CFAA). We will not bring a DMCA claim against you for circumventing the technological measures we have used to protect the applications in scope.\n\nIf legal action is initiated by a third party against you and you have complied with Zomato's bug bounty policy, Zomato will take steps to make it known that your actions were conducted in compliance with this policy.\n\nPlease submit a [HackerOne report] (https://hackerone.com/zomato) to us before engaging in conduct that may be inconsistent with or unaddressed by this policy.\n\nThank you for helping keep @Zomato safe for the community!\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":"2020-05-17T16:12:27.419Z"},{"id":3622776,"new_policy":"We take security seriously at Zomato, and we’re committed to protecting our community. If you are a security researcher or expert, and believe you’ve identified security-related issues with Zomato’s website or apps, we would appreciate you disclosing it to us responsibly. \n\nOur team is committed to addressing all security issues in a responsible and timely manner, and we ask the security community to give us the opportunity to do so before disclosing them publicly. Please submit a detailed description of the issue to us, along with the steps to reproduce it. We trust the security community to make every effort to protect our users’ data and privacy. \n\n# Disclosure Policy\n* Let us know as soon as possible upon discovery of a potential security issue, and we'll make every effort to quickly resolve the issue.\n* Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party.\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\n# Scope\nThe scope of issues is limited to technical vulnerabilities in the Zomato website or mobile apps. Please do not attempt to compromise the safety or privacy of our users (so please use test accounts), or the availability of Zomato through DoS attacks or spam. We also request you not to use vulnerability testing tools that generate a significant volume of traffic.\n\nCertain vulnerabilities with a working proof of concept on some of our Android mobile app(s) may qualify for an additional bounty through the [Google Play Security Rewards Program] (https://hackerone.com/googleplay). To see which apps and vulnerabilities may qualify for a bounty, please refer to the [Google Play Security Rewards Program’s Scope and Vulnerability Criteria] (https://hackerone.com/googleplay).\n\n# Rewards\nWe will reward reports according to the severity of their impact on a case-by-case basis as determined by our security team. We may pay more for unique, hard-to-find bugs; we may also pay less for bugs with complex prerequisites that lower the risk of exploitation. \n\nBelow, you can find examples of vulnerabilities and their impacts grouped by our severity ranking. This is not an exhaustive list and it is designed to give you insight on how we rate vulnerabilities. \n\n# Critical \n* Remote Code Execution (RCE) - able to execute arbitrary commands on a remote device\n* SQL Injection - able to read Personally Identifiable Information (PII) or other sensitive data / full read/write access to a database\n* Server-Side Request Forgery (SSRF) - able to pivot to internal application and/or access credentials (not blind)\n* Information Disclosure - mass PII leaks including data such as names, phone numbers and addresses\n\n# High \n* Stored Cross-Site Scripting (XSS) - stored XSS with access to non HttpOnly cookies\n* Information Disclosure - leaked credentials\n* Subdomain Takeover - on a domain that still sees traffic or would be a convincing candidate for a phishing attack\n* Cross-Site Request Forgery (CSRF) - leading to account takeover\n* Account Takeover (ATO) - with no or minimal user interaction\n* Insecure Direct Object Reference (IDOR) - read or write access to sensitive data or important fields that you do not have permission to\n* SQL Injection - able to perform queries with a limited access user\n\n# Medium \n* CSRF - able to modify important information (authenticated) \n* ATO - required user interaction\n* IDOR - write access to modify objects that you do not have permission to\n* XSS - reflected/DOM XSS with access to cookies\n* Subdomain Takeover - on an unused subdomain \n\n# Low \n* Directory listings \n* XSS - POST based XSS (with CSRF bypass)\n* Lack of HTTPS on dynamic pages (judged on a case-by-case basis)\n* Server information page (no credentials)\n\n# Eligibility and Responsible Disclosure\nTo promote the discovery and reporting of vulnerabilities and increase user safety, we ask that you:\n* Give us a reasonable time to respond to the issue before making any information about it public.\n* Not access or modify data without explicit permission of the owner.\n* Act in good faith not to degrade the performance of our services (including denial of service).\n \nWe only reward the first reporter of a vulnerability. Public disclosure of the vulnerability prior to resolution will result in disqualification from the program. You must report a qualifying vulnerability through the HackerOne reporting tool to be eligible for a monetary reward.\n\n# Non-qualifying vulnerabilities / Known Issues\n\nWhen 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* 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 brute force 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 implication can be demonstrated \n* Self XSS\n* Promo code abuse (e.g. ordering multiple times using the same promo code)\n* Abuse of our promotional offers and referral codes\n* CSRF on www.zomato.com/php/* and www.zomato.com/clients*/\n* Promo code enumeration, abuse of our promotional offers and referral codes.\n* Able to retrieve user's public information.\n* Username / email enumeration\n\n# Consequences of complying with this policy\n\nWe will not pursue a civil action or initiate a complaint to law enforcement for accidental, good faith violations of this policy. We consider activities conducted consistent with this policy to constitute “authorized” conduct under the Computer Fraud and Abuse Act (CFAA). We will not bring a DMCA claim against you for circumventing the technological measures we have used to protect the applications in scope.\n\nIf legal action is initiated by a third party against you and you have complied with Zomato's bug bounty policy, Zomato will take steps to make it known that your actions were conducted in compliance with this policy.\n\nPlease submit a [HackerOne report] (https://hackerone.com/zomato) to us before engaging in conduct that may be inconsistent with or unaddressed by this policy.\n\nThank you for helping keep @Zomato safe for the community!\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":"2019-11-02T04:54:18.441Z"},{"id":3622133,"new_policy":"We take security seriously at Zomato, and we’re committed to protecting our community. If you are a security researcher or expert, and believe you’ve identified security-related issues with Zomato’s website or apps, we would appreciate you disclosing it to us responsibly. \n\nOur team is committed to addressing all security issues in a responsible and timely manner, and we ask the security community to give us the opportunity to do so before disclosing them publicly. Please submit a detailed description of the issue to us, along with the steps to reproduce it. We trust the security community to make every effort to protect our users’ data and privacy. \n\n# Disclosure Policy\n* Let us know as soon as possible upon discovery of a potential security issue, and we'll make every effort to quickly resolve the issue.\n* Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party.\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\n# Scope\nThe scope of issues is limited to technical vulnerabilities in the Zomato website or mobile apps. Please do not attempt to compromise the safety or privacy of our users (so please use test accounts), or the availability of Zomato through DoS attacks or spam. We also request you not to use vulnerability testing tools that generate a significant volume of traffic.\n\nCertain vulnerabilities with a working proof of concept on some of our Android mobile app(s) may qualify for an additional bounty through the [Google Play Security Rewards Program] (https://hackerone.com/googleplay). To see which apps and vulnerabilities may qualify for a bounty, please refer to the [Google Play Security Rewards Program’s Scope and Vulnerability Criteria] (https://hackerone.com/googleplay).\n\n-----------------------\n\n** One Week Promotion **\n\n#Reward Bonus:\n\nWe'll be awarding a bonus for the best report which is reported between now and November 1st, 2019. To encourage a higher quality of reports, the focus of this engagement is to uncover only critical issues (Critical or High) on our listed assets. The best report received within this time period which meets the above criteria will be eligible for a $2000 bonus.\n\n------------------------\n\n# Rewards\nWe will reward reports according to the severity of their impact on a case-by-case basis as determined by our security team. We may pay more for unique, hard-to-find bugs; we may also pay less for bugs with complex prerequisites that lower the risk of exploitation. \n\nBelow, you can find examples of vulnerabilities and their impacts grouped by our severity ranking. This is not an exhaustive list and it is designed to give you insight on how we rate vulnerabilities. \n\n# Critical \n* Remote Code Execution (RCE) - able to execute arbitrary commands on a remote device\n* SQL Injection - able to read Personally Identifiable Information (PII) or other sensitive data / full read/write access to a database\n* Server-Side Request Forgery (SSRF) - able to pivot to internal application and/or access credentials (not blind)\n* Information Disclosure - mass PII leaks including data such as names, phone numbers and addresses\n\n# High \n* Stored Cross-Site Scripting (XSS) - stored XSS with access to non HttpOnly cookies\n* Information Disclosure - leaked credentials\n* Subdomain Takeover - on a domain that still sees traffic or would be a convincing candidate for a phishing attack\n* Cross-Site Request Forgery (CSRF) - leading to account takeover\n* Account Takeover (ATO) - with no or minimal user interaction\n* Insecure Direct Object Reference (IDOR) - read or write access to sensitive data or important fields that you do not have permission to\n* SQL Injection - able to perform queries with a limited access user\n\n# Medium \n* CSRF - able to modify important information (authenticated) \n* ATO - required user interaction\n* IDOR - write access to modify objects that you do not have permission to\n* XSS - reflected/DOM XSS with access to cookies\n* Subdomain Takeover - on an unused subdomain \n\n# Low \n* Directory listings \n* XSS - POST based XSS (with CSRF bypass)\n* Lack of HTTPS on dynamic pages (judged on a case-by-case basis)\n* Server information page (no credentials)\n\n# Eligibility and Responsible Disclosure\nTo promote the discovery and reporting of vulnerabilities and increase user safety, we ask that you:\n* Give us a reasonable time to respond to the issue before making any information about it public.\n* Not access or modify data without explicit permission of the owner.\n* Act in good faith not to degrade the performance of our services (including denial of service).\n \nWe only reward the first reporter of a vulnerability. Public disclosure of the vulnerability prior to resolution will result in disqualification from the program. You must report a qualifying vulnerability through the HackerOne reporting tool to be eligible for a monetary reward.\n\n# Non-qualifying vulnerabilities / Known Issues\n\nWhen 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* 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 brute force 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 implication can be demonstrated \n* Self XSS\n* Promo code abuse (e.g. ordering multiple times using the same promo code)\n* Abuse of our promotional offers and referral codes\n* CSRF on www.zomato.com/php/* and www.zomato.com/clients*/\n* Promo code enumeration, abuse of our promotional offers and referral codes.\n* Able to retrieve user's public information.\n* Username / email enumeration\n\n# Consequences of complying with this policy\n\nWe will not pursue a civil action or initiate a complaint to law enforcement for accidental, good faith violations of this policy. We consider activities conducted consistent with this policy to constitute “authorized” conduct under the Computer Fraud and Abuse Act (CFAA). We will not bring a DMCA claim against you for circumventing the technological measures we have used to protect the applications in scope.\n\nIf legal action is initiated by a third party against you and you have complied with Zomato's bug bounty policy, Zomato will take steps to make it known that your actions were conducted in compliance with this policy.\n\nPlease submit a [HackerOne report] (https://hackerone.com/zomato) to us before engaging in conduct that may be inconsistent with or unaddressed by this policy.\n\nThank you for helping keep @Zomato safe for the community!\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":"2019-10-24T17:59:40.761Z"},{"id":3615805,"new_policy":"We take security seriously at Zomato, and we’re committed to protecting our community. If you are a security researcher or expert, and believe you’ve identified security-related issues with Zomato’s website or apps, we would appreciate you disclosing it to us responsibly. \n\nOur team is committed to addressing all security issues in a responsible and timely manner, and we ask the security community to give us the opportunity to do so before disclosing them publicly. Please submit a detailed description of the issue to us, along with the steps to reproduce it. We trust the security community to make every effort to protect our users’ data and privacy. \n\n# Disclosure Policy\n* Let us know as soon as possible upon discovery of a potential security issue, and we'll make every effort to quickly resolve the issue.\n* Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party.\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\n# Scope\nThe scope of issues is limited to technical vulnerabilities in the Zomato website or mobile apps. Please do not attempt to compromise the safety or privacy of our users (so please use test accounts), or the availability of Zomato through DoS attacks or spam. We also request you not to use vulnerability testing tools that generate a significant volume of traffic.\n\nCertain vulnerabilities with a working proof of concept on some of our Android mobile app(s) may qualify for an additional bounty through the [Google Play Security Rewards Program] (https://hackerone.com/googleplay). To see which apps and vulnerabilities may qualify for a bounty, please refer to the [Google Play Security Rewards Program’s Scope and Vulnerability Criteria] (https://hackerone.com/googleplay).\n\n# Rewards\nWe will reward reports according to the severity of their impact on a case-by-case basis as determined by our security team. We may pay more for unique, hard-to-find bugs; we may also pay less for bugs with complex prerequisites that lower the risk of exploitation. \n\nBelow, you can find examples of vulnerabilities and their impacts grouped by our severity ranking. This is not an exhaustive list and it is designed to give you insight on how we rate vulnerabilities. \n\n# Critical \n* Remote Code Execution (RCE) - able to execute arbitrary commands on a remote device\n* SQL Injection - able to read Personally Identifiable Information (PII) or other sensitive data / full read/write access to a database\n* Server-Side Request Forgery (SSRF) - able to pivot to internal application and/or access credentials (not blind)\n* Information Disclosure - mass PII leaks including data such as names, phone numbers and addresses\n\n# High \n* Stored Cross-Site Scripting (XSS) - stored XSS with access to non HttpOnly cookies\n* Information Disclosure - leaked credentials\n* Subdomain Takeover - on a domain that still sees traffic or would be a convincing candidate for a phishing attack\n* Cross-Site Request Forgery (CSRF) - leading to account takeover\n* Account Takeover (ATO) - with no or minimal user interaction\n* Insecure Direct Object Reference (IDOR) - read or write access to sensitive data or important fields that you do not have permission to\n* SQL Injection - able to perform queries with a limited access user\n\n# Medium \n* CSRF - able to modify important information (authenticated) \n* ATO - required user interaction\n* IDOR - write access to modify objects that you do not have permission to\n* XSS - reflected/DOM XSS with access to cookies\n* Subdomain Takeover - on an unused subdomain \n\n# Low \n* Directory listings \n* XSS - POST based XSS (with CSRF bypass)\n* Lack of HTTPS on dynamic pages (judged on a case-by-case basis)\n* Server information page (no credentials)\n\n# Eligibility and Responsible Disclosure\nTo promote the discovery and reporting of vulnerabilities and increase user safety, we ask that you:\n* Give us a reasonable time to respond to the issue before making any information about it public.\n* Not access or modify data without explicit permission of the owner.\n* Act in good faith not to degrade the performance of our services (including denial of service).\n \nWe only reward the first reporter of a vulnerability. Public disclosure of the vulnerability prior to resolution will result in disqualification from the program. You must report a qualifying vulnerability through the HackerOne reporting tool to be eligible for a monetary reward.\n\n# Non-qualifying vulnerabilities / Known Issues\n\nWhen 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* 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 brute force 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 implication can be demonstrated \n* Self XSS\n* Promo code abuse (e.g. ordering multiple times using the same promo code)\n* Abuse of our promotional offers and referral codes\n* CSRF on www.zomato.com/php/* and www.zomato.com/clients*/\n* Promo code enumeration, abuse of our promotional offers and referral codes.\n* Able to retrieve user's public information.\n* Username / email enumeration\n\n# Consequences of complying with this policy\n\nWe will not pursue a civil action or initiate a complaint to law enforcement for accidental, good faith violations of this policy. We consider activities conducted consistent with this policy to constitute “authorized” conduct under the Computer Fraud and Abuse Act (CFAA). We will not bring a DMCA claim against you for circumventing the technological measures we have used to protect the applications in scope.\n\nIf legal action is initiated by a third party against you and you have complied with Zomato's bug bounty policy, Zomato will take steps to make it known that your actions were conducted in compliance with this policy.\n\nPlease submit a [HackerOne report] (https://hackerone.com/zomato) to us before engaging in conduct that may be inconsistent with or unaddressed by this policy.\n\nThank you for helping keep @Zomato safe for the community!\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":"2019-08-08T05:37:59.415Z"},{"id":3611727,"new_policy":"We take security seriously at Zomato, and we’re committed to protecting our community. If you are a security researcher or expert, and believe you’ve identified security-related issues with Zomato’s website or apps, we would appreciate you disclosing it to us responsibly. \n\nOur team is committed to addressing all security issues in a responsible and timely manner, and we ask the security community to give us the opportunity to do so before disclosing them publicly. Please submit a detailed description of the issue to us, along with the steps to reproduce it. We trust the security community to make every effort to protect our users’ data and privacy. \n\n# Disclosure Policy\n* Let us know as soon as possible upon discovery of a potential security issue, and we'll make every effort to quickly resolve the issue.\n* Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party.\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\n# Scope\nThe scope of issues is limited to technical vulnerabilities in the Zomato website or mobile apps. Please do not attempt to compromise the safety or privacy of our users (so please use test accounts), or the availability of Zomato through DoS attacks or spam. We also request you not to use vulnerability testing tools that generate a significant volume of traffic.\n\nCertain vulnerabilities with a working proof of concept on some of our Android mobile app(s) may qualify for an additional bounty through the [Google Play Security Rewards Program] (https://hackerone.com/googleplay). To see which apps and vulnerabilities may qualify for a bounty, please refer to the [Google Play Security Rewards Program’s Scope and Vulnerability Criteria] (https://hackerone.com/googleplay).\n\n# Rewards\nWe will reward reports according to the severity of their impact on a case-by-case basis as determined by our security team. We may pay more for unique, hard-to-find bugs; we may also pay less for bugs with complex prerequisites that lower the risk of exploitation. \n\nBelow, you can find examples of vulnerabilities and their impacts grouped by our severity ranking. This is not an exhaustive list and it is designed to give you insight on how we rate vulnerabilities. \n\n# Critical \n* Remote Code Execution (RCE) - able to execute arbitrary commands on a remote device\n* SQL Injection - able to read Personally Identifiable Information (PII) or other sensitive data / full read/write access to a database\n* Server-Side Request Forgery (SSRF) - able to pivot to internal application and/or access credentials (not blind)\n* Information Disclosure - mass PII leaks including data such as names, phone numbers and addresses\n\n# High \n* Stored Cross-Site Scripting (XSS) - stored XSS with access to non HttpOnly cookies\n* Information Disclosure - leaked credentials\n* Subdomain Takeover - on a domain that still sees traffic or would be a convincing candidate for a phishing attack\n* Cross-Site Request Forgery (CSRF) - leading to account takeover\n* Account Takeover (ATO) - with no or minimal user interaction\n* Insecure Direct Object Reference (IDOR) - read or write access to sensitive data or important fields that you do not have permission to\n* SQL Injection - able to perform queries with a limited access user\n\n# Medium \n* CSRF - able to modify important information (authenticated) \n* ATO - required user interaction\n* IDOR - write access to modify objects that you do not have permission to\n* XSS - reflected/DOM XSS with access to cookies\n* Subdomain Takeover - on an unused subdomain \n\n# Low \n* Directory listings \n* XSS - POST based XSS (with CSRF)\n* Lack of HTTPS on dynamic pages (judged on a case-by-case basis)\n* Server information page (no credentials)\n\n# Eligibility and Responsible Disclosure\nTo promote the discovery and reporting of vulnerabilities and increase user safety, we ask that you:\n* Give us a reasonable time to respond to the issue before making any information about it public.\n* Not access or modify data without explicit permission of the owner.\n* Act in good faith not to degrade the performance of our services (including denial of service).\n \nWe only reward the first reporter of a vulnerability. Public disclosure of the vulnerability prior to resolution will result in disqualification from the program. You must report a qualifying vulnerability through the HackerOne reporting tool to be eligible for a monetary reward.\n\n# Non-qualifying vulnerabilities / Known Issues\n\nWhen 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* 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 brute force 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 implication can be demonstrated \n* Self XSS\n* Promo code abuse (e.g. ordering multiple times using the same promo code)\n* Abuse of our promotional offers and referral codes\n* CSRF on www.zomato.com/php/* and www.zomato.com/clients*/\n\n# Consequences of complying with this policy\n\nWe will not pursue a civil action or initiate a complaint to law enforcement for accidental, good faith violations of this policy. We consider activities conducted consistent with this policy to constitute “authorized” conduct under the Computer Fraud and Abuse Act (CFAA). We will not bring a DMCA claim against you for circumventing the technological measures we have used to protect the applications in scope.\n\nIf legal action is initiated by a third party against you and you have complied with Zomato's bug bounty policy, Zomato will take steps to make it known that your actions were conducted in compliance with this policy.\n\nPlease submit a [HackerOne report] (https://hackerone.com/zomato) to us before engaging in conduct that may be inconsistent with or unaddressed by this policy.\n\nThank you for helping keep @Zomato safe for the community!\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":"2019-06-12T09:05:29.207Z"},{"id":3606957,"new_policy":"We take security seriously at Zomato, and we’re committed to protecting our community. If you are a security researcher or expert, and believe you’ve identified security-related issues with Zomato’s website or apps, we would appreciate you disclosing it to us responsibly. \n\nOur team is committed to addressing all security issues in a responsible and timely manner, and we ask the security community to give us the opportunity to do so before disclosing them publicly. Please submit a detailed description of the issue to us, along with the steps to reproduce it. We trust the security community to make every effort to protect our users’ data and privacy. \n\n**Disclosure Policy**\n* Let us know as soon as possible upon discovery of a potential security issue, and we'll make every effort to quickly resolve the issue.\n* Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party.\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\n**Scope**\nThe scope of issues is limited to technical vulnerabilities in the Zomato website or mobile apps. Please do not attempt to compromise the safety or privacy of our users (so please use test accounts), or the availability of Zomato through DoS attacks or spam. We also request you not to use vulnerability testing tools that generate a significant volume of traffic.\n\nCertain vulnerabilities with a working proof of concept on some of our Android mobile app(s) may qualify for an additional bounty through the [Google Play Security Rewards Program] (https://hackerone.com/googleplay). To see which apps and vulnerabilities may qualify for a bounty, please refer to the [Google Play Security Rewards Program’s Scope and Vulnerability Criteria] (https://hackerone.com/googleplay).\n\n**Bounty Program**\nWe will reward reports according to their severity on a case-by-case basis as determined by our security team. We may pay more for unique, hard-to-find bugs; we may also pay less for bugs with complex prerequisites that lower risk of exploitation.\n\nThe minimum reward for severe bugs like Remote Code Execution or User Personal Information Access is $2000 USD.\n\n**Eligibility and Responsible Disclosure**\nTo promote the discovery and reporting of vulnerabilities and increase user safety, we ask that you:\n* Give us a reasonable time to respond to the issue before making any information about it public.\n* Not access or modify data without explicit permission of the owner.\n* Act in good faith not to degrade the performance of our services (including denial of service).\n \nWe only reward the first reporter of a vulnerability. Public disclosure of the vulnerability prior to resolution will result in disqualification from the program. You must report a qualifying vulnerability through the HackerOne reporting tool to be eligible for a monetary reward.\n\n**Non-qualifying vulnerabilities / Known Issues**\n\nAlthough we review every reported issue on a case-by-case basis, some of them may not qualify depending on their impact. Here are some common low-risk issues that typically do not qualify:\n\n* Attacks requiring physical access to a user's device\n* Forms missing CSRF tokens (we require evidence of actual CSRF vulnerability)\n* Login/logout CSRF\n* Password and account recovery policies, such as reset link expiration or password complexity\n* Invalid or missing SPF (Sender Policy Framework) records\n* Content spoofing/text injection\n* Username enumeration and other similar enumeration reports\n* Self-XSS without a vector for a third party attack.\n* Issues related to software or protocols not under Zomato's control\n* Reports of spam\n* Bypass of URL malware detection\n* Best practices concerns\n* Denial of Service Attacks\n* Bruteforce Attacks\n* Spamming the users\n* Content injection issues\n* Open redirects with minimal security implications\n* Stack traces that disclose information\n* Banner grabbing issues\n* Outdated WordPress instances and plugins\n* Tab nabbing\n* Failure to implement security best practices such as rate limiting, minimum password strength, and mobile binary protection\n* Recently disclosed 0-day vulnerabilities\n* Account/e-mail enumeration\n* Results of automated tools or scanners\n* Login/logout/unauthenticated/low-impact CSRF\n* Lack of the Secure flag on non-sensitive cookies. We provide full site SSL as a mechanism to defend against MITM (via HSTS) for sensitive session cookies.\n* Lack of HTTPOnly flag on non-sensitive cookies. We have set the HTTPOnly flag on cookies we feel are sensitive and we do not consider the lack of HTTPOnly on other cookies to be a vulnerability.\n* Vulnerabilities only affecting users of outdated or unpatched browsers and platforms\n* Any physical attempts against Zomato property or data centers\n* Issues without clearly identified security impact, such as clickjacking on a static website, missing security headers, or descriptive error messages\n* Do not test the physical security of Zomato offices, employees, equipment, etc.\n* Do not test using social engineering techniques (this includes phishing attacks against Zomato employees/contractors). Do not perform DoS or DDoS attacks.\n* Do not in any way attack our end users, or engage in the trade of stolen user credentials.\n* CSRF on `www.zomato.com/php/*` , `www.zomato.com/clients/*`\n* Promo code enumeration, abuse of our promotional offers and referral codes.\n* Able to retrieve user's public information.\n\n###Consequences of complying with this policy\n\nWe will not pursue a civil action or initiate a complaint to law enforcement for accidental, good faith violations of this policy. We consider activities conducted consistent with this policy to constitute “authorized” conduct under the Computer Fraud and Abuse Act (CFAA). We will not bring a DMCA claim against you for circumventing the technological measures we have used to protect the applications in scope.\n\nIf legal action is initiated by a third party against you and you have complied with Zomato's bug bounty policy, Zomato will take steps to make it known that your actions were conducted in compliance with this policy.\n\nPlease submit a [HackerOne report] (https://hackerone.com/zomato) to us before engaging in conduct that may be inconsistent with or unaddressed by this policy.\n\nThank you for helping keep @Zomato safe for the community!\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":"2019-04-05T09:27:13.749Z"},{"id":3606117,"new_policy":"We take security seriously at Zomato, and we’re committed to protecting our community. If you are a security researcher or expert, and believe you’ve identified security-related issues with Zomato’s website or apps, we would appreciate you disclosing it to us responsibly. \n\nOur team is committed to addressing all security issues in a responsible and timely manner, and we ask the security community to give us the opportunity to do so before disclosing them publicly. Please submit a detailed description of the issue to us, along with the steps to reproduce it. We trust the security community to make every effort to protect our users’ data and privacy. \n\n**Disclosure Policy**\n* Let us know as soon as possible upon discovery of a potential security issue, and we'll make every effort to quickly resolve the issue.\n* Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party.\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\n**Scope**\nThe scope of issues is limited to technical vulnerabilities in the Zomato website or mobile apps. Please do not attempt to compromise the safety or privacy of our users (so please use test accounts), or the availability of Zomato through DoS attacks or spam. We also request you not to use vulnerability testing tools that generate a significant volume of traffic.\n\nCertain vulnerabilities with a working proof of concept on some of our Android mobile app(s) may qualify for an additional bounty through the [Google Play Security Rewards Program] (https://hackerone.com/googleplay). To see which apps and vulnerabilities may qualify for a bounty, please refer to the [Google Play Security Rewards Program’s Scope and Vulnerability Criteria] (https://hackerone.com/googleplay).\n\n**Bounty Program**\nWe will reward reports according to their severity on a case-by-case basis as determined by our security team. We may pay more for unique, hard-to-find bugs; we may also pay less for bugs with complex prerequisites that lower risk of exploitation.\n\nThe minimum reward for severe bugs like Remote Code Execution or User Personal Information Access is $2000 USD.\n\n**Eligibility and Responsible Disclosure**\nTo promote the discovery and reporting of vulnerabilities and increase user safety, we ask that you:\n* Give us a reasonable time to respond to the issue before making any information about it public.\n* Not access or modify data without explicit permission of the owner.\n* Act in good faith not to degrade the performance of our services (including denial of service).\n \nWe only reward the first reporter of a vulnerability. Public disclosure of the vulnerability prior to resolution will result in disqualification from the program. You must report a qualifying vulnerability through the HackerOne reporting tool to be eligible for a monetary reward.\n\n**Non-qualifying vulnerabilities / Known Issues**\n\nAlthough we review every reported issue on a case-by-case basis, some of them may not qualify depending on their impact. Here are some common low-risk issues that typically do not qualify:\n\n* Attacks requiring physical access to a user's device\n* Forms missing CSRF tokens (we require evidence of actual CSRF vulnerability)\n* Login/logout CSRF\n* Password and account recovery policies, such as reset link expiration or password complexity\n* Invalid or missing SPF (Sender Policy Framework) records\n* Content spoofing/text injection\n* Username enumeration and other similar enumeration reports\n* Self-XSS without a vector for a third party attack.\n* Issues related to software or protocols not under Zomato's control\n* Reports of spam\n* Bypass of URL malware detection\n* Best practices concerns\n* Denial of Service Attacks\n* Bruteforce Attacks\n* Spamming the users\n* Content injection issues\n* Open redirects with minimal security implications\n* Stack traces that disclose information\n* Banner grabbing issues\n* Outdated WordPress instances and plugins\n* Tab nabbing\n* Failure to implement security best practices such as rate limiting, minimum password strength, and mobile binary protection\n* Recently disclosed 0-day vulnerabilities\n* Account/e-mail enumeration\n* Results of automated tools or scanners\n* Login/logout/unauthenticated/low-impact CSRF\n* Lack of the Secure flag on non-sensitive cookies. We provide full site SSL as a mechanism to defend against MITM (via HSTS) for sensitive session cookies.\n* Lack of HTTPOnly flag on non-sensitive cookies. We have set the HTTPOnly flag on cookies we feel are sensitive and we do not consider the lack of HTTPOnly on other cookies to be a vulnerability.\n* Vulnerabilities only affecting users of outdated or unpatched browsers and platforms\n* Any physical attempts against Zomato property or data centers\n* Issues without clearly identified security impact, such as clickjacking on a static website, missing security headers, or descriptive error messages\n* Do not test the physical security of Zomato offices, employees, equipment, etc.\n* Do not test using social engineering techniques (this includes phishing attacks against Zomato employees/contractors). Do not perform DoS or DDoS attacks.\n* Do not in any way attack our end users, or engage in the trade of stolen user credentials.\n* CSRF on `www.zomato.com/php/*` , `www.zomato.com/clients/*`\n* Promo code enumeration, abuse of our promotional offers and referral codes.\n\n###Consequences of complying with this policy\n\nWe will not pursue a civil action or initiate a complaint to law enforcement for accidental, good faith violations of this policy. We consider activities conducted consistent with this policy to constitute “authorized” conduct under the Computer Fraud and Abuse Act (CFAA). We will not bring a DMCA claim against you for circumventing the technological measures we have used to protect the applications in scope.\n\nIf legal action is initiated by a third party against you and you have complied with Zomato's bug bounty policy, Zomato will take steps to make it known that your actions were conducted in compliance with this policy.\n\nPlease submit a [HackerOne report] (https://hackerone.com/zomato) to us before engaging in conduct that may be inconsistent with or unaddressed by this policy.\n\nThank you for helping keep @Zomato safe for the community!\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":"2019-03-25T18:30:27.006Z"},{"id":3604749,"new_policy":"We take security seriously at Zomato, and we’re committed to protecting our community. If you are a security researcher or expert, and believe you’ve identified security-related issues with Zomato’s website or apps, we would appreciate you disclosing it to us responsibly. \n\nOur team is committed to addressing all security issues in a responsible and timely manner, and we ask the security community to give us the opportunity to do so before disclosing them publicly. Please submit a detailed description of the issue to us, along with the steps to reproduce it. We trust the security community to make every effort to protect our users’ data and privacy. \n\n**Disclosure Policy**\n* Let us know as soon as possible upon discovery of a potential security issue, and we'll make every effort to quickly resolve the issue.\n* Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party.\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\n**Scope**\nThe scope of issues is limited to technical vulnerabilities in the Zomato website or mobile apps. Please do not attempt to compromise the safety or privacy of our users (so please use test accounts), or the availability of Zomato through DoS attacks or spam. We also request you not to use vulnerability testing tools that generate a significant volume of traffic.\n\nCertain vulnerabilities with a working proof of concept on some of our Android mobile app(s) may qualify for an additional bounty through the [Google Play Security Rewards Program] (https://hackerone.com/googleplay). To see which apps and vulnerabilities may qualify for a bounty, please refer to the [Google Play Security Rewards Program’s Scope and Vulnerability Criteria] (https://hackerone.com/googleplay).\n\n---------------------\n**Two Week Promotion**\n\nHey Hackers, \n\nFor the next two weeks, we will be awarding double bounties! Any new report that is reported between now and March 25th, 2019 will receive twice the bounty it normally would. To encourage a higher quality of reports, best report received within this time period will be eligible for a $2500 bonus.\n\nApart from the ones listed on our program page, here are few known/out of scope issues:\n\n- Email verification on our mobile application(s)\n- Social engineering, e.g. contacting support for refunds\n- Using disposable emails/Number to spoof the identity\n- www.zomato.com/blog/*\n\nIf you have any questions, feel free to reach out to us at security@zomato.com.\n\nWe look forward to your findings! Thank you and happy hacking!\n\n---------------------\n\n**Bounty Program**\nWe will reward reports according to their severity on a case-by-case basis as determined by our security team. We may pay more for unique, hard-to-find bugs; we may also pay less for bugs with complex prerequisites that lower risk of exploitation.\n\nThe minimum reward for severe bugs like Remote Code Execution or User Personal Information Access is $1000 USD.\n\n**Eligibility and Responsible Disclosure**\nTo promote the discovery and reporting of vulnerabilities and increase user safety, we ask that you:\n* Give us a reasonable time to respond to the issue before making any information about it public.\n* Not access or modify data without explicit permission of the owner.\n* Act in good faith not to degrade the performance of our services (including denial of service).\n \nWe only reward the first reporter of a vulnerability. Public disclosure of the vulnerability prior to resolution will result in disqualification from the program. You must report a qualifying vulnerability through the HackerOne reporting tool to be eligible for a monetary reward.\n\n**Non-qualifying vulnerabilities / Known Issues**\n\nAlthough we review every reported issue on a case-by-case basis, some of them may not qualify depending on their impact. Here are some common low-risk issues that typically do not qualify:\n\n* Attacks requiring physical access to a user's device\n* Forms missing CSRF tokens (we require evidence of actual CSRF vulnerability)\n* Login/logout CSRF\n* Password and account recovery policies, such as reset link expiration or password complexity\n* Invalid or missing SPF (Sender Policy Framework) records\n* Content spoofing/text injection\n* Username enumeration and other similar enumeration reports\n* Self-XSS without a vector for a third party attack.\n* Issues related to software or protocols not under Zomato's control\n* Reports of spam\n* Bypass of URL malware detection\n* Best practices concerns\n* Denial of Service Attacks\n* Bruteforce Attacks\n* Spamming the users\n* Content injection issues\n* Open redirects with minimal security implications\n* Stack traces that disclose information\n* Banner grabbing issues\n* Outdated WordPress instances and plugins\n* Tab nabbing\n* Failure to implement security best practices such as rate limiting, minimum password strength, and mobile binary protection\n* Recently disclosed 0-day vulnerabilities\n* Account/e-mail enumeration\n* Results of automated tools or scanners\n* Login/logout/unauthenticated/low-impact CSRF\n* Lack of the Secure flag on non-sensitive cookies. We provide full site SSL as a mechanism to defend against MITM (via HSTS) for sensitive session cookies.\n* Lack of HTTPOnly flag on non-sensitive cookies. We have set the HTTPOnly flag on cookies we feel are sensitive and we do not consider the lack of HTTPOnly on other cookies to be a vulnerability.\n* Vulnerabilities only affecting users of outdated or unpatched browsers and platforms\n* Any physical attempts against Zomato property or data centers\n* Issues without clearly identified security impact, such as clickjacking on a static website, missing security headers, or descriptive error messages\n* Do not test the physical security of Zomato offices, employees, equipment, etc.\n* Do not test using social engineering techniques (this includes phishing attacks against Zomato employees/contractors). Do not perform DoS or DDoS attacks.\n* Do not in any way attack our end users, or engage in the trade of stolen user credentials.\n* CSRF on `www.zomato.com/php/*` , `www.zomato.com/clients/*`\n* Promo code enumeration, abuse of our promotional offers and referral codes.\n\n###Consequences of complying with this policy\n\nWe will not pursue a civil action or initiate a complaint to law enforcement for accidental, good faith violations of this policy. We consider activities conducted consistent with this policy to constitute “authorized” conduct under the Computer Fraud and Abuse Act (CFAA). We will not bring a DMCA claim against you for circumventing the technological measures we have used to protect the applications in scope.\n\nIf legal action is initiated by a third party against you and you have complied with Zomato's bug bounty policy, Zomato will take steps to make it known that your actions were conducted in compliance with this policy.\n\nPlease submit a [HackerOne report] (https://hackerone.com/zomato) to us before engaging in conduct that may be inconsistent with or unaddressed by this policy.\n\nThank you for helping keep @Zomato safe for the community!\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":"2019-03-08T16:36:22.295Z"},{"id":3604476,"new_policy":"We take security seriously at Zomato, and we’re committed to protecting our community. If you are a security researcher or expert, and believe you’ve identified security-related issues with Zomato’s website or apps, we would appreciate you disclosing it to us responsibly. \n\nOur team is committed to addressing all security issues in a responsible and timely manner, and we ask the security community to give us the opportunity to do so before disclosing them publicly. Please submit a detailed description of the issue to us, along with the steps to reproduce it. We trust the security community to make every effort to protect our users’ data and privacy. \n\n**Disclosure Policy**\n* Let us know as soon as possible upon discovery of a potential security issue, and we'll make every effort to quickly resolve the issue.\n* Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party.\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\n**Scope**\nThe scope of issues is limited to technical vulnerabilities in the Zomato website or mobile apps. Please do not attempt to compromise the safety or privacy of our users (so please use test accounts), or the availability of Zomato through DoS attacks or spam. We also request you not to use vulnerability testing tools that generate a significant volume of traffic.\n\nCertain vulnerabilities with a working proof of concept on some of our Android mobile app(s) may qualify for an additional bounty through the [Google Play Security Rewards Program] (https://hackerone.com/googleplay). To see which apps and vulnerabilities may qualify for a bounty, please refer to the [Google Play Security Rewards Program’s Scope and Vulnerability Criteria] (https://hackerone.com/googleplay).\n\n**Bounty Program**\nWe will reward reports according to their severity on a case-by-case basis as determined by our security team. We may pay more for unique, hard-to-find bugs; we may also pay less for bugs with complex prerequisites that lower risk of exploitation.\n\nThe minimum reward for severe bugs like Remote Code Execution or User Personal Information Access is $1000 USD.\n\n**Eligibility and Responsible Disclosure**\nTo promote the discovery and reporting of vulnerabilities and increase user safety, we ask that you:\n* Give us a reasonable time to respond to the issue before making any information about it public.\n* Not access or modify data without explicit permission of the owner.\n* Act in good faith not to degrade the performance of our services (including denial of service).\n \nWe only reward the first reporter of a vulnerability. Public disclosure of the vulnerability prior to resolution will result in disqualification from the program. You must report a qualifying vulnerability through the HackerOne reporting tool to be eligible for a monetary reward.\n\n**Non-qualifying vulnerabilities / Known Issues**\n\nAlthough we review every reported issue on a case-by-case basis, some of them may not qualify depending on their impact. Here are some common low-risk issues that typically do not qualify:\n\n* Attacks requiring physical access to a user's device\n* Forms missing CSRF tokens (we require evidence of actual CSRF vulnerability)\n* Login/logout CSRF\n* Password and account recovery policies, such as reset link expiration or password complexity\n* Invalid or missing SPF (Sender Policy Framework) records\n* Content spoofing/text injection\n* Username enumeration and other similar enumeration reports\n* Self-XSS without a vector for a third party attack.\n* Issues related to software or protocols not under Zomato's control\n* Reports of spam\n* Bypass of URL malware detection\n* Best practices concerns\n* Denial of Service Attacks\n* Bruteforce Attacks\n* Spamming the users\n* Content injection issues\n* Open redirects with minimal security implications\n* Stack traces that disclose information\n* Banner grabbing issues\n* Outdated WordPress instances and plugins\n* Tab nabbing\n* Failure to implement security best practices such as rate limiting, minimum password strength, and mobile binary protection\n* Recently disclosed 0-day vulnerabilities\n* Account/e-mail enumeration\n* Results of automated tools or scanners\n* Login/logout/unauthenticated/low-impact CSRF\n* Lack of the Secure flag on non-sensitive cookies. We provide full site SSL as a mechanism to defend against MITM (via HSTS) for sensitive session cookies.\n* Lack of HTTPOnly flag on non-sensitive cookies. We have set the HTTPOnly flag on cookies we feel are sensitive and we do not consider the lack of HTTPOnly on other cookies to be a vulnerability.\n* Vulnerabilities only affecting users of outdated or unpatched browsers and platforms\n* Any physical attempts against Zomato property or data centers\n* Issues without clearly identified security impact, such as clickjacking on a static website, missing security headers, or descriptive error messages\n* Do not test the physical security of Zomato offices, employees, equipment, etc.\n* Do not test using social engineering techniques (this includes phishing attacks against Zomato employees/contractors). Do not perform DoS or DDoS attacks.\n* Do not in any way attack our end users, or engage in the trade of stolen user credentials.\n* CSRF on `www.zomato.com/php/*` , `www.zomato.com/clients/*`\n* Promo code enumeration, abuse of our promotional offers and referral codes.\n\n###Consequences of complying with this policy\n\nWe will not pursue a civil action or initiate a complaint to law enforcement for accidental, good faith violations of this policy. We consider activities conducted consistent with this policy to constitute “authorized” conduct under the Computer Fraud and Abuse Act (CFAA). We will not bring a DMCA claim against you for circumventing the technological measures we have used to protect the applications in scope.\n\nIf legal action is initiated by a third party against you and you have complied with Zomato's bug bounty policy, Zomato will take steps to make it known that your actions were conducted in compliance with this policy.\n\nPlease submit a [HackerOne report] (https://hackerone.com/zomato) to us before engaging in conduct that may be inconsistent with or unaddressed by this policy.\n\nThank you for helping keep @Zomato safe for the community!\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":"2019-03-07T18:56:34.593Z"},{"id":3604475,"new_policy":"We take security seriously at Zomato, and we’re committed to protecting our community. If you are a security researcher or expert, and believe you’ve identified security-related issues with Zomato’s website or apps, we would appreciate you disclosing it to us responsibly. \n\nOur team is committed to addressing all security issues in a responsible and timely manner, and we ask the security community to give us the opportunity to do so before disclosing them publicly. Please submit a detailed description of the issue to us, along with the steps to reproduce it. We trust the security community to make every effort to protect our users’ data and privacy. \n\n**Disclosure Policy**\n* Let us know as soon as possible upon discovery of a potential security issue, and we'll make every effort to quickly resolve the issue.\n* Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party.\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\n**Scope**\nThe scope of issues is limited to technical vulnerabilities in the Zomato website or mobile apps. Please do not attempt to compromise the safety or privacy of our users (so please use test accounts), or the availability of Zomato through DoS attacks or spam. We also request you not to use vulnerability testing tools that generate a significant volume of traffic.\n\nCertain vulnerabilities with a working proof of concept on some of our Android mobile app(s) may qualify for an additional bounty through the [Google Play Security Rewards Program] (https://hackerone.com/googleplay). To see which apps and vulnerabilities may qualify for a bounty, please refer to the [Google Play Security Rewards Program’s Scope and Vulnerability Criteria] (https://hackerone.com/googleplay).\n\n**Bounty Program**\nWe will reward reports according to their severity on a case-by-case basis as determined by our security team. We may pay more for unique, hard-to-find bugs; we may also pay less for bugs with complex prerequisites that lower risk of exploitation.\n\nThe minimum reward for severe bugs like Remote Code Execution or User Personal Information Access is $1000 USD.\n\n**Eligibility and Responsible Disclosure**\nTo promote the discovery and reporting of vulnerabilities and increase user safety, we ask that you:\n* Give us a reasonable time to respond to the issue before making any information about it public.\n* Not access or modify data without explicit permission of the owner.\n* Act in good faith not to degrade the performance of our services (including denial of service).\n \nWe only reward the first reporter of a vulnerability. Public disclosure of the vulnerability prior to resolution will result in disqualification from the program. You must report a qualifying vulnerability through the HackerOne reporting tool to be eligible for a monetary reward.\n\n**Non-qualifying vulnerabilities / Known Issues**\n\nAlthough we review every reported issue on a case-by-case basis, some of them may not qualify depending on their impact. Here are some common low-risk issues that typically do not qualify:\n\n* Attacks requiring physical access to a user's device\n* Forms missing CSRF tokens (we require evidence of actual CSRF vulnerability)\n* Login/logout CSRF\n* Password and account recovery policies, such as reset link expiration or password complexity\n* Invalid or missing SPF (Sender Policy Framework) records\n* Content spoofing/text injection\n* Username enumeration and other similar enumeration reports\n* Self-XSS without a vector for a third party attack.\n* Issues related to software or protocols not under Zomato's control\n* Reports of spam\n* Bypass of URL malware detection\n* Best practices concerns\n* Denial of Service Attacks\n* Bruteforce Attacks\n* Spamming the users\n* Content injection issues\n* Open redirects with minimal security implications\n* Stack traces that disclose information\n* Banner grabbing issues\n* Outdated WordPress instances and plugins\n* Tab nabbing\n* Failure to implement security best practices such as rate limiting, minimum password strength, and mobile binary protection\n* Recently disclosed 0-day vulnerabilities\n* Account/e-mail enumeration\n* Results of automated tools or scanners\n* Login/logout/unauthenticated/low-impact CSRF\n* Lack of the Secure flag on non-sensitive cookies. We provide full site SSL as a mechanism to defend against MITM (via HSTS) for sensitive session cookies.\n* Lack of HTTPOnly flag on non-sensitive cookies. We have set the HTTPOnly flag on cookies we feel are sensitive and we do not consider the lack of HTTPOnly on other cookies to be a vulnerability.\n* Vulnerabilities only affecting users of outdated or unpatched browsers and platforms\n* Any physical attempts against Zomato property or data centers\n* Issues without clearly identified security impact, such as clickjacking on a static website, missing security headers, or descriptive error messages\n* Do not test the physical security of Zomato offices, employees, equipment, etc.\n* Do not test using social engineering techniques (this includes phishing attacks against Zomato employees/contractors). Do not perform DoS or DDoS attacks.\n* Do not in any way attack our end users, or engage in the trade of stolen user credentials.\n* CSRF on `www.zomato.com/php/*` , `www.zomato.com/clients/*`\n* Promo code enumeration, abuse of our promotional offers and referral codes.\n\n###Consequences of Complying with This Policy\n\nWe will not pursue a civil action or initiate a complaint to law enforcement for accidental, good faith violations of this policy. We consider activities conducted consistent with this policy to constitute “authorized” conduct under the Computer Fraud and Abuse Act (CFAA). We will not bring a DMCA claim against you for circumventing the technological measures we have used to protect the applications in scope.\n\nIf legal action is initiated by a third party against you and you have complied with Zomato's bug bounty policy, Zomato will take steps to make it known that your actions were conducted in compliance with this policy.\n\nPlease submit a [HackerOne report] (https://hackerone.com/zomato) to us before engaging in conduct that may be inconsistent with or unaddressed by this policy.\n\nThank you for helping keep @Zomato safe for the community!\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":"2019-03-07T18:55:53.039Z"},{"id":3593771,"new_policy":"We take security seriously at Zomato, and we’re committed to protecting our community. If you are a security researcher or expert, and believe you’ve identified security-related issues with Zomato’s website or apps, we would appreciate you disclosing it to us responsibly. \n\nOur team is committed to addressing all security issues in a responsible and timely manner, and we ask the security community to give us the opportunity to do so before disclosing them publicly. Please submit a detailed description of the issue to us, along with the steps to reproduce it. We trust the security community to make every effort to protect our users’ data and privacy. \n\n**Disclosure Policy**\n* Let us know as soon as possible upon discovery of a potential security issue, and we'll make every effort to quickly resolve the issue.\n* Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party.\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 explicit permission of the account holder.\n\n**Scope**\nThe scope of issues is limited to technical vulnerabilities in the Zomato website or mobile apps. Please do not attempt to compromise the safety or privacy of our users (so please use test accounts), or the availability of Zomato through DoS attacks or spam. We also request you not to use vulnerability testing tools that generate a significant volume of traffic.\n\nCertain vulnerabilities with a working proof of concept on some of our Android mobile app(s) may qualify for an additional bounty through the [Google Play Security Rewards Program] (https://hackerone.com/googleplay). To see which apps and vulnerabilities may qualify for a bounty, please refer to the [Google Play Security Rewards Program’s Scope and Vulnerability Criteria] (https://hackerone.com/googleplay).\n\n**Bounty Program**\nWe will reward reports according to their severity on a case-by-case basis as determined by our security team. We may pay more for unique, hard-to-find bugs; we may also pay less for bugs with complex prerequisites that lower risk of exploitation.\n\nThe minimum reward for severe bugs like Remote Code Execution or User Personal Information Access is $1000 USD.\n\n**Eligibility and Responsible Disclosure**\nTo promote the discovery and reporting of vulnerabilities and increase user safety, we ask that you:\n* Give us a reasonable time to respond to the issue before making any information about it public.\n* Not access or modify data without explicit permission of the owner.\n* Act in good faith not to degrade the performance of our services (including denial of service).\n \nWe only reward the first reporter of a vulnerability. Public disclosure of the vulnerability prior to resolution will result in disqualification from the program. You must report a qualifying vulnerability through the HackerOne reporting tool to be eligible for a monetary reward.\n\n**Non-qualifying vulnerabilities / Known Issues**\n\nAlthough we review every reported issue on a case-by-case basis, some of them may not qualify depending on their impact. Here are some common low-risk issues that typically do not qualify:\n\n* Attacks requiring physical access to a user's device\n* Forms missing CSRF tokens (we require evidence of actual CSRF vulnerability)\n* Login/logout CSRF\n* Password and account recovery policies, such as reset link expiration or password complexity\n* Invalid or missing SPF (Sender Policy Framework) records\n* Content spoofing/text injection\n* Username enumeration and other similar enumeration reports\n* Self-XSS without a vector for a third party attack.\n* Issues related to software or protocols not under Zomato's control\n* Reports of spam\n* Bypass of URL malware detection\n* Best practices concerns\n* Denial of Service Attacks\n* Bruteforce Attacks\n* Spamming the users\n* Content injection issues\n* Open redirects with minimal security implications\n* Stack traces that disclose information\n* Banner grabbing issues\n* Outdated wordpress instances and plugins\n* Tab nabbing\n* Failure to implement security best practices such as rate limiting, minimum password strength, and mobile binary protection\n* Recently disclosed 0-day vulnerabilities\n* Account/e-mail enumeration\n* Results of automated tools or scanners\n* Login/logout/unauthenticated/low-impact CSRF\n* Lack of the Secure flag on non-sensitive cookies. We provide full site SSL as a mechanism to defend against MITM (via HSTS) for sensitive session cookies.\n* Lack of HTTPOnly flag on non-sensitive cookies. We have set the HTTPOnly flag on cookies we feel are sensitive and we do not consider the lack of HTTPOnly on other cookies to be a vulnerability.\n* Vulnerabilities only affecting users of outdated or unpatched browsers and platforms\n* Any physical attempts against Zomato property or data centers\n* Issues without clearly identified security impact, such as clickjacking on a static website, missing security headers, or descriptive error messages\n* Do not test the physical security of Zomato offices, employees, equipment, etc.\n* Do not test using social engineering techniques (this includes phishing attacks against Zomato employees/contractors). Do not perform DoS or DDoS attacks.\n* Do not in any way attack our end users, or engage in the trade of stolen user credentials.\n* CSRF on `www.zomato.com/php/*` , `www.zomato.com/clients/*`\n* Promo code enumeration, abuse of our promotional offers and referral codes.\n\n###Consequences of Complying with This Policy\n\nWe will not pursue civil action or initiate a complaint to law enforcement for accidental, good faith violations of this policy. We consider activities conducted consistent with this policy to constitute “authorized” conduct under the Computer Fraud and Abuse Act (CFAA). We will not bring a DMCA claim against you for circumventing the technological measures we have used to protect the applications in scope.\n\nIf legal action is initiated by a third party against you and you have complied with Zomato's bug bounty policy, Zomato will take steps to make it known that your actions were conducted in compliance with this policy.\n\nPlease submit a [HackerOne report] (https://hackerone.com/zomato) to us before engaging in conduct that may be inconsistent with or unaddressed by this policy.\n\nThank you for helping keep @Zomato safe for the community!\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":"2018-11-06T04:57:18.752Z"},{"id":3588795,"new_policy":"We take security seriously at Zomato, and we’re committed to protecting our community. If you are a security researcher or expert, and believe you’ve identified security-related issues with Zomato’s website or apps, we would appreciate you disclosing it to us responsibly. \n\nOur team is committed to addressing all security issues in a responsible and timely manner, and we ask the security community to give us the opportunity to do so before disclosing them publicly. Please submit a detailed description of the issue to us, along with the steps to reproduce it. We trust the security community to make every effort to protect our users’ data and privacy. \n\n**Disclosure Policy**\n* Let us know as soon as possible upon discovery of a potential security issue, and we'll make every effort to quickly resolve the issue.\n* Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party.\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 explicit permission of the account holder.\n\n**Scope**\nThe scope of issues is limited to technical vulnerabilities in the Zomato website or mobile apps. Please do not attempt to compromise the safety or privacy of our users (so please use test accounts), or the availability of Zomato through DoS attacks or spam. We also request you not to use vulnerability testing tools that generate a significant volume of traffic.\n\nCertain vulnerabilities with a working proof of concept on some of our Android mobile app(s) may qualify for an additional bounty through the [Google Play Security Rewards Program] (https://hackerone.com/googleplay). To see which apps and vulnerabilities may qualify for a bounty, please refer to the [Google Play Security Rewards Program’s Scope and Vulnerability Criteria] (https://hackerone.com/googleplay).\n\n**Bounty Program**\nWe will reward reports according to their severity on a case-by-case basis as determined by our security team. We may pay more for unique, hard-to-find bugs; we may also pay less for bugs with complex prerequisites that lower risk of exploitation.\n\nThe minimum reward for severe bugs like Remote Code Execution or User Personal Information Access is $1000 USD.\n\n**Eligibility and Responsible Disclosure**\nTo promote the discovery and reporting of vulnerabilities and increase user safety, we ask that you:\n* Give us a reasonable time to respond to the issue before making any information about it public.\n* Not access or modify data without explicit permission of the owner.\n* Act in good faith not to degrade the performance of our services (including denial of service).\n \nWe only reward the first reporter of a vulnerability. Public disclosure of the vulnerability prior to resolution will result in disqualification from the program. You must report a qualifying vulnerability through the HackerOne reporting tool to be eligible for a monetary reward.\n\n**Non-qualifying vulnerabilities / Known Issues**\n\nAlthough we review every reported issue on a case-by-case basis, some of them may not qualify depending on their impact. Here are some common low-risk issues that typically do not qualify:\n\n* Attacks requiring physical access to a user's device\n* Forms missing CSRF tokens (we require evidence of actual CSRF vulnerability)\n* Login/logout CSRF\n* Password and account recovery policies, such as reset link expiration or password complexity\n* Invalid or missing SPF (Sender Policy Framework) records\n* Content spoofing/text injection\n* Username enumeration and other similar enumeration reports\n* Self-XSS without a vector for a third party attack.\n* Issues related to software or protocols not under Zomato's control\n* Reports of spam\n* Bypass of URL malware detection\n* Best practices concerns\n* Denial of Service Attacks\n* Bruteforce Attacks\n* Spamming the users\n* Content injection issues\n* Open redirects with minimal security implications\n* Stack traces that disclose information\n* Banner grabbing issues\n* Outdated wordpress instances and plugins\n* Tab nabbing\n* Failure to implement security best practices such as rate limiting, minimum password strength, and mobile binary protection\n* Recently disclosed 0-day vulnerabilities\n* Account/e-mail enumeration\n* Results of automated tools or scanners\n* Login/logout/unauthenticated/low-impact CSRF\n* Lack of the Secure flag on non-sensitive cookies. We provide full site SSL as a mechanism to defend against MITM (via HSTS) for sensitive session cookies.\n* Lack of HTTPOnly flag on non-sensitive cookies. We have set the HTTPOnly flag on cookies we feel are sensitive and we do not consider the lack of HTTPOnly on other cookies to be a vulnerability.\n* Vulnerabilities only affecting users of outdated or unpatched browsers and platforms\n* Any physical attempts against Zomato property or data centers\n* Issues without clearly identified security impact, such as clickjacking on a static website, missing security headers, or descriptive error messages\n* Do not test the physical security of Zomato offices, employees, equipment, etc.\n* Do not test using social engineering techniques (this includes phishing attacks against Zomato employees/contractors). Do not perform DoS or DDoS attacks.\n* Do not in any way attack our end users, or engage in the trade of stolen user credentials.\n* CSRF on `www.zomato.com/php/*` , `www.zomato.com/clients/*`\n\n###Consequences of Complying with This Policy\n\nWe will not pursue civil action or initiate a complaint to law enforcement for accidental, good faith violations of this policy. We consider activities conducted consistent with this policy to constitute “authorized” conduct under the Computer Fraud and Abuse Act (CFAA). We will not bring a DMCA claim against you for circumventing the technological measures we have used to protect the applications in scope.\n\nIf legal action is initiated by a third party against you and you have complied with Zomato's bug bounty policy, Zomato will take steps to make it known that your actions were conducted in compliance with this policy.\n\nPlease submit a [HackerOne report] (https://hackerone.com/zomato) to us before engaging in conduct that may be inconsistent with or unaddressed by this policy.\n\nThank you for helping keep @Zomato safe for the community!\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":"2018-09-15T18:32:45.932Z"},{"id":3588684,"new_policy":"We take security seriously at Zomato, and we’re committed to protecting our community. If you are a security researcher or expert, and believe you’ve identified security-related issues with Zomato’s website or apps, we would appreciate you disclosing it to us responsibly. \n\nOur team is committed to addressing all security issues in a responsible and timely manner, and we ask the security community to give us the opportunity to do so before disclosing them publicly. Please submit a detailed description of the issue to us, along with the steps to reproduce it. We trust the security community to make every effort to protect our users’ data and privacy. \n\n**Disclosure Policy**\n* Let us know as soon as possible upon discovery of a potential security issue, and we'll make every effort to quickly resolve the issue.\n* Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party.\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 explicit permission of the account holder.\n\n**Scope**\nThe scope of issues is limited to technical vulnerabilities in the Zomato website or mobile apps. Please do not attempt to compromise the safety or privacy of our users (so please use test accounts), or the availability of Zomato through DoS attacks or spam. We also request you not to use vulnerability testing tools that generate a significant volume of traffic.\n\nCertain vulnerabilities with a working proof of concept on some of our Android mobile app(s) may qualify for an additional bounty through the [Google Play Security Rewards Program] (https://hackerone.com/googleplay). To see which apps and vulnerabilities may qualify for a bounty, please refer to the [Google Play Security Rewards Program’s Scope and Vulnerability Criteria] (https://hackerone.com/googleplay).\n\n---------------------\n###**Two Week Promotion**\n\nHey Hackers,\n\nThanks to the great reports you have submitted to us in the past. For the next two weeks, we will be awarding double bounties! Any new report that is reported between now and September 15th, 2018 will receive twice the bounty it normally would.\n\nTo encourage activity, best report received within this time period will be eligible for $2500 bonus.\n\nOut-Of-Scope / Known Design Issues:\n\nApart from the ones listed below in *Non-qualifying vulnerabilities*, here are few known issues:\n\n- Email Verification on our App(s)\n- Social Engineering, e.g. contacting support for refunds\n- Using Disposable Emails/Number to spoof identity\n- CSRF on www.zomato.com/php/*\n- traceapi.zomato.com\n- www.zomato.com/blog/*\n\nIf you have any questions, feel free to reach out to us at security@zomato.com!\n\nWe look forward to your findings! Thank you and Happy Hacking!\n\n---------------------\n\n**Bounty Program**\nWe will reward reports according to their severity on a case-by-case basis as determined by our security team. We may pay more for unique, hard-to-find bugs; we may also pay less for bugs with complex prerequisites that lower risk of exploitation.\n\nThe minimum reward for severe bugs like Remote Code Execution or User Personal Information Access is $1000 USD.\n\n**Eligibility and Responsible Disclosure**\nTo promote the discovery and reporting of vulnerabilities and increase user safety, we ask that you:\n* Give us a reasonable time to respond to the issue before making any information about it public.\n* Not access or modify data without explicit permission of the owner.\n* Act in good faith not to degrade the performance of our services (including denial of service).\n \nWe only reward the first reporter of a vulnerability. Public disclosure of the vulnerability prior to resolution will result in disqualification from the program. You must report a qualifying vulnerability through the HackerOne reporting tool to be eligible for a monetary reward.\n\n**Non-qualifying vulnerabilities / Known Issues**\n\nAlthough we review every reported issue on a case-by-case basis, some of them may not qualify depending on their impact. Here are some common low-risk issues that typically do not qualify:\n\n* Attacks requiring physical access to a user's device\n* Forms missing CSRF tokens (we require evidence of actual CSRF vulnerability)\n* Login/logout CSRF\n* Password and account recovery policies, such as reset link expiration or password complexity\n* Invalid or missing SPF (Sender Policy Framework) records\n* Content spoofing/text injection\n* Username enumeration and other similar enumeration reports\n* Self-XSS without a vector for a third party attack.\n* Issues related to software or protocols not under Zomato's control\n* Reports of spam\n* Bypass of URL malware detection\n* Best practices concerns\n* Denial of Service Attacks\n* Bruteforce Attacks\n* Spamming the users\n* Content injection issues\n* Open redirects with minimal security implications\n* Stack traces that disclose information\n* Banner grabbing issues\n* Outdated wordpress instances and plugins\n* Tab nabbing\n* Failure to implement security best practices such as rate limiting, minimum password strength, and mobile binary protection\n* Recently disclosed 0-day vulnerabilities\n* Account/e-mail enumeration\n* Results of automated tools or scanners\n* Login/logout/unauthenticated/low-impact CSRF\n* Lack of the Secure flag on non-sensitive cookies. We provide full site SSL as a mechanism to defend against MITM (via HSTS) for sensitive session cookies.\n* Lack of HTTPOnly flag on non-sensitive cookies. We have set the HTTPOnly flag on cookies we feel are sensitive and we do not consider the lack of HTTPOnly on other cookies to be a vulnerability.\n* Vulnerabilities only affecting users of outdated or unpatched browsers and platforms\n* Any physical attempts against Zomato property or data centers\n* Issues without clearly identified security impact, such as clickjacking on a static website, missing security headers, or descriptive error messages\n* Do not test the physical security of Zomato offices, employees, equipment, etc.\n* Do not test using social engineering techniques (this includes phishing attacks against Zomato employees/contractors). Do not perform DoS or DDoS attacks.\n* Do not in any way attack our end users, or engage in the trade of stolen user credentials.\n* CSRF on `www.zomato.com/php/*` , `www.zomato.com/clients/*`\n\n###Consequences of Complying with This Policy\n\nWe will not pursue civil action or initiate a complaint to law enforcement for accidental, good faith violations of this policy. We consider activities conducted consistent with this policy to constitute “authorized” conduct under the Computer Fraud and Abuse Act (CFAA). We will not bring a DMCA claim against you for circumventing the technological measures we have used to protect the applications in scope.\n\nIf legal action is initiated by a third party against you and you have complied with Zomato's bug bounty policy, Zomato will take steps to make it known that your actions were conducted in compliance with this policy.\n\nPlease submit a [HackerOne report] (https://hackerone.com/zomato) to us before engaging in conduct that may be inconsistent with or unaddressed by this policy.\n\nThank you for helping keep @Zomato safe for the community!\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":"2018-09-14T01:23:31.293Z"},{"id":3587522,"new_policy":"We take security seriously at Zomato, and we’re committed to protecting our community. If you are a security researcher or expert, and believe you’ve identified security-related issues with Zomato’s website or apps, we would appreciate you disclosing it to us responsibly. \n\nOur team is committed to addressing all security issues in a responsible and timely manner, and we ask the security community to give us the opportunity to do so before disclosing them publicly. Please submit a detailed description of the issue to us, along with the steps to reproduce it. We trust the security community to make every effort to protect our users’ data and privacy. \n\n**Disclosure Policy**\n* Let us know as soon as possible upon discovery of a potential security issue, and we'll make every effort to quickly resolve the issue.\n* Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party.\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 explicit permission of the account holder.\n\n**Scope**\nThe scope of issues is limited to technical vulnerabilities in the Zomato website or mobile apps. Please do not attempt to compromise the safety or privacy of our users (so please use test accounts), or the availability of Zomato through DoS attacks or spam. We also request you not to use vulnerability testing tools that generate a significant volume of traffic.\n\nCertain vulnerabilities with a working proof of concept on some of our Android mobile app(s) may qualify for an additional bounty through the [Google Play Security Rewards Program] (https://hackerone.com/googleplay). To see which apps and vulnerabilities may qualify for a bounty, please refer to the [Google Play Security Rewards Program’s Scope and Vulnerability Criteria] (https://hackerone.com/googleplay).\n\n---------------------\n###**Two Week Promotion**\n\nHey Hackers,\n\nThanks to the great reports you have submitted to us in the past. For the next two weeks, we will be awarding double bounties! Any new report that is reported between now and September 15th, 2018 will receive twice the bounty it normally would.\n\nTo encourage activity, best report received within this time period will be eligible for $2500 bonus.\n\nOut-Of-Scope/Known Design Issues:\n\nApart from the ones listed below in *Non-qualifying vulnerabilities*, here are few known issues:\n\n- Email Verification on our App(s)\n- Social Engineering, e.g. contacting support for refunds\n- Using Disposable Emails/Number to spoof identity\n- CSRF on www.zomato.com/php/*\n- traceapi.zomato.com\n- www.zomato.com/blog/*\n\nIf you have any questions, feel free to reach out to us at security@zomato.com!\n\nWe look forward to your findings! Thank you and Happy Hacking!\n\n---------------------\n\n**Bounty Program**\nWe will reward reports according to their severity on a case-by-case basis as determined by our security team. We may pay more for unique, hard-to-find bugs; we may also pay less for bugs with complex prerequisites that lower risk of exploitation.\n\nThe minimum reward for severe bugs like Remote Code Execution or User Personal Information Access is $1000 USD.\n\n**Eligibility and Responsible Disclosure**\nTo promote the discovery and reporting of vulnerabilities and increase user safety, we ask that you:\n* Give us a reasonable time to respond to the issue before making any information about it public.\n* Not access or modify data without explicit permission of the owner.\n* Act in good faith not to degrade the performance of our services (including denial of service).\n \nWe only reward the first reporter of a vulnerability. Public disclosure of the vulnerability prior to resolution will result in disqualification from the program. You must report a qualifying vulnerability through the HackerOne reporting tool to be eligible for a monetary reward.\n\n**Non-qualifying vulnerabilities**\nAlthough we review every reported issue on a case-by-case basis, some of them may not qualify depending on their impact. Here are some common low-risk issues that typically do not qualify:\n* Attacks requiring physical access to a user's device\n* Forms missing CSRF tokens (we require evidence of actual CSRF vulnerability)\n* Login/logout CSRF\n* Password and account recovery policies, such as reset link expiration or password complexity\n* Invalid or missing SPF (Sender Policy Framework) records\n* Content spoofing/text injection\n* Username enumeration and other similar enumeration reports\n* Self-XSS without a vector for a third party attack.\n* Issues related to software or protocols not under Zomato's control\n* Reports of spam\n* Bypass of URL malware detection\n* Best practices concerns\n* Denial of Service Attacks\n* Bruteforce Attacks\n* Spamming the users\n* Content injection issues\n* Open redirects with minimal security implications\n* Stack traces that disclose information\n* Banner grabbing issues\n* Outdated wordpress instances and plugins\n* Tab nabbing\n* Failure to implement security best practices such as rate limiting, minimum password strength, and mobile binary protection\n* Recently disclosed 0-day vulnerabilities\n* Account/e-mail enumeration\n* Results of automated tools or scanners\n* Login/logout/unauthenticated/low-impact CSRF\n* Lack of the Secure flag on non-sensitive cookies. We provide full site SSL as a mechanism to defend against MITM (via HSTS) for sensitive session cookies.\n* Lack of HTTPOnly flag on non-sensitive cookies. We have set the HTTPOnly flag on cookies we feel are sensitive and we do not consider the lack of HTTPOnly on other cookies to be a vulnerability.\n* Vulnerabilities only affecting users of outdated or unpatched browsers and platforms\n* Any physical attempts against Zomato property or data centers\n* Issues without clearly identified security impact, such as clickjacking on a static website, missing security headers, or descriptive error messages\n* Do not test the physical security of Zomato offices, employees, equipment, etc.\n* Do not test using social engineering techniques (this includes phishing attacks against Zomato employees/contractors). Do not perform DoS or DDoS attacks.\n* Do not in any way attack our end users, or engage in the trade of stolen user credentials.\n\n###Consequences of Complying with This Policy\n\nWe will not pursue civil action or initiate a complaint to law enforcement for accidental, good faith violations of this policy. We consider activities conducted consistent with this policy to constitute “authorized” conduct under the Computer Fraud and Abuse Act (CFAA). We will not bring a DMCA claim against you for circumventing the technological measures we have used to protect the applications in scope.\n\nIf legal action is initiated by a third party against you and you have complied with Zomato's bug bounty policy, Zomato will take steps to make it known that your actions were conducted in compliance with this policy.\n\nPlease submit a [HackerOne report] (https://hackerone.com/zomato) to us before engaging in conduct that may be inconsistent with or unaddressed by this policy.\n\nThank you for helping keep @Zomato safe for the community!\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":"2018-08-31T18:33:51.087Z"},{"id":3587449,"new_policy":"We take security seriously at Zomato, and we’re committed to protecting our community. If you are a security researcher or expert, and believe you’ve identified security-related issues with Zomato’s website or apps, we would appreciate you disclosing it to us responsibly. \n\nOur team is committed to addressing all security issues in a responsible and timely manner, and we ask the security community to give us the opportunity to do so before disclosing them publicly. Please submit a detailed description of the issue to us, along with the steps to reproduce it. We trust the security community to make every effort to protect our users’ data and privacy. \n\n**Disclosure Policy**\n* Let us know as soon as possible upon discovery of a potential security issue, and we'll make every effort to quickly resolve the issue.\n* Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party.\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 explicit permission of the account holder.\n\n**Scope**\nThe scope of issues is limited to technical vulnerabilities in the Zomato website or mobile apps. Please do not attempt to compromise the safety or privacy of our users (so please use test accounts), or the availability of Zomato through DoS attacks or spam. We also request you not to use vulnerability testing tools that generate a significant volume of traffic.\n\nCertain vulnerabilities with a working proof of concept on some of our Android mobile app(s) may qualify for an additional bounty through the [Google Play Security Rewards Program] (https://hackerone.com/googleplay). To see which apps and vulnerabilities may qualify for a bounty, please refer to the [Google Play Security Rewards Program’s Scope and Vulnerability Criteria] (https://hackerone.com/googleplay).\n\n---------------------\n###**Two Week Promotion**\n\nHey Hackers,\n\nThanks to the great reports you have submitted to us in the past. For the next two weeks, we will be awarding double bounties! Any new report that is reported between now and September 15th, 2018 will receive twice the bounty it normally would.\n\nTo encourage activity, best report received within this time period will be eligible for $2500 bonus.\n\nOut-Of-Scope/Known Design Issues:\n\nApart from the ones listed below in *Non-qualifying vulnerabilities*, here are few known issues:\n\n- Email Verification on our APP(s)\n- Social Engineering, e.g. contacting support for refunds\n- Using Disposable Emails/Number to spoof identity\n- CSRF on www.zomato.com/php/*\n- traceapi.zomato.com\n- www.zomato.com/blog/*\n\nIf you have any questions, feel free to reach out to us at security@zomato.com!\n\nWe look forward to your findings! Thank you and Happy Hacking!\n\n---------------------\n\n**Bounty Program**\nWe will reward reports according to their severity on a case-by-case basis as determined by our security team. We may pay more for unique, hard-to-find bugs; we may also pay less for bugs with complex prerequisites that lower risk of exploitation.\n\nThe minimum reward for severe bugs like Remote Code Execution or User Personal Information Access is $1000 USD.\n\n**Eligibility and Responsible Disclosure**\nTo promote the discovery and reporting of vulnerabilities and increase user safety, we ask that you:\n* Give us a reasonable time to respond to the issue before making any information about it public.\n* Not access or modify data without explicit permission of the owner.\n* Act in good faith not to degrade the performance of our services (including denial of service).\n \nWe only reward the first reporter of a vulnerability. Public disclosure of the vulnerability prior to resolution will result in disqualification from the program. You must report a qualifying vulnerability through the HackerOne reporting tool to be eligible for a monetary reward.\n\n**Non-qualifying vulnerabilities**\nAlthough we review every reported issue on a case-by-case basis, some of them may not qualify depending on their impact. Here are some common low-risk issues that typically do not qualify:\n* Attacks requiring physical access to a user's device\n* Forms missing CSRF tokens (we require evidence of actual CSRF vulnerability)\n* Login/logout CSRF\n* Password and account recovery policies, such as reset link expiration or password complexity\n* Invalid or missing SPF (Sender Policy Framework) records\n* Content spoofing / text injection\n* Username enumeration and other similar enumeration reports\n* Self-XSS without a vector for a third party attack.\n* Issues related to software or protocols not under Zomato's control\n* Reports of spam\n* Bypass of URL malware detection\n* Best practices concerns\n* Denial of Service Attacks\n* Bruteforce Attacks\n* Spamming the users\n* Content injection issues\n* Open redirects with minimal security implications\n* Stack traces that disclose information\n* Banner grabbing issues\n* Outdated wordpress instances and plugins\n* Tab nabbing\n* Failure to implement security best practices such as rate limiting, minimum password strength, and mobile binary protection\n* Recently disclosed 0-day vulnerabilities\n* Account/e-mail enumeration\n* Results of automated tools or scanners\n* Login/logout/unauthenticated/low-impact CSRF\n* Lack of the Secure flag on non-sensitive cookies. We provide full site SSL as a mechanism to defend against MITM (via HSTS) for sensitive session cookies.\n* Lack of HTTPOnly flag on non-sensitive cookies. We have set the HTTPOnly flag on cookies we feel are sensitive and we do not consider the lack of HTTPOnly on other cookies to be a vulnerability.\n* Vulnerabilities only affecting users of outdated or unpatched browsers and platforms\n* Any physical attempts against Zomato property or data centers\n* Issues without clearly identified security impact, such as clickjacking on a static website, missing security headers, or descriptive error messages\n* Do not test the physical security of Zomato offices, employees, equipment, etc.\n* Do not test using social engineering techniques (this includes phishing attacks against Zomato employees/contractors). Do not perform DoS or DDoS attacks.\n* Do not in any way attack our end users, or engage in the trade of stolen user credentials.\n\n###Consequences of Complying with This Policy\n\nWe will not pursue civil action or initiate a complaint to law enforcement for accidental, good faith violations of this policy. We consider activities conducted consistent with this policy to constitute “authorized” conduct under the Computer Fraud and Abuse Act (CFAA). We will not bring a DMCA claim against you for circumventing the technological measures we have used to protect the applications in scope.\n\nIf legal action is initiated by a third party against you and you have complied with Zomato's bug bounty policy, Zomato will take steps to make it known that your actions were conducted in compliance with this policy.\n\nPlease submit a [HackerOne report] (https://hackerone.com/zomato) to us before engaging in conduct that may be inconsistent with or unaddressed by this policy.\n\nThank you for helping keep @Zomato safe for the community!\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":"2018-08-31T09:41:35.290Z"},{"id":3582929,"new_policy":"We take security seriously at Zomato, and we’re committed to protecting our community. If you are a security researcher or expert, and believe you’ve identified security-related issues with Zomato’s website or apps, we would appreciate you disclosing it to us responsibly. \n\nOur team is committed to addressing all security issues in a responsible and timely manner, and we ask the security community to give us the opportunity to do so before disclosing them publicly. Please submit a detailed description of the issue to us, along with the steps to reproduce it. We trust the security community to make every effort to protect our users’ data and privacy. \n\n**Disclosure Policy**\n* Let us know as soon as possible upon discovery of a potential security issue, and we'll make every effort to quickly resolve the issue.\n* Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party.\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 explicit permission of the account holder.\n\n**Scope**\nThe scope of issues is limited to technical vulnerabilities in the Zomato website or mobile apps. Please do not attempt to compromise the safety or privacy of our users (so please use test accounts), or the availability of Zomato through DoS attacks or spam. We also request you not to use vulnerability testing tools that generate a significant volume of traffic.\n\nCertain vulnerabilities with a working proof of concept on some of our Android mobile app(s) may qualify for an additional bounty through the [Google Play Security Rewards Program] (https://hackerone.com/googleplay). To see which apps and vulnerabilities may qualify for a bounty, please refer to the [Google Play Security Rewards Program’s Scope and Vulnerability Criteria] (https://hackerone.com/googleplay).\n\n**Bounty Program**\nWe will reward reports according to their severity on a case-by-case basis as determined by our security team. We may pay more for unique, hard-to-find bugs; we may also pay less for bugs with complex prerequisites that lower risk of exploitation.\n\nThe minimum reward for severe bugs like Remote Code Execution or User Personal Information Access is $1000 USD.\n\n**Eligibility and Responsible Disclosure**\nTo promote the discovery and reporting of vulnerabilities and increase user safety, we ask that you:\n* Give us a reasonable time to respond to the issue before making any information about it public.\n* Not access or modify data without explicit permission of the owner.\n* Act in good faith not to degrade the performance of our services (including denial of service).\n \nWe only reward the first reporter of a vulnerability. Public disclosure of the vulnerability prior to resolution will result in disqualification from the program. You must report a qualifying vulnerability through the HackerOne reporting tool to be eligible for a monetary reward.\n\n**Non-qualifying vulnerabilities**\nAlthough we review every reported issue on a case-by-case basis, some of them may not qualify depending on their impact. Here are some common low-risk issues that typically do not qualify:\n* Attacks requiring physical access to a user's device\n* Forms missing CSRF tokens (we require evidence of actual CSRF vulnerability)\n* Login/logout CSRF\n* Password and account recovery policies, such as reset link expiration or password complexity\n* Invalid or missing SPF (Sender Policy Framework) records\n* Content spoofing / text injection\n* Username enumeration and other similar enumeration reports\n* Self-XSS without a vector for a third party attack.\n* Issues related to software or protocols not under Zomato's control\n* Reports of spam\n* Bypass of URL malware detection\n* Best practices concerns\n* Denial of Service Attacks\n* Bruteforce Attacks\n* Spamming the users\n* Content injection issues\n* Open redirects with minimal security implications\n* Stack traces that disclose information\n* Banner grabbing issues\n* Outdated wordpress instances and plugins\n* Tab nabbing\n* Failure to implement security best practices such as rate limiting, minimum password strength, and mobile binary protection\n* Recently disclosed 0-day vulnerabilities\n* Account/e-mail enumeration\n* Results of automated tools or scanners\n* Login/logout/unauthenticated/low-impact CSRF\n* Lack of the Secure flag on non-sensitive cookies. We provide full site SSL as a mechanism to defend against MITM (via HSTS) for sensitive session cookies.\n* Lack of HTTPOnly flag on non-sensitive cookies. We have set the HTTPOnly flag on cookies we feel are sensitive and we do not consider the lack of HTTPOnly on other cookies to be a vulnerability.\n* Vulnerabilities only affecting users of outdated or unpatched browsers and platforms\n* Any physical attempts against Zomato property or data centers\n* Issues without clearly identified security impact, such as clickjacking on a static website, missing security headers, or descriptive error messages\n* Do not test the physical security of Zomato offices, employees, equipment, etc.\n* Do not test using social engineering techniques (this includes phishing attacks against Zomato employees/contractors). Do not perform DoS or DDoS attacks.\n* Do not in any way attack our end users, or engage in the trade of stolen user credentials.\n\n###Consequences of Complying with This Policy\n\nWe will not pursue civil action or initiate a complaint to law enforcement for accidental, good faith violations of this policy. We consider activities conducted consistent with this policy to constitute “authorized” conduct under the Computer Fraud and Abuse Act (CFAA). We will not bring a DMCA claim against you for circumventing the technological measures we have used to protect the applications in scope.\n\nIf legal action is initiated by a third party against you and you have complied with Zomato's bug bounty policy, Zomato will take steps to make it known that your actions were conducted in compliance with this policy.\n\nPlease submit a [HackerOne report] (https://hackerone.com/zomato) to us before engaging in conduct that may be inconsistent with or unaddressed by this policy.\n\nThank you for helping keep @Zomato safe for the community!\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":"2018-07-18T03:56:25.181Z"},{"id":3579055,"new_policy":"We take security seriously at Zomato, and we’re committed to protecting our community. If you are a security researcher or expert, and believe you’ve identified security-related issues with Zomato’s website or apps, we would appreciate you disclosing it to us responsibly. \n\nOur team is committed to addressing all security issues in a responsible and timely manner, and we ask the security community to give us the opportunity to do so before disclosing them publicly. Please submit a detailed description of the issue to us, along with the steps to reproduce it. We trust the security community to make every effort to protect our users’ data and privacy. \n\n**Disclosure Policy**\n* Let us know as soon as possible upon discovery of a potential security issue, and we'll make every effort to quickly resolve the issue.\n* Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party.\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 explicit permission of the account holder.\n\n**Scope**\nThe scope of issues is limited to technical vulnerabilities in the Zomato website or mobile apps. Please do not attempt to compromise the safety or privacy of our users (so please use test accounts), or the availability of Zomato through DoS attacks or spam. We also request you not to use vulnerability testing tools that generate a significant volume of traffic. \n\n**Bounty Program**\nWe will reward reports according to their severity on a case-by-case basis as determined by our security team. We may pay more for unique, hard-to-find bugs; we may also pay less for bugs with complex prerequisites that lower risk of exploitation.\n\nThe minimum reward for severe bugs like Remote Code Execution or User Personal Information Access is $1000 USD.\n\n**We give out bounties from the previous week's resolved reports on Mondays.**\n\n**Eligibility and Responsible Disclosure**\nTo promote the discovery and reporting of vulnerabilities and increase user safety, we ask that you:\n* Give us a reasonable time to respond to the issue before making any information about it public.\n* Not access or modify data without explicit permission of the owner.\n* Act in good faith not to degrade the performance of our services (including denial of service).\n \nWe only reward the first reporter of a vulnerability. Public disclosure of the vulnerability prior to resolution will result in disqualification from the program. You must report a qualifying vulnerability through the HackerOne reporting tool to be eligible for a monetary reward.\n\n**Non-qualifying vulnerabilities**\nAlthough we review every reported issue on a case-by-case basis, some of them may not qualify depending on their impact. Here are some common low-risk issues that typically do not qualify:\n* Attacks requiring physical access to a user's device\n* Forms missing CSRF tokens (we require evidence of actual CSRF vulnerability)\n* Login/logout CSRF\n* Password and account recovery policies, such as reset link expiration or password complexity\n* Invalid or missing SPF (Sender Policy Framework) records\n* Content spoofing / text injection\n* Username enumeration and other similar enumeration reports\n* Self-XSS without a vector for a third party attack.\n* Issues related to software or protocols not under Zomato's control\n* Reports of spam\n* Bypass of URL malware detection\n* Best practices concerns\n* Denial of Service Attacks\n* Bruteforce Attacks\n* Spamming the users\n* Content injection issues\n* Open redirects with minimal security implications\n* Stack traces that disclose information\n* Banner grabbing issues\n* Outdated wordpress instances and plugins\n* Tab nabbing\n* Failure to implement security best practices such as rate limiting, minimum password strength, and mobile binary protection\n* Recently disclosed 0-day vulnerabilities\n* Account/e-mail enumeration\n* Results of automated tools or scanners\n* Login/logout/unauthenticated/low-impact CSRF\n* Lack of the Secure flag on non-sensitive cookies. We provide full site SSL as a mechanism to defend against MITM (via HSTS) for sensitive session cookies.\n* Lack of HTTPOnly flag on non-sensitive cookies. We have set the HTTPOnly flag on cookies we feel are sensitive and we do not consider the lack of HTTPOnly on other cookies to be a vulnerability.\n* Vulnerabilities only affecting users of outdated or unpatched browsers and platforms\n* Any physical attempts against Zomato property or data centers\n* Issues without clearly identified security impact, such as clickjacking on a static website, missing security headers, or descriptive error messages\n* Do not test the physical security of Zomato offices, employees, equipment, etc.\n* Do not test using social engineering techniques (this includes phishing attacks against Zomato employees/contractors). Do not perform DoS or DDoS attacks.\n* Do not in any way attack our end users, or engage in the trade of stolen user credentials.\n\n###Consequences of Complying with This Policy\n\nWe will not pursue civil action or initiate a complaint to law enforcement for accidental, good faith violations of this policy. We consider activities conducted consistent with this policy to constitute “authorized” conduct under the Computer Fraud and Abuse Act (CFAA). We will not bring a DMCA claim against you for circumventing the technological measures we have used to protect the applications in scope.\n\nIf legal action is initiated by a third party against you and you have complied with Zomato's bug bounty policy, Zomato will take steps to make it known that your actions were conducted in compliance with this policy.\n\nPlease submit a [HackerOne report] (https://hackerone.com/zomato) to us before engaging in conduct that may be inconsistent with or unaddressed by this policy.\n\nThank you for helping keep @Zomato safe for the community!\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":"2018-06-02T10:57:23.580Z"},{"id":3578383,"new_policy":"We take security seriously at Zomato, and we’re committed to protecting our community. If you are a security researcher or expert, and believe you’ve identified security-related issues with Zomato’s website or apps, we would appreciate you disclosing it to us responsibly. \n\nOur team is committed to addressing all security issues in a responsible and timely manner, and we ask the security community to give us the opportunity to do so before disclosing them publicly. Please submit a detailed description of the issue to us, along with the steps to reproduce it. We trust the security community to make every effort to protect our users’ data and privacy. \n\n**Disclosure Policy**\n* Let us know as soon as possible upon discovery of a potential security issue, and we'll make every effort to quickly resolve the issue.\n* Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party.\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 explicit permission of the account holder.\n\n**Scope**\nThe scope of issues is limited to technical vulnerabilities in the Zomato website or mobile apps. Please do not attempt to compromise the safety or privacy of our users (so please use test accounts), or the availability of Zomato through DoS attacks or spam. We also request you not to use vulnerability testing tools that generate a significant volume of traffic. \n\n**Bounty Program**\nWe will reward reports according to their severity on a case-by-case basis as determined by our security team. We may pay more for unique, hard-to-find bugs; we may also pay less for bugs with complex prerequisites that lower risk of exploitation.\n\nThe minimum reward for severe bugs like Remote Code Execution or User Personal Information Access is $1000 USD.\n\n**We give out bounties from the previous week's resolved reports on Mondays.**\n\n**Eligibility and Responsible Disclosure**\nTo promote the discovery and reporting of vulnerabilities and increase user safety, we ask that you:\n* Give us a reasonable time to respond to the issue before making any information about it public.\n* Not access or modify data without explicit permission of the owner.\n* Act in good faith not to degrade the performance of our services (including denial of service).\n \nWe only reward the first reporter of a vulnerability. Public disclosure of the vulnerability prior to resolution will result in disqualification from the program. You must report a qualifying vulnerability through the HackerOne reporting tool to be eligible for a monetary reward.\n\n**Non-qualifying vulnerabilities**\nAlthough we review every reported issue on a case-by-case basis, some of them may not qualify depending on their impact. Here are some common low-risk issues that typically do not qualify:\n* Attacks requiring physical access to a user's device\n* Forms missing CSRF tokens (we require evidence of actual CSRF vulnerability)\n* Login/logout CSRF\n* Password and account recovery policies, such as reset link expiration or password complexity\n* Invalid or missing SPF (Sender Policy Framework) records\n* Content spoofing / text injection\n* Username enumeration and other similar enumeration reports\n* Self-XSS without a vector for a third party attack.\n* Issues related to software or protocols not under Zomato's control\n* Reports of spam\n* Bypass of URL malware detection\n* Best practices concerns\n* Denial of Service Attacks\n* Bruteforce Attacks\n* Spamming the users\n* Content injection issues\n* Open redirects with minimal security implications\n* Stack traces that disclose information\n* Banner grabbing issues\n* Outdated wordpress instances and plugins\n* Tab nabbing\n* Failure to implement security best practices such as rate limiting, minimum password strength, and mobile binary protection\n* Recently disclosed 0-day vulnerabilities\n* Account/e-mail enumeration\n* Results of automated tools or scanners\n* Login/logout/unauthenticated/low-impact CSRF\n* Lack of the Secure flag on non-sensitive cookies. We provide full site SSL as a mechanism to defend against MITM (via HSTS) for sensitive session cookies.\n* Lack of HTTPOnly flag on non-sensitive cookies. We have set the HTTPOnly flag on cookies we feel are sensitive and we do not consider the lack of HTTPOnly on other cookies to be a vulnerability.\n* Vulnerabilities only affecting users of outdated or unpatched browsers and platforms\n* Any physical attempts against Zomato property or data centers\n* Issues without clearly identified security impact, such as clickjacking on a static website, missing security headers, or descriptive error messages\n* Do not test the physical security of Zomato offices, employees, equipment, etc.\n* Do not test using social engineering techniques (this includes phishing attacks against Zomato employees/contractors). Do not perform DoS or DDoS attacks.\n* Do not in any way attack our end users, or engage in the trade of stolen user credentials.\n\n###Consequences of Complying with This Policy\n\nWe will not pursue civil action or initiate a complaint to law enforcement for accidental, good faith violations of this policy. We consider activities conducted consistent with this policy to constitute “authorized” conduct under the Computer Fraud and Abuse Act (CFAA).\n\nIf legal action is initiated by a third party against you and you have complied with Zomato's bug bounty policy, Zomato will take steps to make it known that your actions were conducted in compliance with this policy.\n\nPlease submit a [HackerOne report] (https://hackerone.com/zomato) to us before engaging in conduct that may be inconsistent with or unaddressed by this policy.\n\nThank you for helping keep @Zomato safe for the community!\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":"2018-06-01T05:55:42.896Z"},{"id":3557143,"new_policy":"We take security seriously at Zomato, and we’re committed to protecting our community. If you are a security researcher or expert, and believe you’ve identified security-related issues with Zomato’s website or apps, we would appreciate you disclosing it to us responsibly. \n\nOur team is committed to addressing all security issues in a responsible and timely manner, and we ask the security community to give us the opportunity to do so before disclosing them publicly. Please submit a detailed description of the issue to us, along with the steps to reproduce it. We trust the security community to make every effort to protect our users’ data and privacy. \n\n**Disclosure Policy**\n* Let us know as soon as possible upon discovery of a potential security issue, and we'll make every effort to quickly resolve the issue.\n* Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party.\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 explicit permission of the account holder.\n\n**Scope**\nThe scope of issues is limited to technical vulnerabilities in the Zomato website or mobile apps. Please do not attempt to compromise the safety or privacy of our users (so please use test accounts), or the availability of Zomato through DoS attacks or spam. We also request you not to use vulnerability testing tools that generate a significant volume of traffic. \n\n**Bounty Program**\nWe will reward reports according to their severity on a case-by-case basis as determined by our security team. We may pay more for unique, hard-to-find bugs; we may also pay less for bugs with complex prerequisites that lower risk of exploitation.\n\nThe minimum reward for severe bugs like Remote Code Execution or User Personal Information Access is $1000 USD.\n\n**We give out bounties from the previous week's resolved reports on Mondays.**\n\n**Eligibility and Responsible Disclosure**\nTo promote the discovery and reporting of vulnerabilities and increase user safety, we ask that you:\n* Give us a reasonable time to respond to the issue before making any information about it public.\n* Not access or modify data without explicit permission of the owner.\n* Act in good faith not to degrade the performance of our services (including denial of service).\n \nWe only reward the first reporter of a vulnerability. Public disclosure of the vulnerability prior to resolution will result in disqualification from the program. You must report a qualifying vulnerability through the HackerOne reporting tool to be eligible for a monetary reward.\n\n**Non-qualifying vulnerabilities**\nAlthough we review every reported issue on a case-by-case basis, some of them may not qualify depending on their impact. Here are some common low-risk issues that typically do not qualify:\n* Attacks requiring physical access to a user's device\n* Forms missing CSRF tokens (we require evidence of actual CSRF vulnerability)\n* Login/logout CSRF\n* Password and account recovery policies, such as reset link expiration or password complexity\n* Invalid or missing SPF (Sender Policy Framework) records\n* Content spoofing / text injection\n* Username enumeration and other similar enumeration reports\n* Self-XSS without a vector for a third party attack.\n* Issues related to software or protocols not under Zomato's control\n* Reports of spam\n* Bypass of URL malware detection\n* Best practices concerns\n* Denial of Service Attacks\n* Bruteforce Attacks\n* Spamming the users\n* Content injection issues\n* Open redirects with minimal security implications\n* Stack traces that disclose information\n* Banner grabbing issues\n* Outdated wordpress instances and plugins\n* Tab nabbing\n* Failure to implement security best practices such as rate limiting, minimum password strength, and mobile binary protection\n* Recently disclosed 0-day vulnerabilities\n* Account/e-mail enumeration\n* Results of automated tools or scanners\n* Login/logout/unauthenticated/low-impact CSRF\n* Lack of the Secure flag on non-sensitive cookies. We provide full site SSL as a mechanism to defend against MITM (via HSTS) for sensitive session cookies.\n* Lack of HTTPOnly flag on non-sensitive cookies. We have set the HTTPOnly flag on cookies we feel are sensitive and we do not consider the lack of HTTPOnly on other cookies to be a vulnerability.\n* Vulnerabilities only affecting users of outdated or unpatched browsers and platforms\n* Any physical attempts against Zomato property or data centers\n* Issues without clearly identified security impact, such as clickjacking on a static website, missing security headers, or descriptive error messages\n* Do not test the physical security of Zomato offices, employees, equipment, etc.\n* Do not test using social engineering techniques (this includes phishing attacks against Zomato employees/contractors). Do not perform DoS or DDoS attacks.\n* Do not in any way attack our end users, or engage in the trade of stolen user credentials.\n\nThank you for helping keep Zomato safe for the community!\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":"2017-07-08T15:55:57.330Z"},{"id":3557088,"new_policy":"We take security seriously at Zomato, and we’re committed to protecting our community. If you are a security researcher or expert, and believe you’ve identified security-related issues with Zomato’s website or apps, we would appreciate you disclosing it to us responsibly. \n\nOur team is committed to addressing all security issues in a responsible and timely manner, and we ask the security community to give us the opportunity to do so before disclosing them publicly. Please submit a detailed description of the issue to us, along with the steps to reproduce it. We trust the security community to make every effort to protect our users’ data and privacy. \n\n**Disclosure Policy**\n* Let us know as soon as possible upon discovery of a potential security issue, and we'll make every effort to quickly resolve the issue.\n* Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party.\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 explicit permission of the account holder.\n\n**Scope**\nThe scope of issues is limited to technical vulnerabilities in the Zomato website or mobile apps. Please do not attempt to compromise the safety or privacy of our users (so please use test accounts), or the availability of Zomato through DoS attacks or spam. We also request you not to use vulnerability testing tools that generate a significant volume of traffic. \n\n**Bounty Program**\nWe will reward reports according to their severity on a case-by-case basis as determined by our security team. We may pay more for unique, hard-to-find bugs; we may also pay less for bugs with complex prerequisites that lower risk of exploitation.\n\nThe minimum reward for severe bugs like Remote Code Execution or User Personal Information Access is $1000 USD.\n\n**We give out bounties from the previous week's resolved reports on Mondays.**\n\n**Eligibility and Responsible Disclosure**\nTo promote the discovery and reporting of vulnerabilities and increase user safety, we ask that you:\n* Give us a reasonable time to respond to the issue before making any information about it public.\n* Not access or modify data without explicit permission of the owner.\n* Act in good faith not to degrade the performance of our services (including denial of service).\n \nWe only reward the first reporter of a vulnerability. Public disclosure of the vulnerability prior to resolution will result in disqualification from the program. You must report a qualifying vulnerability through the HackerOne reporting tool to be eligible for a monetary reward.\n\n**Non-qualifying vulnerabilities**\nAlthough we review every reported issue on a case-by-case basis, some of them may not qualify depending on their impact. Here are some common low-risk issues that typically do not qualify:\n* Attacks requiring physical access to a user's device\n* Forms missing CSRF tokens (we require evidence of actual CSRF vulnerability)\n* Login/logout CSRF\n* Password and account recovery policies, such as reset link expiration or password complexity\n* Invalid or missing SPF (Sender Policy Framework) records\n* Content spoofing / text injection\n* Username enumeration and other similar enumeration reports\n* Self-XSS without a vector for a third party attack.\n* Issues related to software or protocols not under Zomato's control\n* Reports of spam\n* Bypass of URL malware detection\n* Best practices concerns\n* Denial of Service Attacks\n* Bruteforce Attacks\n* Spamming the users\n* Content injection issues\n* Open redirects with minimal security implications\n* Stack traces that disclose information\n* Banner grabbing issues\n* Outdated wordpress instances and plugins\n* Tab nabbing\n* Failure to implement security best practices such as rate limiting, minimum password strength, and mobile binary protection\n* Recently disclosed 0-day vulnerabilities\n* Account/e-mail enumeration\n* Results of automated tools or scanners\n* Login/logout/unauthenticated/low-impact CSRF\n* Lack of the Secure flag on non-sensitive cookies. We provide full site SSL as a mechanism to defend against MITM (via HSTS) for sensitive session cookies.\n* Lack of HTTPOnly flag on non-sensitive cookies. We have set the HTTPOnly flag on cookies we feel are sensitive and we do not consider the lack of HTTPOnly on other cookies to be a vulnerability.\n* Vulnerabilities only affecting users of outdated or unpatched browsers and platforms\n* Any physical attempts against Zomato property or data centers\n* Issues without clearly identified security impact, such as clickjacking on a static website, missing security headers, or descriptive error messages\n\nThank you for helping keep Zomato safe for the community!\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":"2017-07-07T10:12:56.661Z"},{"id":3556700,"new_policy":"We take security seriously at Zomato, and we’re committed to protecting our community. If you are a security researcher or expert, and believe you’ve identified security-related issues with Zomato’s website or apps, we would appreciate you disclosing it to us responsibly. \n\nOur team is committed to addressing all security issues in a responsible and timely manner, and we ask the security community to give us the opportunity to do so before disclosing them publicly. Please submit a detailed description of the issue to us, along with the steps to reproduce it. We trust the security community to make every effort to protect our users’ data and privacy. \n\n**Disclosure Policy**\n* Let us know as soon as possible upon discovery of a potential security issue, and we'll make every effort to quickly resolve the issue.\n* Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party.\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 explicit permission of the account holder.\n\n**Scope**\nThe scope of issues is limited to technical vulnerabilities in the Zomato website or mobile apps. Please do not attempt to compromise the safety or privacy of our users (so please use test accounts), or the availability of Zomato through DoS attacks or spam. We also request you not to use vulnerability testing tools that generate a significant volume of traffic. \n\n**Bounty Program**\nWe will reward reports according to their severity on a case-by-case basis as determined by our security team. We may pay more for unique, hard-to-find bugs; we may also pay less for bugs with complex prerequisites that lower risk of exploitation.\n\nThe minimum reward for severe bugs like Remote Code Execution or User Personal Information Access is $1000 USD.\n\n**Eligibility and Responsible Disclosure**\nTo promote the discovery and reporting of vulnerabilities and increase user safety, we ask that you:\n* Give us a reasonable time to respond to the issue before making any information about it public.\n* Not access or modify data without explicit permission of the owner.\n* Act in good faith not to degrade the performance of our services (including denial of service).\n \nWe only reward the first reporter of a vulnerability. Public disclosure of the vulnerability prior to resolution will result in disqualification from the program. You must report a qualifying vulnerability through the HackerOne reporting tool to be eligible for a monetary reward.\n\n**Non-qualifying vulnerabilities**\nAlthough we review every reported issue on a case-by-case basis, some of them may not qualify depending on their impact. Here are some common low-risk issues that typically do not qualify:\n* Attacks requiring physical access to a user's device\n* Forms missing CSRF tokens (we require evidence of actual CSRF vulnerability)\n* Login/logout CSRF\n* Password and account recovery policies, such as reset link expiration or password complexity\n* Invalid or missing SPF (Sender Policy Framework) records\n* Content spoofing / text injection\n* Username enumeration and other similar enumeration reports\n* Self-XSS without a vector for a third party attack.\n* Issues related to software or protocols not under Zomato's control\n* Reports of spam\n* Bypass of URL malware detection\n* Best practices concerns\n* Denial of Service Attacks\n* Bruteforce Attacks\n* Spamming the users\n* Content injection issues\n* Open redirects with minimal security implications\n* Stack traces that disclose information\n* Banner grabbing issues\n* Outdated wordpress instances and plugins\n* Tab nabbing\n* Failure to implement security best practices such as rate limiting, minimum password strength, and mobile binary protection\n* Recently disclosed 0-day vulnerabilities\n* Account/e-mail enumeration\n* Results of automated tools or scanners\n* Login/logout/unauthenticated/low-impact CSRF\n* Lack of the Secure flag on non-sensitive cookies. We provide full site SSL as a mechanism to defend against MITM (via HSTS) for sensitive session cookies.\n* Lack of HTTPOnly flag on non-sensitive cookies. We have set the HTTPOnly flag on cookies we feel are sensitive and we do not consider the lack of HTTPOnly on other cookies to be a vulnerability.\n* Vulnerabilities only affecting users of outdated or unpatched browsers and platforms\n* Any physical attempts against Zomato property or data centers\n* Issues without clearly identified security impact, such as clickjacking on a static website, missing security headers, or descriptive error messages\n\nThank you for helping keep Zomato safe for the community!\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":"2017-07-01T02:02:08.245Z"},{"id":3556480,"new_policy":"We take security seriously at Zomato, and we’re committed to protecting our community. If you are a security researcher or expert, and believe you’ve identified security-related issues with Zomato’s website or apps, we would appreciate you disclosing it to us responsibly. \n\nOur team is committed to addressing all security issues in a responsible and timely manner, and we ask the security community to give us the opportunity to do so before disclosing them publicly. Please submit a detailed description of the issue to us, along with the steps to reproduce it. We trust the security community to make every effort to protect our users’ data and privacy. \n\n**Disclosure Policy**\n* Let us know as soon as possible upon discovery of a potential security issue, and we'll make every effort to quickly resolve the issue.\n* Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party.\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 explicit permission of the account holder.\n\n**Scope**\nThe scope of issues is limited to technical vulnerabilities in the Zomato website or mobile apps. Please do not attempt to compromise the safety or privacy of our users (so please use test accounts), or the availability of Zomato through DoS attacks or spam. We also request you not to use vulnerability testing tools that generate a significant volume of traffic. \n\n**Bounty Program**\nWe will reward reports according to their severity on a case-by-case basis as determined by our security team. We may pay more for unique, hard-to-find bugs; we may also pay less for bugs with complex prerequisites that lower risk of exploitation.\n\nThe minimum reward for severe bugs like Remote Code Execution or User Personal Information Access is $1000 USD.\n\n**Eligibility and Responsible Disclosure**\nTo promote the discovery and reporting of vulnerabilities and increase user safety, we ask that you:\n* Give us a reasonable time to respond to the issue before making any information about it public.\n* Not access or modify data without explicit permission of the owner.\n* Act in good faith not to degrade the performance of our services (including denial of service).\n \nWe only reward the first reporter of a vulnerability. Public disclosure of the vulnerability prior to resolution will result in disqualification from the program. You must report a qualifying vulnerability through the HackerOne reporting tool to be eligible for a monetary reward.\n\n**Non-qualifying vulnerabilities**\nAlthough we review every reported issue on a case-by-case basis, some of them may not qualify depending on their impact. Here are some common low-risk issues that typically do not qualify:\n* Attacks requiring physical access to a user's device\n* Forms missing CSRF tokens (we require evidence of actual CSRF vulnerability)\n* Login/logout CSRF\n* Password and account recovery policies, such as reset link expiration or password complexity\n* Invalid or missing SPF (Sender Policy Framework) records\n* Content spoofing / text injection\n* Username enumeration and other similar enumeration reports\n* Self-XSS without a vector for a third party attack.\n* Issues related to software or protocols not under Zomato's control\n* Reports of spam\n* Bypass of URL malware detection\n* Lack of the Secure flag on non-sensitive cookies. We provide full site SSL as a mechanism to defend against MITM (via HSTS) for sensitive session cookies.\n* Lack of HTTPOnly flag on non-sensitive cookies. We have set the HTTPOnly flag on cookies we feel are sensitive and we do not consider the lack of HTTPOnly on other cookies to be a vulnerability.\n* Vulnerabilities only affecting users of outdated or unpatched browsers and platforms\n* Any physical attempts against Zomato property or data centers\n* Issues without clearly identified security impact, such as clickjacking on a static website, missing security headers, or descriptive error messages\n\nThank you for helping keep Zomato safe for the community!\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":"2017-06-28T05:29:14.537Z"},{"id":3556479,"new_policy":"We take security seriously at Zomato, and we’re committed to protecting our community. If you are a security researcher or expert, and believe you’ve identified security-related issues with Zomato’s website or apps, we would appreciate you disclosing it to us responsibly. \n\nOur team is committed to addressing all security issues in a responsible and timely manner, and we ask the security community to give us the opportunity to do so before disclosing them publicly. Please submit a detailed description of the issue to us, along with the steps to reproduce it. We trust the security community to make every effort to protect our users’ data and privacy. \n\n**Disclosure Policy**\n* Let us know as soon as possible upon discovery of a potential security issue, and we'll make every effort to quickly resolve the issue.\n* Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party.\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 explicit permission of the account holder.\n\n**Scope**\nThe scope of issues is limited to technical vulnerabilities in the Zomato website or mobile apps. Please do not attempt to compromise the safety or privacy of our users (so please use test accounts), or the availability of Zomato through DoS attacks or spam. We also request you not to use vulnerability testing tools that generate a significant volume of traffic. \n\n**Bounty Program**\nWe will reward reports according to their severity on a case-by-case basis as determined by our security team. We may pay more for unique, hard-to-find bugs; we may also pay less for bugs with complex prerequisites that lower risk of exploitation.\n\nThe minimum reward for severe bugs like Remote Code Execution or User Personal Information Access is $1000 USD.\n\n**Non-qualifying vulnerabilities**\nAlthough we review every reported issue on a case-by-case basis, some of them may not qualify depending on their impact. Here are some common low-risk issues that typically do not qualify:\n* Attacks requiring physical access to a user's device\n* Forms missing CSRF tokens (we require evidence of actual CSRF vulnerability)\n* Login/logout CSRF\n* Password and account recovery policies, such as reset link expiration or password complexity\n* Invalid or missing SPF (Sender Policy Framework) records\n* Content spoofing / text injection\n* Username enumeration and other similar enumeration reports\n* Self-XSS without a vector for a third party attack.\n* Issues related to software or protocols not under Zomato's control\n* Reports of spam\n* Bypass of URL malware detection\n* Lack of the Secure flag on non-sensitive cookies. We provide full site SSL as a mechanism to defend against MITM (via HSTS) for sensitive session cookies.\n* Lack of HTTPOnly flag on non-sensitive cookies. We have set the HTTPOnly flag on cookies we feel are sensitive and we do not consider the lack of HTTPOnly on other cookies to be a vulnerability.\n* Vulnerabilities only affecting users of outdated or unpatched browsers and platforms\n* Any physical attempts against Zomato property or data centers\n* Issues without clearly identified security impact, such as clickjacking on a static website, missing security headers, or descriptive error messages\n\nThank you for helping keep Zomato safe for the community!\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":"2017-06-28T04:47:02.012Z"},{"id":3556478,"new_policy":"We take security seriously at Zomato, and we’re committed to protecting our community. If you are a security researcher or expert, and believe you’ve identified security-related issues with Zomato’s website or apps, we would appreciate you disclosing it to us responsibly. \n\nOur team is committed to addressing all security issues in a responsible and timely manner, and we ask the security community to give us the opportunity to do so before disclosing them publicly. Please submit a detailed description of the issue to us, along with the steps to reproduce it. We trust the security community to make every effort to protect our users’ data and privacy. \n\n**Disclosure Policy**\n* Let us know as soon as possible upon discovery of a potential security issue, and we'll make every effort to quickly resolve the issue.\n* Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party.\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 explicit permission of the account holder.\n\n**Scope**\nThe scope of issues is limited to technical vulnerabilities in the Zomato website or mobile apps. Please do not attempt to compromise the safety or privacy of our users (so please use test accounts), or the availability of Zomato through DoS attacks or spam. We also request you not to use vulnerability testing tools that generate a significant volume of traffic. \n\n**Bounty Program**\nWe do not currently have a monetary bug bounty programme, but any report that results in a change will at minimum receive Hall of Fame recognition. We would also be more than happy to provide a certificate of acknowledgement. \n\n**Non-qualifying vulnerabilities**\nAlthough we review every reported issue on a case-by-case basis, some of them may not qualify depending on their impact. Here are some common low-risk issues that typically do not qualify:\n* Attacks requiring physical access to a user's device\n* Forms missing CSRF tokens (we require evidence of actual CSRF vulnerability)\n* Login/logout CSRF\n* Password and account recovery policies, such as reset link expiration or password complexity\n* Invalid or missing SPF (Sender Policy Framework) records\n* Content spoofing / text injection\n* Username enumeration and other similar enumeration reports\n* Self-XSS without a vector for a third party attack.\n* Issues related to software or protocols not under Zomato's control\n* Reports of spam\n* Bypass of URL malware detection\n* Lack of the Secure flag on non-sensitive cookies. We provide full site SSL as a mechanism to defend against MITM (via HSTS) for sensitive session cookies.\n* Lack of HTTPOnly flag on non-sensitive cookies. We have set the HTTPOnly flag on cookies we feel are sensitive and we do not consider the lack of HTTPOnly on other cookies to be a vulnerability.\n* Vulnerabilities only affecting users of outdated or unpatched browsers and platforms\n* Any physical attempts against Zomato property or data centers\n* Issues without clearly identified security impact, such as clickjacking on a static website, missing security headers, or descriptive error messages\n\nThank you for helping keep Zomato safe for the community!\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":"2017-06-28T04:33:42.755Z"},{"id":3556477,"new_policy":"We take security seriously at Zomato, and we’re committed to protecting our community. If you are a security researcher or expert, and believe you’ve identified security-related issues with Zomato’s website or apps, we would appreciate you disclosing it to us responsibly. \n\nOur team is committed to addressing all security issues in a responsible and timely manner, and we ask the security community to give us the opportunity to do so before disclosing them publicly. Please submit a detailed description of the issue to us, along with the steps to reproduce it. We trust the security community to make every effort to protect our users’ data and privacy. \n\n# Disclosure Policy\n* Let us know as soon as possible upon discovery of a potential security issue, and we'll make every effort to quickly resolve the issue.\n* Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party.\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 explicit permission of the account holder.\n\n#Scope\nThe scope of issues is limited to technical vulnerabilities in the Zomato website or mobile apps. Please do not attempt to compromise the safety or privacy of our users (so please use test accounts), or the availability of Zomato through DoS attacks or spam. We also request you not to use vulnerability testing tools that generate a significant volume of traffic. \n\n# Bounty Program\nWe do not currently have a monetary bug bounty programme, but any report that results in a change will at minimum receive Hall of Fame recognition. We would also be more than happy to provide a certificate of acknowledgement. \n\n# Non-qualifying vulnerabilities\nAlthough we review every reported issue on a case-by-case basis, some of them may not qualify depending on their impact. Here are some common low-risk issues that typically do not qualify:\nAttacks requiring physical access to a user's device\nForms missing CSRF tokens (we require evidence of actual CSRF vulnerability)\nLogin/logout CSRF\nPassword and account recovery policies, such as reset link expiration or password complexity\nInvalid or missing SPF (Sender Policy Framework) records\nContent spoofing / text injection\nUsername enumeration and other similar enumeration reports\nSelf-XSS without a vector for a third party attack.\nIssues related to software or protocols not under Zomato's control\nReports of spam\nBypass of URL malware detection\nLack of the Secure flag on non-sensitive cookies. We provide full site SSL as a mechanism to defend against MITM (via HSTS) for sensitive session cookies.\nLack of HTTPOnly flag on non-sensitive cookies. We have set the HTTPOnly flag on cookies we feel are sensitive and we do not consider the lack of HTTPOnly on other cookies to be a vulnerability.\nVulnerabilities only affecting users of outdated or unpatched browsers and platforms\nAny physical attempts against Zomato property or data centers\nIssues without clearly identified security impact, such as clickjacking on a static website, missing security headers, or descriptive error messages\n\nThank you for helping keep Zomato safe for the community!\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":"2017-06-28T04:29:02.787Z"},{"id":3555732,"new_policy":"We take security seriously at Zomato, and we’re committed to protecting our community. If you are a security researcher or expert, and believe you’ve identified security-related issues with Zomato’s website or apps, we would appreciate you disclosing it to us responsibly. \n\nOur team is committed to addressing all security issues in a responsible and timely manner, and we ask the security community to give us the opportunity to do so before disclosing them publicly. Please submit a detailed description of the issue to us, along with the steps to reproduce it. We trust the security community to make every effort to protect our users’ data and privacy. \n\n# Disclosure Policy\n* Let us know as soon as possible upon discovery of a potential security issue, and we'll make every effort to quickly resolve the issue.\n* Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party.\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 explicit permission of the account holder.\n\n#Scope\nThe scope of issues is limited to technical vulnerabilities in the Zomato website or mobile apps. Please do not attempt to compromise the safety or privacy of our users (so please use test accounts), or the availability of Zomato through DoS attacks or spam. We also request you not to use vulnerability testing tools that generate a significant volume of traffic. \n\n# Bounty Program\nWe do not currently have a monetary bug bounty programme, but any report that results in a change will at minimum receive Hall of Fame recognition. We would also be more than happy to provide a certificate of acknowledgement. \n\n# Non-qualifying vulnerabilities\nAlthough we review every reported issue on a case-by-case basis, some of them may not qualify depending on their impact. Here are some common low-risk issues that typically do not qualify:\nAttacks requiring physical access to a user's device\nForms missing CSRF tokens (we require evidence of actual CSRF vulnerability)\nLogin/logout CSRF\nPassword and account recovery policies, such as reset link expiration or password complexity\nInvalid or missing SPF (Sender Policy Framework) records\nContent spoofing / text injection\nUsername enumeration and other similar enumeration reports\nSelf-XSS without a vector for a third party attack.\nIssues related to software or protocols not under Zomato's control\nReports of spam\nBypass of URL malware detection\nVulnerabilities only affecting users of outdated or unpatched browsers and platforms\nAny physical attempts against Zomato property or data centers\nIssues without clearly identified security impact, such as clickjacking on a static website, missing security headers, or descriptive error messages\n\nThank you for helping keep Zomato safe for the community!\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":"2017-06-15T04:47:40.757Z"},{"id":3555731,"new_policy":"We take security seriously at Zomato, and we’re committed to protecting our community. If you are a security researcher or expert and believe you’ve identified security-related issues with Zomato’s website or apps, we would appreciate you disclosing it to us responsibly. \n\nOur team is committed to addressing all security issues in a responsible and timely manner, and we ask the security community to give us the opportunity to do so before disclosing them publicly. Please submit a detailed description of the issue to us, along with the steps to reproduce it. We trust the security community to make every effort to protect our users’ data and privacy. \n\n# Disclosure Policy\n* Let us know as soon as possible upon discovery of a potential security issue, and we'll make every effort to quickly resolve the issue.\n* Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party.\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\n#Scope\nThe scope of issues is limited to technical vulnerabilities in the Zomato website or mobile apps. Please do not attempt to compromise the safety or privacy of our users (so please use test accounts), or the availability of Zomato through DoS attacks or spam. We also request you not to use vulnerability testing tools that generate a significant volume of traffic. \n\n# Bounty Program\nWe do not currently have a monetary bug bounty program, but any report that results in a change will at minimum receive Hall of Fame recognition. We would also be more than happy to provide a certificate of acknowledgment. \n\n# Non-qualifying vulnerabilities\nAlthough we review every reported issue on a case-by-case basis, some of them may not qualify depending on their impact. Here are some common low-risk issues that typically do not qualify:\nAttacks requiring physical access to a user's device\nForms missing CSRF tokens (we require evidence of actual CSRF vulnerability)\nLogin/logout CSRF\nPassword and account recovery policies, such as reset link expiration or password complexity\nInvalid or missing SPF (Sender Policy Framework) records\nContent spoofing / text injection\nUsername enumeration and other similar enumeration reports\nSelf-XSS without a vector for a third party attack.\nIssues related to software or protocols not under Zomato's control\nReports of spam\nBypass of URL malware detection\nVulnerabilities only affecting users of outdated or unpatched browsers and platforms\nAny physical attempts against Zomato property or data centers\nIssues without clearly identified security impact, such as clickjacking on a static website, missing security headers, or descriptive error messages\n\nThank you for helping keep Zomato safe for the community!\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":"2017-06-15T04:47:25.905Z"},{"id":2223861,"new_policy":"We take security seriously at Zomato, and we’re committed to protecting our community. If you are a security researcher or expert, and believe you’ve identified security-related issues with Zomato’s website or apps, we would appreciate you disclosing it to us responsibly. \n\nOur team is committed to addressing all security issues in a responsible and timely manner, and we ask the security community to give us the opportunity to do so before disclosing them publicly. Please submit a detailed description of the issue to us, along with the steps to reproduce it. We trust the security community to make every effort to protect our users’ data and privacy. \n\n# Disclosure Policy\n* Let us know as soon as possible upon discovery of a potential security issue, and we'll make every effort to quickly resolve the issue.\n* Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party.\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 explicit permission of the account holder.\n\n#Scope\nThe scope of issues is limited to technical vulnerabilities in the Zomato website or mobile apps. Please do not attempt to compromise the safety or privacy of our users (so please use test accounts), or the availability of Zomato through DoS attacks or spam. We also request you not to use vulnerability testing tools that generate a significant volume of traffic. \n\n# Bounty Program\nWe do not currently have a monetary bug bounty programme, but any report that results in a change will at minimum receive Hall of Fame recognition. We would also be more than happy to provide a certificate of acknowledgement. \n\n# Non-qualifying vulnerabilities\nAlthough we review every reported issue on a case-by-case basis, some of them may not qualify depending on their impact. Here are some common low-risk issues that typically do not qualify:\nAttacks requiring physical access to a user's device\nForms missing CSRF tokens (we require evidence of actual CSRF vulnerability)\nLogin/logout CSRF\nPassword and account recovery policies, such as reset link expiration or password complexity\nInvalid or missing SPF (Sender Policy Framework) records\nContent spoofing / text injection\nIssues related to software or protocols not under Zomato's control\nReports of spam\nBypass of URL malware detection\nVulnerabilities only affecting users of outdated or unpatched browsers and platforms\nAny physical attempts against Zomato property or data centers\nIssues without clearly identified security impact, such as clickjacking on a static website, missing security headers, or descriptive error messages\n\nThank you for helping keep Zomato safe for the community!\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":"2016-02-04T11:58:25.691Z"}]