Honest Web Bug Bounty Program

Honest

Rp0 ~ Rp7.500.000Total reward

Description

PT Honest Financial Technologies

We believe everyone deserves access to fair financial products. At Honest, we build financial products that people love. We create products that are fair, easy to understand and improve our customers’ lives. We strive to be:
Honest - We build fair and transparent financial products.
Humble - We treat everyone with respect and own our mistakes.
Hardworking - We add value every day and serve our customers 24/7.

Target info

Vulnerability Disclosure Policy

Honest takes the security of its systems and applications seriously. To ensure that our
systems are secure and free from vulnerabilities, we have established a private bug
bounty program through RedStorm.io.
This program is designed to encourage security researchers to identify and report
vulnerabilities in our systems and applications. By doing so, we can quickly address any
security issues that may arise and improve the overall security posture of our
organization.
As a security researcher, if you want to participate in our private bug bounty program,
you are required to register and report through RedStorm.io. This platform provides a
secure and efficient way to submit reports and receive rewards for valid vulnerabilities.
We believe that this program is an essential part of our security strategy, and we are
committed to providing a safe and secure environment for our customers and
employees. We encourage security researchers to participate in our program and help
us identify and remediate security vulnerabilities.
Thank you for your interest in our private bug bounty program, and we look forward to
working with you to improve the security of our systems and applications.

Response Targets

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

First Response: 1 business day
Time to Triage: 4 business days
Time to Bounty: 10 business days

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

Disclosure Policy

Please do not discuss this program or any vulnerabilities (even resolved ones)
outside of the program without express consent from the organization.

Program Rules

  • Please provide detailed reports with reproducible steps. If the report is not detailed
    enough to reproduce the issue, the issue will not be eligible for a reward.
  • Submit one vulnerability per-report, unless you need to chain vulnerabilities to
    provide impact.
  • When duplicates occur, we only award the first report that was received (provided
    that it can be fully reproduced).
  • Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.
    Social engineering (e.g. phishing, vishing, smishing) is prohibited.
  • Make a good faith effort to avoid privacy violations, destruction of data, and
    interruption or degradation of our service. Only interact with accounts you own or
    with the explicit permission of the account holder.

Quality Reports

By submitting reports to the program, you can notify programs of vulnerabilities. While
not all great vulnerability reports look the same, many share common features:

  • Detailed descriptions of your discovery with clear, concise, reproducible steps or a
    working proof-of-concept (POC). If you do not explain the vulnerability in detail,
    there may be significant delays in the process, which is undesirable for everyone.
  • Screenshots and/or videos can sometimes assist security teams in reproducing
    your issue. Most teams prefer written reproduction steps, but screenshots and
    videos can be used to augment your report and make it easier for security teams to
    quickly understand the issue you‘re reporting.
  • The impact of the vulnerability; if this bug were exploited, what could happen?
    Security teams need to file bugs internally and get resources to fix these issues.
    Describing why the issue is important can assist in quickly understanding the impact
    of the issue and help prioritize response and remediation.

It’s best to be comprehensive, yet concise so that our security team need to have all the
details required to verify and validate your report. We recommend you provide enough
information to:

  • Outline the bug.
  • Reproduce the bug.
  • Assess the coverage the bug applies to.
  • Provide additional related logs or information.

Reward Eligibility and Amount

We are happy to thank everyone who submits valid reports which help us improve the
security of Honest however only those that meet the following eligibility requirements
may receive a monetary reward:

  • You must be the first reporter of a vulnerability.
  • The vulnerability must be a qualifying vulnerability (see below).
  • The report must contain the following elements:
    • Clear textual description of the vulnerability, how it can be exploited, the security
      impact it has on the application, its users, and remediation advice on fixing the
      vulnerability.
    • Proof of exploitation: screenshots and/or videos demonstrating how the exploit
      was performed, and showing the final impact.
    • Provide complete steps with the necessary information to reproduce the exploit,
      including (if necessary) code snippets, payloads, commands etc.
  • You must not break any of the testing policy rules listed above
  • You must not be a former or current employee of Honest or one of its contractors.
  • Reward amounts are based on:
    • Reward grid of the report‘s scope
    • CVSS scoring and actual business impact of the vulnerability upon performing risk
      analysis

