This Eclipse Foundation Project adheres to the Eclipse Foundation Vulnerability Reporting Policy.

If you think you have found a vulnerability in this repository, please report it to us through coordinated disclosure.

Please do not report security vulnerabilities through public issues, discussions, or change requests.

Instead, you can report it using one of the following ways:

• Contact the Eclipse Foundation Security Team via email
• Create a confidential issue in the Eclipse Foundation Vulnerability Reporting Tracker
• Report a vulnerability directly via private vulnerability reporting on GitHub

You can find more information about reporting and disclosure at the Eclipse Foundation Security page.

Please include as much of the information listed below as you can to help us better understand and resolve the issue:

• The type of issue (e.g., buffer overflow, SQL injection, or cross-site scripting)
• Affected version(s)
• Impact of the issue, including how an attacker might exploit the issue
• Step-by-step instructions to reproduce the issue
• The location of the affected source code (tag/branch/commit or direct URL)
• Full paths of source file(s) related to the manifestation of the issue
• Any special configuration required to reproduce the issue
• Any log files that are related to this issue (if possible)
• Proof-of-concept or exploit code (if possible)

This information will help us triage your report more quickly.

Otterdog executes with the credentials of the organizations it manages. Some of its inputs are trusted and are equivalent to code, in particular the otterdog.json configuration and the default configuration referenced by its base_template, whose Python scripts otterdog executes. Issues that require control of such an input are not considered vulnerabilities. The trusted and untrusted inputs are listed in the threat model.