Warning
johnisn't to be used on untrusted input and should be run with the lowest privileges necessary;- it is unrealistic to have zero bugs, it is a consequence of how many formats and different parsers it has.
- prefer sandboxed versions of packages (snap, flatpak or Docker) whenever you need "hardening".
Additionally:
Important
- the MPI library (not used by packages from this repository) tends to open and listening ports,
so it can expose itself,
john, and the underlying system to direct network-based attacks as well; - use the
--formatoption to reduce parsing of input files; - if you are compiling
johnyourself, you can also reduce dependencies by removing plugin formats or ignoring optional libraries/features, thus minimizing the attack surface for potential security threats.
The john community releases patches for security vulnerabilities. Which versions are eligible for
receiving such patches depends on the version:
| Version | Supported | Note |
|---|---|---|
| upstream bleeding code | ✔ | Under development version |
| latest release | ✔ | Most recent release |
| any previous release | ❌ | No longer maintained |
Please just report issues in public right away:
- if you are worried about a package or its dependencies, create a bug report here;
- otherwise, at https://github.com/openwall/john/issues.
The john community will send you a response indicating the next steps in handling your report. After the initial
response to your report, the security team will keep you informed of progress and may request additional
information or guidance.
If the issue is confirmed, john community will release a patch as soon as possible depending on complexity.
Please note that for security purposes all inputs are considered trusted by upstream john, and it should
be assumed that input can control the program in arbitrary ways. In cases where greater robustness is desired,
use the snap, the flatpak or the Docker version; you can also use the --format option to reduce parsing
of input files.
When you think John The Ripper has a potential security vulnerability.
When you know of or suspect a potential vulnerability on another project that is used by john.
For example, in a packaged dependency.