P1 - CVSS Rating=9.0 - 10.0 : Rp7.500.000
P2 - CVSS Rating=7.0 - 8.9 : Rp5.000.000
P3 - CVSS Rating=4.0 - 6.9 : Rp2.000.000
P4 - CVSS Rating=0.1 - 3.9 : Rp500.000
P5 - CVSS Rating=0.0 : Rp0

Third-Party Services

If you believe an issue with one of our third-party service providers:

  1. Any reports regarding third-party services resulting from Honest‘s misconfiguration
    or insecure usage of those services will be considered in scope.
  2. Any reports regarding third-party services resulting from vulnerabilities of third
    parties that affect all their users and can realistically be mitigated by Honest will be
    considered in scope.
  3. Any reports regarding third-party services resulting from vulnerabilities of third
    parties that affect all their users and cannot realistically be mitigated by Honest will
    be considered out of scope.

Out of scope vulnerabilities

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

  • Highly speculative report with no real proof
  • API keys intended for use by clients e.g Google Maps API Key
  • Clickjacking on pages with no sensitive actions
  • Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions or minimal impact
  • Attacks requiring MITM or physical access to a user‘s device.
  • Previously known vulnerable libraries without a working Proof of Concept.
  • Comma Separated Values (CSV) injection without demonstrating a vulnerability.
  • Any activity that could lead to the disruption of our service (DoS).
  • Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
  • Rate limiting or brute-force issues on authenticated and non-authenticated endpoints
  • Tabnabbing
  • Open redirect - unless an additional security impact can be demonstrated
  • Issues that require unlikely user interaction
  • Microsites with little to no user data outside of listed scope.
  • Sending a spam email to a user directly without going through our system
  • Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)
  • Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors).
  • Disclosure of information that does not present a significant risk e.g. outdated info, personal task list with no sensitive data.
  • Any issues related to web browsers, such as:
    • Issues that do not affect the latest version of modern browsers
    • Issues related to web browser add-ons
  • Missing HTTP security headers but not limited to:
    • Strict-Transport-Security
    • HttpOnly
    • X-Frame-Options
    • X-XSS-Protection
    • X-Content-Type-Options
    • Content-Security-Policy
    • X-Content-Security-Policy
    • X-WebKit-CSP
    • Content-Security-Policy-Report-Only*
  • Any infrastructure vulnerabilities that are related to the following, that do not have high impact and severity on the infrastructure:
    • Missing best practices in SSL/TLS configuration or any Certificates/TLS/SSL related issues
    • DNS issues (i.e. MX records, SPF records, etc.)
    • Server configuration issues (i.e., open ports, TLS, etc.)
  • Most vulnerabilities within our sandbox, UAT, or staging environments.
  • Subdomain takeover without any real impact.

Recently disclosed 0-day vulnerabilities
For any 0-days vulnerabilities, we really love the excitement, however please do understand that we need time to patch and it will take at minimum of 2 months. During the period of time any new CVEs won’t be qualified for a reward. However, in certain exceptional cases, if we decide to reward, the decision will be at our discretion.

Safe Harbour

Any activities in relation to your participation in this program conducted in a manner with
full submission and compliance with this Policy Page will be considered authorized
conduct and we will not initiate or suggest legal action against you. If legal action is
initiated by a third party against you in connection with your participation in this
program, provided that you have fully submitted and complied with this program’s Policy
Page, we will make it known that your actions were conducted pursuant to this program
and have complied with the Policy Page.

In Scope

Web Application: honest.co.id

Reward

This program adheres to the RedStorm Vulnerability Rating Taxonomy for the prioritization/rating of findings. if relevant, the deviations from the VRT shoul be listed here in a markdown table:

P1 POINT REWARD 100 Rp7.500.000
P2 POINT REWARD 50 Rp5.000.000
P3 POINT REWARD 20 Rp2.000.000
P4 POINT REWARD 10 Rp500.000
P5 POINT REWARD 5 Rp0

Targets

In Scope
honest.co.id
Website
Out of scope
Other
Other

1

Vulnerabilities rewarded
Latest hall of fame
Richa Behl
Copyright © 2018 - RedStorm. All rights reserved.TermsPrivacyContact