Skip to content

Genetec

Bug bounty on security.txt genetec.com

Accepting reports Full safe harbor security.txt mentions bounty
Top reward
Not published
Top severity paid
Not published
Assets in scope
23
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]
Full safe harbor
Good-faith research is authorised; no legal action.

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 we run a private Bug Bounty program where selected researchers are invited to test our assets and are rewarded for valid vulnerability reports.
Safe harbor
Full We consider activities that adhere to this program as authorized and will not pursue legal action against you for responsibly disclosing vulnerabilities.

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

Scope

23 assets you may test.

Domains 12

  • autovu.cloud
  • autovu.com
  • clearance.network
  • clearid.io
  • curbsense.com No bounty
  • genetec.cloud
  • geneteccloud.com
  • genetec.com
  • genetec.one
  • login.genetec.com
  • ops.center
  • q2c.eu No bounty

Wildcard domains 11

  • *.autovu.cloud
  • *.autovu.com
  • *.clearance.network
  • *.clearid.io
  • *.curbsense.com No bounty
  • *.genetec.cloud
  • *.geneteccloud.com
  • *.genetec.com
  • *.genetec.one
  • *.ops.center
  • *.q2c.eu No bounty

Rules

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

While testing

  • Security researchers must submit VDP reports through our designated form .
  • Submissions sent through other channels will not be processed.

Not accepted

  • Vulnerabilities that rely on social engineering (this includes phishing attacks against Genetec employees)
  • Denial of Service Attacks (DOS)
  • Physical attempts against Genetec property or data centers
  • Attack that assumes admin control of a service machine
  • Missing best practices with no demonstrable security impact (i.e. missing HTTP headers, SSL/TLS configuration, etc.)
  • Insecure cookies for non-sensitive cookies or 3rd party cookies
  • Sending blind XSS by email or spamming Genetec employees
  • Vulnerable third party packages without proof of concept (ex. jQuery)
  • Missing DNS CAA record

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.