Description

The Antwerp-Bruges Port Authority has a key role in the port's day-to-day operation. The Port Authority manages and maintains the docks, the bridges, the locks, the quay walls and the land. The personnel is also responsible for safe shipping traffic in the docks, the bridges and locks. In addition, the Port Authority provides tugs and cranes, carries out dredging work and promotes the port at home and abroad.

Bounties
Low
Medium
High
Critical
Exceptional
Tier 2
€0
€20
€50
€100
€150
Up to €150
Rules of engagement
Required
Not applicable
max. 5 requests/sec
Not applicable

Our promise to you

  • 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

  • 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)
Domains

*.c-point.be

Tier 2
URL

api.portofantwerpbruges.com

Tier 2
URL

apps.portofantwerpbruges.com

Tier 2
URL

as2.portofantwerpbruges.com

Tier 2
URL

digitalspecs.portofantwerpbruges.com

Tier 2
URL

login.portofantwerpbruges.com

Tier 2
URL

maximo.portofantwerpbruges.com

Tier 2
URL

my.portofantwerpbruges.com

Tier 2
URL

oprc.portofantwerpbruges.com

Tier 2
URL

register-accpt.portofantwerpbruges.com

Tier 2
URL

servicedesk-accpt.portofantwerpbruges.com

Tier 2
URL

servicedesk.portofantwerp.com

Tier 2
URL

servicedesk.portofantwerpbruges.com

Tier 2
URL

share.portofantwerpbruges.com

Tier 2
URL

webapps.portofantwerpbruges.com

Tier 2
URL

wiki.portofantwerpbruges.com

Tier 2
URL

www.oursustainableport.com

Tier 2
URL

www.portofantwerpbruges.com

Tier 2
URL

188.118.8.0/25

No Bounty
IP Range

94.107.237.192/26

No Bounty
IP Range
In scope

The use of an intigriti.me address is mandatory at all times!

We are happy to announce our first program! We've done our best to clean most of our known issues and now would like to request your help to spot the once we missed! We are specifically looking for

  • CVE-2021- 44228 and all Log4Shell relating issues
  • leaking of personal data
  • horizontal / vertical privilege escalation
  • SQLi
  • ...

IMPORTANT:
Some websites partially share the same codebase and can contain common issues. If a specific issue has already been found in another Port of Antwerp website it will be treated as a duplicate.

Rewards

Port of Antwerp SWAG will be awarded for valid High+ submissions

Out of scope

Out of scope DOMAINS

  • jobs.portofantwerp.com
  • media.portofantwerp.com
  • future.portofantwerp.com
  • register.portofantwerp.com (NOTE: register-accpt.portofantwerp.com and register-test.portofantwerp.com are IN scope!)

Out of scope ACTIONS

Doing registrations on our websites without the use of an intigriti.me address

Application

  • Pre-auth account takeover / oauth squatting
  • 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 without proven business impact
  • Blind SSRF without proven business impact (DNS pingback only is not sufficient)
  • Disclosed and/or misconfigured Google API key (including maps)
  • 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 credentials without proven impact
  • 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 discovered zero-day vulnerabilities found in in-scope assets within 14 days after the public release of a patch or mitigation may be reported, but are usually not eligible for a bounty.
  • 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
  • Self-XSS that cannot be used to exploit other users
  • 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
  • Attacks requiring installing malicious applications onto 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

  • RCE (Remote Code Execution)

Critical

  • SQL injection
  • Authentication bypass on critical infrastructure
  • Privilege escalation

High

  • Access to all customer personal data
  • Stored XSS without user interaction

Medium

  • XSS
  • CSRF with a significant impact

Low

  • XSS that requires lots of user interaction ( > 3 steps)
  • CSRF with a very limited impact

Port of Antwerp is following intigriti's standard view on severity assessment and impact analysis. More information can be found on:
http://kb.intigriti.com/en/articles/3672302-severity-assessment

FAQ

Where can we get credentials for the app?

We currently don’t offer any credentials to test user roles.

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
Last 90 day response times
avg. time first response
< 8 hours
avg. time to decide
< 3 weeks
avg. time to triage
< 2 days
Activity
11/28
Port of Antwerp-Bruges
changed the domains
11/28
Port of Antwerp-Bruges
changed the bounties
11/28
Port of Antwerp-Bruges
changed the domains
11/28
Port of Antwerp-Bruges
changed the bounties
11/28
Port of Antwerp-Bruges
changed the domains
11/28
Port of Antwerp-Bruges
changed the bounties
11/28
Port of Antwerp-Bruges
changed the domains
11/28
Port of Antwerp-Bruges
changed the bounties
11/28
Port of Antwerp-Bruges
changed the domains
11/28
Port of Antwerp-Bruges
changed the bounties