Caution
While we certainly allow the usage of LLMs / AI as a tool for vulnerability research, we do reserve the right to reject security advisories which are clearly auto-generated and which do not meet the following criteria:
- You MUST disclose whether AI has been used.
- You MUST specify where and how AI was involved in the process.
- You MUST write the security advisory yourself.
We only support the latest official release version with respect to security vulnerabilities. Thus, only the latest or then the upcoming next release version will receive vulnerability fixes and security updates. A vulnerability may however be reported for any version, unless it already has been fixed with a later release version.
Important
- Please always verify that no later release version exists which fixes the vulnerability.
- Please always consult the documentation first before creating a vulnerability report: https://safeexambrowser.org/windows/win_usermanual_en.html.
- Please always attach the log file(s) of the affected session(s)! They can be found under
%LocalAppData%\SafeExamBrowser\Logs.
Describe the Vulnerability A clear and concise description of what the vulnerability is.
Proof of Concept Please provide a proof-of-concept implementation in a private repository or as attachment.
Steps to Reproduce Steps to reproduce the behavior:
- Go to '...'
- Click on '....'
- Scroll down to '....'
- See ...
Expected Behavior A clear and concise description of what you expected to happen.
Screenshots If applicable, add screenshots to help explain your problem.
Version Information
- OS: [e.g. Windows 10 Professional, Version 1803]
- SEB-Version [e.g. SEB 3.0.1]
Additional Context Add any other context about the vulnerability here.