Description

Torfs - the well-known shoe retailer in Belgium - is still a 100% family business today. This family character guarantees a number of important values within the company where employees are central. A head office in Sint-Niklaas and a spectacular distribution center in Temse offer support to the points of sale and customers of the E-Commerce website. With more than 80 stores in Flanders, 2 shops in the French part of Belgium and a growing online shop in Belgium, The Netherlands and several marketplaces, Torfs wants to be and remain the most customer-friendly optichannel shoe store chain.

Bounties
Low
Medium
High
Critical
Exceptional
Tier 2
€ 0
€ 250
€ 750
€ 2,500
€ 5,000
Up to € 5,000
Tier 3
€ 0
€ 100
€ 250
€ 500
€ 1,000
Up to € 1,000
Domains

winkels.torfs.be

Tier 2
URL

🇫🇷🇳🇱

www.schoenentorfs.be

Tier 2
URL

🇫🇷🇳🇱

www.schoenentorfs.nl

Tier 2
URL

🇳🇱

www.torfs.be

Tier 2
URL

🇫🇷🇳🇱

www.torfs.nl

Tier 2
URL

🇳🇱

www.samenfittorfs.be

Tier 3
URL

🇳🇱 - NEW domain!

www.sterkinjeschoenen.be

Tier 3
URL

🇫🇷🇳🇱 - NEW domain!

www.torfssuppliers.be

Tier 3
URL

🇬🇧 - NEW domain!

Any related Torfs domain

No Bounty
Other
In scope

The use of an intigriti.me address is mandatory at all times! (Not respecting these rules means you will not be eligible for a bounty)

All the websites have an open registration.

Please do not use the following methods:

  • Bruteforce -> Password / Username bruteforce
  • Directory / file enumeration: see rate limit guidelines
  • Directory / file / content enumeration: see rate limit guidelines
  • Rate limit (maximum amount of requests per second) used in automation: 1 requests per second

BACKGROUND INFO

winkels.torfs.be is a website exhibited in the Torfs stores. They allow customers to consult the online store via kiosk touch-screens. This website is customized to give a better user experience via touch screens.

IMPORTANT

All the websites share the same codebase. They can contain common issues. If a specific issue has already been found in another one of these websites it will be treated as a duplicate for this one.

Out of scope

Subdomain takeover is out of scope!

Application

  • Self-XSS that cannot be used to exploit other users
  • Verbose messages/files/directory listings without disclosing any sensitive information
  • CORS misconfiguration on non-sensitive endpoints
  • Missing cookie flags
  • Missing security headers
  • Cross-site Request Forgery with no or low impact
  • Presence of autocomplete attribute on web forms
  • Reverse tabnabbing
  • Bypassing rate-limits or the non-existence of rate-limits.
  • Best practices violations (password complexity, expiration, re-use, etc.)
  • Clickjacking on pages with no sensitive actions
  • CSV Injection
  • Host Header Injection
  • Sessions not being invalidated (logout, enabling 2FA, ..)
  • Hyperlink injection/takeovers
  • Mixed content type issues
  • Cross-domain referer leakage
  • Content injection
  • Username / email enumeration
  • E-mail bombing
  • HTTP Request smuggling without any proven impact
  • Homograph attacks
  • XMLRPC enabled
  • Banner grabbing / Version disclosure
  • Open ports without an accompanying proof-of-concept demonstrating vulnerability
  • Weak SSL configurations and SSL/TLS scan reports
  • Not stripping metadata of images
  • Disclosing credentials without proven impact
  • Disclosing API keys without proven impact
  • Same-site scripting
  • Arbitrary file upload without proof of the existence of the uploaded file

General

  • In case that a reported vulnerability was already known to the company from their own tests, it will be flagged as a duplicate.
  • Theoretical security issues with no realistic exploit scenario(s) or attack surfaces, or issues that would require complex end user interactions to be exploited, may be excluded or be lowered in severity
  • Spam, social engineering and physical intrusion
  • DoS/DDoS attacks or brute force attacks.
  • Vulnerabilities that are limited to non-current browsers (older than 3 versions) will not be accepted
  • Attacks requiring physical access to a victim’s computer/device, man in the middle or compromised user accounts
  • Recently disclosed zero-day vulnerabilities in commercial products where no patch or a recent patch (< 2 weeks) is available. We need time to patch our systems just like everyone else - please give us 2 weeks before reporting these types of issues.
  • Reports that state that software is out of date/vulnerable without a proof-of-concept
Rules of engagement

Guidelines

  • Remember: quality over quantity!
  • Provide detailed but to-the point reproduction steps
  • Include a clear attack scenario, a step by step guide in the PoC is highly appreciated
  • Please do NOT discuss bugs before they are fixed

Safe harbour for researchers

Torfs considers ethical hacking activities conducted consistent with the Researcher Guidelines, the Program description and restrictions (the Terms) to constitute “authorized” conduct under criminal law. Torfs will not pursue civil action or initiate a complaint for accidental, good faith violations, nor will they file a complaint for circumventing technological measures used by us to protect the scope as part of your ethical hacking activities.

If legal action is initiated by a third party against you and you have complied with the Terms, Torfs will take steps to make it known that your actions were conducted in compliance and with our approval.

Severity assessment

All our rewards are impact based, therefore we kindly ask you to carefully evaluate a vulnerability's impact when picking a severity rating. To give you an idea of what kind of bugs belong in a certain severity rating we've put some examples below. Note that depending on the impact a bug can sometimes be given a higher/lower severity rating.

Exceptional

  • Remote Code Execution
  • SQLi

Critical

  • Read only access to all PII sensitive date (personal details,…)

High

  • Stored XSS without user interaction
  • Authentication bypass on critical infrastructure
  • Order free shoes, sidenote: Torfs will only accept payment bypasses if Torfs received the payment notification as well from their third party.

Medium

  • XSS that requires user interaction
  • Misuse of vouchers

Low

  • CSRF
  • Open redirect
FAQ

Can I create a test account?

Yes and you are encouraged to do so! Please use your @intigriti.me email address for the account creation. More info can be found here: https://kb.intigriti.com/product-features/intigritime

Are there specific rules to follow for test accounts creation?

Yes. Only use your @intigriti.me email address for the account creation.

All aboard!
Please log in or sign up on the platform

For obvious reasons we can only allow submissions or applications for our program with a valid intigriti account.

It will only take 2 minutes to create a new one or even less to log in with an existing account, so don't hesitate and let's get started. We would be thrilled to have you as part of our community.

Program specifics
ID check required
Reputation points
Triage
Last 90 day response times
avg. time first response
< 24 hours
avg. time to decide
< 4 days
avg. time to triage
< 2 days
Activity
1/22
logo
g30rgyth3d4rk
created a submission
1/21
Torfs
closed a submission
1/20
logo
jackspa22ow
created a submission
1/20
Torfs
unsuspended the program
1/20
Torfs
closed a submission
1/20
Torfs
closed a submission
1/20
Torfs
closed a submission
1/20
Torfs
closed a submission
1/19
Torfs
suspended the program
1/19
logo
pratik23
created a submission