Skip to content

DZ BANK AG

Bug bounty on security.txt dzbank.de

Accepting reports security.txt mentions bounty
Top reward
Not published
Top severity paid
Not published
Assets in scope
21
Public CVEs
0
Last change
No changes yet

At a glance

What to know before you start testing.

Pays cash
Amounts are not published; ask before you invest time.
Report by email
[email protected]
Partial safe harbor
Some legal protection; read the terms.
Publish after a fix
Coordinate the timing with the company.

Rewards

What the company's own policy page says it pays.

The policy page has no reward table. Here is what it says, in its own words.

Pays cash
Yes A bug bounty will only be paid to the first person who reports the corresponding security hole.
Safe harbor
Partial Please note that the extension of your activities to websites which are not included in the above list may be classified as illegal and punished accordingly.

Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original

Scope

21 assets you may test.

Domains 20

  • confirm.dzbank.de
  • derifin.dzbank.de
  • dialin.dzbank.de
  • dzbank.de
  • dzbbvservice.dzbank.de
  • dz-haltung.dzbank.de
  • finledger.dzbank.de
  • geschaeftsbericht.dzbank.de
  • guided-tour.dzbank.de
  • halbjahresfinanzbericht.dzbank.de
  • haltung.dzbank.de
  • i-net.dzbank.de
  • ingen.dzbank.de
  • institutionelle.dzbank.de
  • login.dzbank.de
  • psd2-xs2a.dzbank.de
  • rsp.support.dzbank.de
  • searchapp.dzbank.de
  • searchresult.dzbank.de
  • wertewelt.dzbank.de

Web 1

  • https://dzeg.dzbank.de

Rules

What the policy asks of you, and the bug types it won't reward, quoted from DZ BANK AG's policy. "We" in these lines means the program, not this site.

While testing

  • Do not publish any security vulnerabilities before we have fixed them.
  • Due to internal processes and the complexity involved, this "Responsible Disclosure" is valid for at least 120 days.
  • Access only the data necessary to prove the vulnerability.
  • Do not delete or modify any data.
  • Our internal and external services must not be disturbed, interrupted or impaired by DDoS attacks or in any other way.
  • Do not implement backdoors or similar. Use methods to obtain persistent access.
  • Do not carry out any attacks on the basis of "brute force" or "fuzzing".
  • Do not attack our end users in any way and do not trade in stolen user data.
  • Do not send phishing e-mails to third parties, including employees or partners of DZ BANK, and do not use any other social engineering techniques.

Not accepted

  • Complaints about services, products and/or equipment of DZ BANK AG and its affiliated companies
  • Questions and complaints regarding the availability of our web services
  • Phishing mails or fraud
  • All vulnerabilities, without a detailed description of the attack methodology or proof of exploitability
  • Automatic reports generated by scan tools
  • Our policies regarding SPF/DKIM/DMARC Records
  • HTML character set error messages such as "does not specify charset" or "unrecognized charset
  • The absence of Secure/HTTP Only Flags for non-sensitive cookies
  • The absence of HTTP Strict Transport Security (HSTS)
  • Clickjacking or the absence of X-frame options
  • Cachebare HTTPS response pages on non-critical pages
  • Use of insecure SSL/TLS ciphers
  • Vulnerabilities that only affect users with outdated browsers and reduced security settings
  • Security holes that are only caused by the use of an outdated browser do not entitle to the payment of a reward.

Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original

Changes

Tracked since 12 Nov 2026. Last checked 3 hours ago.

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

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.