Vulnerability reporting

Report a security vulnerability

The RAF takes the security of our web site seriously. If you believe you have found a vulnerability in the RAF web site, you can report it at https://hackerone.com/34160193-e594-4c17-ad4d-27e0cbf22f70/embedded_submissions/new

Vulnerability Disclosure Policy

We recommend reading this disclosure policy fully before you report any vulnerabilities. This helps ensure that you understand the policy, and act in compliance with it.

Please note that this policy does not provide any form of indemnity for any actions if they are either in breach of the law or of this policy. It does not provide an indemnity from the RAF or any third party.

Scope

This disclosure policy applies only to vulnerabilities in the RAF products and services under the following conditions:

  • ‘In scope’ vulnerabilities must be original, previously unreported, and not already discovered by internal procedures.
  • Volumetric vulnerabilities are not in scope - meaning that simply overwhelming a service with a high volume of requests is not in scope.
  • Reports of non-exploitable vulnerabilities, or reports indicating that our services do not fully align with 'best practice', for example missing security headers, are not in scope.
  • TLS configuration weaknesses, for example 'weak' cipher suite support or the presence of TLS1.0 support, are not in scope.
  • The policy applies to everyone, including for example the RAF staff, third party suppliers and general users of the RAF public services.

Reporting

If you have discovered something you believe to be an in-scope security vulnerability, first you should check the above details for more information about scope, then submit a report on this page.

In your submission, include details of:

  • The website or page where the vulnerability can be observed.
  • A brief description of the type of vulnerability, for example an 'XSS vulnerability'.

Your report should provide a benign, non-destructive, proof of exploitation. This helps to ensure that the report can be triaged quickly and accurately. It also reduces the likelihood of duplicate reports, or malicious exploitation of some vulnerabilities, such as sub-domain takeovers.

What to expect

After you have submitted your report, we will respond to your report within 5 working days and aim to triage your report within 10 working days. We’ll also keep you informed about our progress throughout the process via HackerOne if you have registered for an account.

Priority for bug fixes or mitigations are assessed by looking at the impact severity and exploit complexity. Vulnerability reports might take some time to triage or address. You are welcome to enquire on the status of the process but should avoid doing so more than once every 14 days. The reason is to allow our teams to focus on the reports as much as possible.

When the reported vulnerability is resolved, or remediation work is scheduled, the Vulnerability Disclosure Team will notify you, and invite you to confirm that the solution covers the vulnerability adequately.

Guidance

You must NOT:

  • Access unnecessary amounts of data. For example, 2 or 3 records is enough to demonstrate most vulnerabilities, such as an enumeration or direct object reference vulnerability.
  • Use high-intensity invasive or destructive technical security scanning tools to find vulnerabilities.
  • Violate the privacy of the RAF users, staff, contractors, services or systems. For example, by sharing, redistributing and/or not properly securing data retrieved from our systems or services.
  • Communicate any vulnerabilities or associated details using methods not described in this policy.
  • Modify data in the RAF systems or services.
  • Disrupt the RAF services or systems.
  • Social engineer, 'phish' or physically attack RAF staff or infrastructure.
  • Disclose any vulnerabilities in the RAF systems or services to 3rd parties or the public, prior to the RAF confirming that those vulnerabilities have been mitigated or rectified. However, this is not intended to stop you notifying a vulnerability to 3rd parties for whom the vulnerability is directly relevant. An example would be where the vulnerability being reported is in a 3rd party software library or framework. Details of the specific vulnerability as it applies to the RAF must not be referenced in such reports.

We ask you to delete securely any and all data retrieved during your research as soon as it is no longer required or within 1 month of the vulnerability being resolved, whichever occurs first.

Legalities

This policy is designed to be compatible with common vulnerability disclosure good practice. It does not give you permission to act in any manner that is inconsistent with the law, or which might cause the RAF to be in breach of any of its legal obligations, including but not limited to:

  • The Computer Misuse Act (1990)
  • The General Data Protection Regulation 2016/679 (GDPR) and the Data Protection Act 2018
  • The Copyright, Designs and Patents Act (1988)
  • The Official Secrets Act (1989)

The RAF affirms that it will not seek prosecution of any security researcher who reports any security vulnerability on a RAF service or system, where the researcher has acted in good faith and in accordance with this disclosure policy.

Using Internet Explorer 8? Please switch to using Chrome if you can.