docs/security-and-privacy/statement-on-security/README.md
At its core, OpenProject is an open-source software that is developed and published on GitHub. Every change to the OpenProject code base ends up in an open repository accessible to everyone. This results in a transparent software where every commit can be traced back to the contributor.
Automated tests and manual code reviews ensure that these contributions are safe for the entire community of OpenProject. These tests encompass the correctness of security and access control features. We have ongoing collaborations with security professionals to test the OpenProject code base for security exploits.
For more information on security and data privacy for OpenProject, please visit: www.openproject.org/security-and-privacy.
security.txt
OpenProject uses the security.txt standard for defining security policies.
You can find our security.txt here: www.openproject.org/security.txt
Please see securitytxt.org for more information.
If you want to receive immediate security notifications via email as we publish them, please sign up to our security mailing list.
No messages except for security advisories or security related announcements will be sent there.
To unsubscribe, you will find a link at the end of every email.
Any security related information will also be published in the release notes and as GitHub Security Advisories.
OpenProject uses GitHub to manage and publish security advisory listings. All publicly known security issues on OpenProject with at least a medium CVSS score are reported as CVEs and can be found through these advisories. All published CVEs will also be listed on cve.org.
Next to GitHub advisories, you may also directly reach out to the security team via email using [email protected].
We take all facets of security seriously at OpenProject. If you want to report a security concern, have remarks, or contributions regarding security at OpenProject, please reach out to us at [email protected].
If you can, please send us a PGP-encrypted email using the following key:
You can also report a vulnerability directly in GitHub, if you prefer. When in doubt, please also send an informal email to [email protected] with the link to the advisory. The advisories allows us to communicate and collaborate privately with you, and it will remain private until we publish the vulnerability.
To help us validate and address the issue efficiently, your report should include:
Providing clear reproduction steps is essential. Reports that lack sufficient detail for us to validate the issue may take significantly longer to process.
Please adhere to the following rules when reporting or researching security issues:
We appreciate your time in every security report you communicate to us. There are a number of cases that can be viewed as security vulnerabilities, but for which we might either reject or not follow up with a full CVE publication. We still welcome you to reach out and discuss potential mitigations or attack vectors with us. Examples for these cases could be
dev branch, of course please also contact us for that.The severity of security issues is assessed on a case-by-case basis by our security team using the CVSS v3.1 calculator. We consider both the potential impact (e.g., a vulnerability affecting all users is more severe than one requiring specific conditions) and the difficulty to exploit (e.g., a vulnerability requiring administrator access or advanced permissions is less severe than one exploitable by unauthenticated users).
As a general guideline:
When we receive vulnerability reports from researchers or through internal identification, the following process takes place:
All vulnerabilities are treated with the highest priority. Critical and high impact vulnerabilities are aimed to be available as an upgradable fix within 21 days after confirmation of the vulnerability, so 14 days until the pre-announcement. This timeline represents our targets. Actual resolution times may vary depending on the complexity of the issue and the availability of our team.
A security issue is considered fixed only once the fix has been released for all supported versions affected by the issue.
For critical and high-severity vulnerabilities, subscribers of our security mailing list will receive a pre-release notification 7 days before the security release. This notification will include the planned release date and the severity of the issue, but will not include vulnerability details or patches. This gives administrators time to schedule maintenance windows and prepare for an upgrade.
Because OpenProject is open source, any fix committed to our public repository is inherently visible. Adding additional wait time between official releases and communication about vulnerabilities would allow exploitation of the vulnerabilities by simply reading the published code. For this reason, we follow a simultaneous disclosure approach:
Please note that OpenProject does not currently offer its own bug bounty program. For any security vulnerability you responsibly disclose to us, whether through another bug bounty program or through our website, we will do our best to give you appropriate credit. We will gladly reference your work, name, and website on every publication we make related to the security update.
OpenProject administrators can enforce authentication mechanisms and password rules to ensure users choose secure passwords according to current industry standards. Passwords stored by OpenProject are securely stored using salted bcrypt. Alternatively, external authentication providers and protocols (such as LDAP, SAML) can be enforced to avoid using and exposing passwords within OpenProject.
Administrators are provided with fine-grained role-based access control mechanisms to ensure that users are only seeing and accessing the data they are allowed to on an individual project level.
Admins can set a specific session duration in the system administration, so that it is guaranteed that a session is automatically terminated after inactivity.
Secure your authentication mechanisms with a second factor by TOTP and WebAuthn standards (or SMS, depending on your instance) to be provided by users upon logging in.
This badge shows the current status of your OpenProject installation. It will inform administrators of an installation on whether new releases or security updates are available for your platform.
Security updates allow a fast fix of security issues in the system. Relevant channels will be monitored regarding security topics and the responsible contact person will be informed. Software packages for security fixes will be provided promptly. Sign up to our security mailing list to receive all security notifications via e-mail.
Synchronize OpenProject users and groups with your company's LDAP to update users and group memberships based on LDAP group members.
With the single sign-on feature you can securely access OpenProject. Control and secure access to your projects with the main authentication providers.
Find out more about our GDPR compliance.