| version | supported |
|---|---|
| 0.5.x | yes |
CellScope reads binaries that you did not write, so a crafted file should never be able to do anything worse than make CellScope report an error. Please report privately if you find a way for a file to:
- run code on the machine analyzing it
- write files outside the folder you told CellScope to use
- crash or hang CellScope in a way that can be triggered on purpose
Two things are not security issues, because they work as designed:
- Extensions run code. An extension is ordinary Python, and loading one runs it with your permissions. Only load extensions you trust, as docs/EXTENSIONS.md explains.
- CellScope does not decrypt or bypass anything. It works on decrypted files you already have, from software you own.
Use GitHub's private vulnerability reporting: open the Security tab of the CellScope repository and choose Report a vulnerability. Please include:
- what the problem is and what an attacker could do with it
- the CellScope version, your OS, and your Python version
- how to reproduce it, ideally with a small synthetic file built for the purpose, never a file from a commercial game
Please do not open a public issue for a security problem.
I will acknowledge your report as soon as I can, keep you updated while I work on a fix, and credit you in the release notes unless you would rather stay anonymous.