Bountytalk - Forums Advertising & Bounty Hub
Other Bounties => Bug bounty programs => Topic started by: Angelina on June 14, 2023, 07:06:35 pm
-
submit bug report: https://www.flickr.com/
Welcome to Flickr's BugBounty Program! We look forward to seeing your reports and working with you to improve our product. Please reach out with any questions, and feel free to share a link to your photostream on reports if you're a user of the product. Thanks!
Response Targets
Flickr will make a best effort to meet the following response targets for hackers participating in our program:
Time to first response (from report submit) - 3 business days
Time to triage (from report submit) - 3 business days
Time to bounty (from triage) - 14 business days
We’ll try to keep you informed about our progress throughout the process.
Disclosure Policy
Follow HackerOne's disclosure guidelines.
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 explicit permission of the account holder.
Please only submit bugs that show a clear exploit, not a theoretical vector
Rewards
Please see the structured bounty table above and report criteria below. Our bounty table provides general guidelines, and all final decisions are at the discretion of Flickr.
Report Criteria
Failure to meet these criteria will most likely result in an Informative or NA report:
Must include steps to reproduce the vulnerability
Must include a working Proof of Concept
NO: "Leaked keys"
YES: PoC showing how the leaked keys are used to gain access, etc.
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:
HTML listed at https://www.flickr.com/html.gne is legitimate usage in text inputs. Clickable links are legitimate usage. Any HTML that’s not outlined at that URL however is fair game.
Vulnerabilities that only work on our unsupported browser versions: Chrome, Firefox, Safari, and Edge that are older than the last 2 versions, or any other browser not already listed.
Clickjacking on pages with no sensitive actions.
Unauthenticated/logout/login CSRF.
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.
Missing best practices in SSL/TLS configuration.
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
Self XSS
Spam
Vulnerabilities due to user generated content that don't result in access to private data or account takeover (i.e. Links in comments redirecting to a malicious site are out of scope)
We're not concerned with keeping our coupon codes secret, please use any you brute-force to buy a subscription :)
Reports of exposed hostnames or IPs without any actual exploit
Anything related to abuse reporting on our platform. Any Flickr accounts that interfere or submit erroneous abuse reports may be subject to deletion.
AWS resources that are not shown to be owned by Flickr
Any issue that results in users being logged out of Flickr, without exposing any PII or allowing for account takeover
Any issue related to circumventing free account restrictions (i.e. 1000 photo limit)
Anything related to SPF or email configuration
End-user Flickr API keys leaked on non-Flickr owned GitHub repos, search results, etc...
Anything related to the sending or receiving of emails, with the exception of email content (i.e. Email header bugs are out of scope)
Safe Harbor
Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you. If legal action is initiated by a third party against you in connection with activities conducted under this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.
Thank you for helping keep Flickr and our users safe!