Description

HLN.be is the number one news site in Flanders. 24/7 news with a focus on current events, sports and entertainment. The editors know how to keep their finger on the pulse at all times: on average every 4 minutes a new article appears on the news site. Readers consume their news more and more fragmented through their social media, so it is important for HLN to stay top of mind with its own app.

Bounties
Low
Medium
High
Critical
Exceptional
Tier 2
€ 0
€ 250
€ 700
€ 1,100
€ 2,000
Up to € 2,000
Tier 3
€ 0
€ 50
€ 50
€ 50
€ 50
Up to € 50
Rules of engagement
Required
Not applicable
max. 5 requests/sec
Not applicable

Our promise to you

  • We will respond to report in ultimately two weeks, probably faster!
  • We are happy to respond to any questions, please use the button in the right top corner for this.
  • We respect the safe harbour clause that you can find below

Your promise to us

  • ONLY USE YOUR INTIGRITI.ME ADDRESS (in case of violation, no bounty can be awarded)
  • Provide detailed but to-the point reproduction steps
  • Include a clear attack scenario. How will this affect us exactly?
  • Remember: quality over quantity!
  • Please do not discuss or post vulnerabilities without our consent (including PoC's on YouTube and Vimeo)
  • Please do not use automatic scanners - be creative and do it yourself! We cannot accept any submissions found by using automatic scanners. Scanners also won't improve your skills, and can cause a high server load (we'd like to put our time in thanking researchers rather than blocking their IP's 😉)
Domains

hln.be

Tier 2
URL

login2.hln.be

Tier 2
URL

myaccount.hln.be

Tier 2
URL

www.hln.be

Tier 2
URL

*.hln.be

Tier 3
URL
In scope

IMPORTANT:
The websites partially share the same codebase with other DPG products (included, but not limited to, Algemeen Dagblad, De Morgen, De Volkskrant, Het Parool, Humo, Trouw). They can contain common issues. If a specific issue has already been found in another DPG website it will be treated as a duplicate.

We're interested to hear about any issue that potentially compromises our company or its user's security. Before submitting a vulnerability make sure to check that it's not listed in our out of scope policy (which you can find below). If you have additional questions about our program feel free to contact us through Intigriti's support.

Out of scope

Known Issues

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
  • Anything related to email spoofing, SPF, DMARC or DKIM
  • 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 API keys without proven impact
  • Same-site scripting
  • Subdomain takeover without taken over the subdomain
  • 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

Mobile

  • Shared links leaked through the system clipboard
  • Any URIs leaked because a malicious app has permission to view URIs opened
  • The absence of certificate pinning
  • Sensitive data in URLs/request bodies when protected by TLS
  • Lack of obfuscation
  • Path disclosure in the binary
  • Lack of jailbreak & root detection
  • Crashes due to malformed URL Schemes
  • Lack of binary protection (anti-debugging) controls, mobile SSL pinning
  • Snapshot/Pasteboard leakage
  • Runtime hacking exploits (exploits only possible in a jailbroken environment)
  • API key leakage used for insensitive activities/actions
  • Attacks requiring physical access to the victim's device
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

  • A remote code execution vulnerability on the production server
  • Full database access (incl. update/delete)

Critical

  • A SQL injection vulnerability
  • Access to all customer personal data or access to a targeted user
  • A numeric IDOR that allows mass write/read actions on critical features
  • Path traversal leading to the disclosure of local files

High

  • Access to random users' data (sensitive PII)
  • A stored XSS vulnerability (excluding unexploitable self-XSS)
  • Vertical authentication bypass

Medium

  • A DOM XSS vulnerability
  • Reflected XSS
  • An IDOR leading to the disclosure of non-critical data
  • A CSRF with a significant impact
  • Lateral authentication bypass

Low

  • A reflected XSS vulnerability that requires significant user interaction
  • A CSRF vulnerability in a non-critical feature
  • Open redirect
FAQ

Where can we get credentials for the app?

You can self-register on the application but please don’t forget to use your @intigriti.me address.

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.

Researchers
last contributors
logo
logo
logo
logo
logo
logo
leaderboard
logo
logo
logo
logo
logo
logo
Overall stats
submissions received
177
average payout
€116
accepted submissions
31
total payouts
€2,250
Last 90 day response times
avg. time first response
< 24 hours
avg. time to decide
< 2 weeks
avg. time to triage
< 6 days
Activity
10/22
logo
created a submission
10/20
logo
created a submission
10/19
DPG Media
closed a submission
10/19
DPG Media
closed a submission
10/19
DPG Media
accepted a submission
10/17
logo
created a submission
10/15
logo
created a submission
10/13
logo
created a submission
10/5
DPG Media
changed the rules of engagement
10/1
DPG Media
closed a submission