We take the security of Rat GUI, the Rat Library and our websites seriously. If you believe you have found a security vulnerability, please report it to us privately so we can fix it before it is made public. We welcome reports from security researchers, customers and anyone else.

Known vulnerabilities in our releases

Every supported release of Rat GUI is scanned daily for known vulnerabilities (CVEs) in the third-party components it ships. Each finding is listed with our assessment of what it means for Rat GUI: not affected, affected, or under investigation.

Our commitment: when a fixed version of a component exists, Rat GUI updates to it within fifteen days. Where no fixed version exists yet, Rat GUI ships the newest version available and the finding stays listed until it is fixed.

View the security assessment ↗

For each release it also provides a machine-readable OpenVEX document and the software bill of materials (SBOM) of each installer, for use with your own vulnerability scanner.

How to report

Email security@rat-gui.com. Please do not report security issues through our general enquiries address, public GitLab issues or social media.

Please include as much of the following as you can:

  • The affected product and version (Rat GUI, the Rat Library, rat-gui.com or littlebeastengineering.com).
  • The operating system and version you used.
  • A description of the issue and the steps to reproduce it, or a proof of concept.
  • What an attacker could achieve by exploiting it.
  • How we can contact you, and whether you would like to be credited.

What you can expect from us

  • We will acknowledge your report within 5 working days.
  • We will investigate, confirm whether the issue is a vulnerability and assess its severity, and keep you informed of our progress.
  • We aim to release a fix within 90 days of your report. Critical issues are prioritised and fixed as quickly as possible.
  • We will agree a disclosure date with you, normally once a fix is available. We ask that you do not disclose the issue publicly before then.
  • With your permission, we will credit you in the release notes.

Scope

In scope:

  • Rat GUI for Windows, macOS and Linux.
  • The open-source Rat Library on GitLab.
  • The websites rat-gui.com and littlebeastengineering.com.

Out of scope:

  • Services run by third parties, such as our licensing provider and GitLab itself. Please report those to the provider directly.
  • Denial-of-service testing, social engineering, and physical attacks.

Safe harbour

We will not take legal action against anyone who reports a vulnerability in good faith and in line with this policy. That means avoiding harm to our users, our data and our services, only accessing what you need to show the issue, and giving us reasonable time to fix it before disclosing it.

This policy is also published in machine-readable form at /.well-known/security.txt.