SECURITY.md

Coder welcomes feedback from security researchers and the general publicto help improve our security. If you believe you have discovered a vulnerability,privacy issue, exposed data, or other security issues in any of our assets, wewant to hear from you. This policy outlines steps for reporting vulnerabilitiesto us, what we expect, what you can expect from us.

You can see the pretty versionhere

If an attacker could fully compromise a Coder installation, they could spinup expensive workstations, steal valuable credentials, or steal proprietarysource code. We take this risk very seriously and employ routine pen testing,vulnerability scanning, and code reviews. We also welcome the contributionsfrom the community that helped make this product possible.

Please report security issues tosecurity@coder.com, providingall relevant information. The more details you provide, the easier it will befor us to triage and fix the issue.

Our primary concern is around an abuse of the Coder application that allowsan attacker to gain access to another users workspace, or spin up unwantedworkspaces.

• DOS/DDOS attacks affecting availability --> While we do support rate limitingof requests, we primarily leave this to the owner of the Coder installation. Ourrationale is that a DOS attack only affecting availability is not a valuabletarget for attackers.
• Abuse of a compromised user credential --> If a user credential is compromisedoutside of the Coder ecosystem, then we consider it beyond the scope of our application.However, if an unprivileged user could escalate their permissions or gain accessto another workspace, that is a cause for concern.
• Vulnerabilities in third party systems --> Vulnerabilities discovered inout-of-scope systems should be reported to the appropriate vendor or applicable authority.

When working with us, according to this policy, you can expect us to:

• Respond to your report promptly, and work with you to understand and validate your report;
• Strive to keep you informed about the progress of a vulnerability as it is processed;
• Work to remediate discovered vulnerabilities in a timely manner, within our operational constraints; and
• Extend Safe Harbor for your vulnerability research that is related to this policy.

In participating in our vulnerability disclosure program in good faith, we ask that you:

• Play by the rules, including following this policy and any other relevant agreements.If there is any inconsistency between this policy and any other applicable terms, theterms of this policy will prevail;
• Report any vulnerability you’ve discovered promptly;
• Avoid violating the privacy of others, disrupting our systems, destroying data, and/orharming user experience;
• Use only the Official Channels to discuss vulnerability information with us;
• Provide us a reasonable amount of time (at least 90 days from the initial report) toresolve the issue before you disclose it publicly;
• Perform testing only on in-scope systems, and respect systems and activities whichare out-of-scope;
• If a vulnerability provides unintended access to data: Limit the amount of data youaccess to the minimum required for effectively demonstrating a Proof of Concept; andcease testing and submit a report immediately if you encounter any user data during testing,such as Personally Identifiable Information (PII), Personal Healthcare Information (PHI),credit card data, or proprietary information;
• You should only interact with test accounts you own or with explicit permission from
• the account holder; and
• Do not engage in extortion.

There aren’t any published security advisories