Infosec Institute

Open Bug Bounty mentioned in the
Top 6 Bug Bounty programs of
2022 by the InfoSec Institute

The Hacker News

Open Bug Bounty named among the
Top 5 Bug Bounty programs of 2021
by The Hacker News

For security researchers
Report a Vulnerability
Submit, help fixing, get kudos.
For website owners
Start a Bug Bounty
Run your bounty program for free.
1,775,119 coordinated disclosures
1,467,787 fixed vulnerabilities
2,089 bug bounty programs, 4,024 websites
56,752 researchers, 1,734 honor badges

3 Foot Tall Bug Bounty Program

3 Foot Tall runs a bug bounty program to ensure the highest security and privacy of its websites. Everyone is eligible to participate in the program subject to the below-mentioned conditions and requirements of 3 Foot Tall

Open Bug Bounty performs triage and verification of the submissions. However, we never intervene to the further process of vulnerability remediation and disclosure between 3 Foot Tall and researchers.

Bug bounty program allow private and public submissions.

Bug Bounty Scope

The following websites are within the scope of the program:

*.3foottall.co.uk
*.3foottall.com

Non-Intrusive Submissions Handling

The following section encompasses submission of the vulnerabilities that do not require intrusive testing as per Open Bug Bounty rules:

- Cross Site Scripting (XSS)
- Open Redirect

- Cross Site Request Forgery (CSRF)
- Improper Access Control

General Requirements:

Please provide a brief summary of the issue, including any URIs or other identifiers as necessary.
For complex issues, a workflow may be required to verify the issue.
A PoC or screenshots are appreciated to diagnose/confirm issues and fixes.
Please do not submit multiple reports for different subdomains if the page is clearly the same.

Testing Requirements:

No social engineering contacts please.
No destructive or damaging test, any deliberate disruption caused to normal operations will forfeit any possibly award and will be reported.
No excessive or repeated scanning.
Please note that excessive scanning or repeated attempts may get auto-blocked and reported as malicious by automated monitoring.
Please be aware that invalid or unauthorised subdomains are resolved to the main website.

Possible Awards:

We will always add a recommendation in the researchers’ profile for all valid reports.
Valid reports may be listed on acknowledgements page, if deemed appropriate,
Financial or gift awards may be awarded where they are seen appropriate for the issue identified. Not all vulnerabilities are eligible for an award, duplicate reports are also ineligible.

Special Notes:

No disclosure of issues identified before a resolution can be implemented.
Issues in third-party libraries or code where no official fix is available are excluded - please report those vulnerabilities to the responsible person for those codebases.
For submissions not appropriate on Open Bug Bounty, please contact us on directly through the contact form on our website.

Other Submissions Handling

Website owner want to receive information about other vulnerabilities

Notifications:

[email protected]

General Requirements:

Please provide a brief summary of the issue, including any URIs or other identifiers as necessary.
For complex issues, a workflow may be required to verify the issue.
A PoC or screenshots are appreciated to diagnose/confirm issues and fixes.
Please do not submit multiple reports for different subdomains if the page is clearly the same.

Testing Requirements:

No social engineering contacts please.
No destructive or damaging test, any deliberate disruption caused to normal operations will forfeit any possibly award and will be reported.
No excessive or repeated scanning.
Please note that excessive scanning or repeated attempts may get auto-blocked and reported as malicious by automated monitoring.
Please be aware that invalid or unauthorised subdomains are resolved to the main website.

Possible Awards:

Valid reports may be listed on acknowledgements page, if deemed appropriate,
Financial or gift awards may be awarded where they are seen appropriate for the issue identified. Not all vulnerabilities are eligible for an award, duplicate reports are also ineligible.

Special Notes:

No disclosure of issues identified before a resolution can be implemented.
Issues in third-party libraries or code where no official fix is available are excluded - please report those vulnerabilities to the responsible person for those codebases.
For submissions not appropriate on Open Bug Bounty, please contact us on directly through the contact form on our website.

Community Rating

Provided by security researchers who reported security vulnerabilities via this bug bounty program:

 
Response Time  Information How quickly researchers get responses to their submissions.
Remediation Time  Information How quickly reported submissions are fixed.
Cooperation and Respect  Information How fairly and respectfully researchers are being treated.

Researcher's comments

No comments so far.

  Latest Patched

 22.01.2025 mylegacy.life.gov.sg
 22.01.2025 fics.nust.edu.pk
 21.01.2025 officemarket.am
 20.01.2025 public.tameside.gov.uk
 20.01.2025 hp.com
 20.01.2025 ted.europa.eu
 19.01.2025 serraria.pb.gov.br
 17.01.2025 cmpentecoste.ce.gov.br

  Latest Blog Posts

04.12.2023 by BAx99x
Unmasking the Power of Cross-Site Scripting (XSS): Types, Exploitation, Detection, and Tools
04.12.2023 by a13h1_
$1120: ATO Bug in Twitter’s
04.12.2023 by ClumsyLulz
How I found a Zero Day in W3 Schools
04.12.2023 by 24bkdoor
Hack the Web like a Pirate: Identifying Vulnerabilities with Style
04.12.2023 by 24bkdoor
Navigating the Bounty Seas with Open Bug Bounty

  Recent Recommendations

    13 January, 2025
    nzpdev:
Andrea discovered an XSS vulnerability on one of our pages. We promptly patched that thanks to her report. We give top marks for spotting our mistake. Thank you again
    20 December, 2024
    CygnusEd:
Thank you very much for your reporting a XSS vulnerability on my site.
Thanks also for the friendly communication!
Great job!
    10 December, 2024
    Sim:
Thank you for identifying an old development project. Information provided was clear allowing a swift removal of the offending code.
    10 December, 2024
    privacysafe:
Andrea is very professional and reported an issue responsibly and in a timely manner, with great communication about the scope and potential impact. Though it was a low-severity issue, this was nevertheless something in need of patching and we're always grateful at PrivacySafe to security researchers, especially hardworking volunteers like Andrea.
    9 December, 2024
    Spinner:
Reported an XSS vulnerability on our website, and provided enough details for us to fix it quickly. So helpful!!