Skip to content

University of York

Vulnerability disclosure program on Self-hosted york.ac.uk

Accepting reports Full safe harbor
Top reward
No cash rewards
Top severity paid
Not published
Assets in scope
4
Public CVEs
0
Last change
No changes yet

At a glance

What to know before you start testing.

No cash rewards
A disclosure program: you report for credit, not money.
Report by email
[email protected]
Full safe harbor
Good-faith research is authorised; no legal action.
Replies within 7 days
As the policy promises.
Publish after a fix
Coordinate the timing with the company.

Rewards

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

This program does not pay cash rewards.

Response
Within 7 days Respond and acknowledge your report within seven calendar days
Safe harbor
Full Promise not to take legal action against you for accessing (or attempting to access) our systems, as long as this policy is followed and you do not cause foreseeable harm
Hall of fame
Yes If you wish, acknowledge your assistance to the University on this page

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

Scope

4 assets you may test, 3 excluded.

Networks 3

  • 144.32.0.0/16
  • 2001:0630:0061::/48
  • 2001:630:61::/48 No bounty

Domains 1

  • york.ac.uk
Out of scope (3)
  • All systems not explicitly mentioned as in-scope
  • Check in
  • Yorsearch

Rules

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

While testing

  • Respect privacy. Contact us immediately if you access anyone else’s data - personal or otherwise.
  • You must not save, store or transmit this information.
  • Act in good faith. You should report the vulnerability to us with no conditions attached.
  • Allow us a reasonable amount of time (at least 90 days) to resolve the vulnerability before publicly disclosing it.
  • Exfiltrate data - instead use a proof of concept to demonstrate a vulnerability
  • Perform social engineering
  • Perform any testing of physical security
  • Use automated scanners/fuzzers
  • Only test vulnerabilities using your own accounts, or accounts that you have permission to test with.

Not accepted

  • Missing security headers that may be best-practice but do not impact on the security of the system in this instance
  • Support for older, but non-exploitable, protocols and cipher suites such as TLS 1.1
  • Fingerprinting/version detection
  • Out of date software, with no exploitable vulnerability.

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 11 Nov 2026. Last checked 5 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.