Skip to content
bugbounty.fyi
Get paid to secure open source 475 paid open-source programs on Sorona, up to $1M Perk Low bugs: $100 or 1 mo Claude Max

Also on Patchstack. All 476 paid open-source programs

Try

Highest paying Newly launched Paid without KYC Full safe harbor
All results

About this site

Posten Bring Responsible Disclosure

By Posten Bring AS Vulnerability disclosure program on Intigriti posten.no

Accepting reports Full safe harbor
Go to program
Top reward
No cash rewards
Top severity paid
Not published
Assets in scope
8
Public CVEs
0
Last change

At a glance

What to know before you start testing.

No cash rewards
A disclosure program: you report for credit, not money.
Report on Intigriti
Submit through the program page.
Full safe harbor
Good-faith research is authorised; no legal action.
No public write-ups
Keep findings private.

Rewards

What Intigriti lists as the payout for each severity.

This program does not pay cash rewards.

Pays cash
No While we do not offer bounties for reported vulnerabilities, we deeply appreciate your contribution to securing our systems.

Summarised with AI from the program policy on Intigriti, read 12 Nov 2026, and checked word for word against it. Read the original

Scope

8 assets you may test.

Wildcard domains 5

  • *.bring.com No bounty
  • *.digipostdata.no No bounty
  • *.digipost.no No bounty
  • *.mybring.com No bounty
  • *.posten.no No bounty

Android apps 1

  • Digipost Android app

iOS apps 1

  • Digipost iOS app

Products and areas 1

  • https://github.com/digipost

Rules

What the policy asks of you, and the bug types it won't reward, quoted from Posten Bring Responsible Disclosure (via Intigriti)'s policy.

While testing

  • Only use publicly available test environments for testing (see below) to avoid impacting production
  • Respect the scope of the program
  • Not discuss or disclose vulnerability information without prior written consent (including PoC's on YouTube and Vimeo)

Not accepted

  • Theoretical security issues with no realistic exploit scenario(s) or attack surfaces, or issues that would require complex end user interactions to be exploited
  • Spam, social engineering and physical intrusion
  • DoS/DDoS attacks or brute force attacks
  • Vulnerabilities that only work on software that no longer receive security updates
  • Attacks requiring physical access to a victim's computer/device, man in the middle or compromised user accounts
  • Reports that state that software is out of date/vulnerable without a proof-of-concept
  • Pre-Auth Account takeover/OAuth squatting
  • Self-XSS that can't 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 without proven impact/unrealistic user interaction
  • CSV Injection
  • Sessions not being invalidated (logout, enabling 2FA, etc.)
  • Content injection without being able to modify the HTML
  • Email bombing
  • HTTP Request smuggling without any proven impact
  • Homograph attacks
  • Banner grabbing/Version disclosure

Summarised with AI from the program policy on Intigriti, read 12 Nov 2026, and checked word for word against it. Read the original

Changes

Tracked since 11 Nov 2026. Last checked 18 minutes ago.

No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.

Before we tracked it

Scope and reward changes recorded before this page started tracking it.

  1. Scope added

    Digipost iOS app

  2. Scope added

    Digipost Android app

  3. Scope added

    https://github.com/digipost

  4. Scope added

    https://*.digipost.no

  5. Scope added

    https://*.digipostdata.no

  6. Scope added

    https://*.posten.no

  7. Scope added

    https://*.bring.com

  8. Scope added

    https://*.mybring.com

  9. Scope removed

    www.showpad.com

Public CVEs

Published vulnerabilities in this vendor's products, from the NVD.

Search NVD

No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.

Original policy

Copied from www.intigriti.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.

Description

Posten Bring AS is a Nordic postal and logistics group that develops and delivers comprehensive solutions within post and logistics. We have over 12,600 employees, and meet the market with the two brands Posten and Bring.

Rules of engagement

By participating in this program, you agree to:

  • Only use publicly available test environments for testing (see below) to avoid impacting production
  • Respect the Community Code of Conduct
  • Respect the Intigriti Terms and Conditions
  • Respect the scope of the program
  • Not discuss or disclose vulnerability information without prior written consent (including PoC's on YouTube and Vimeo)

Test environments

  • difitest.digipost.no
  • difitest.signering.posten.no

In scope

This Responsible Disclosure Program covers all Posten Bring AS services. Researchers should perform testing against the test environments listed in the Rules of engagement section to avoid impacting production.

Out of scope

Any system not explicitly listed in the in-scope section or third-party services not owned or managed by Posten Bring is out of scope.

General

  • Theoretical security issues with no realistic exploit scenario(s) or attack surfaces, or issues that would require complex end user interactions to be exploited
  • Spam, social engineering and physical intrusion
  • DoS/DDoS attacks or brute force attacks
  • Vulnerabilities that only work on software that no longer receive security updates
  • 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

Application

  • Pre-Auth Account takeover/OAuth squatting
  • Self-XSS that can't 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 without proven impact/unrealistic user interaction
  • CSV Injection
  • Sessions not being invalidated (logout, enabling 2FA, etc.)
  • Content injection without being able to modify the HTML
  • Email bombing
  • HTTP Request smuggling without any proven impact
  • Homograph attacks
  • Banner grabbing/Version disclosure
  • Not stripping metadata of files
  • Arbitrary file upload without proof of the existence of the uploaded file
  • Host header injection without proven business impact

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
  • Snapshot/Pasteboard leakage
  • Runtime hacking exploits (exploits only possible in a jailbroken environment)
  • API key leakage used for insensitive activities/actions

Severity

This program follows Intigriti's triage standards based on the proof of concept.

FAQ

Where can we get credentials for the applications?

The process will vary depending on the application. Some applications allow you to self-register while others use Norwegian ID-solutions or require invitations.

Digipost

Norwegian ID is required in production, but you can self-register in the difitest environment.

Personal account

  1. Go to https://www.difitest.digipost.no/registrering/en/person
  2. Click "Continue"
  3. Choose "TestID"
  4. Click "Find random user" and save the SSN (you need it when logging in again)
  5. Click "Authenticate"
  6. Enter your @intigriti.me email address and any phone number
  7. Click "Create Digipost account"
  8. Skip phone number verification by clicking "Continue without confirming now"
  9. Complete the registration process

To log in next time go to https://www.difitest.digipost.no/innlogging/en, select TestID and enter the SSN.

Rewards

While we do not offer bounties for reported vulnerabilities, we deeply appreciate your contribution to securing our systems. As a token of our gratitude, we offer invites to private bug bounty programs in specific cases, such as high severity vulnerabilities and well written reports.