1
1
Security is very important to us. If you discover any issue regarding security, please disclose
2
- the information responsibly by sending an email to security (at) wekan.team and not by
2
+ the information responsibly by sending an email to support (at) wekan.team using
3
+ [ this PGP public key] ( https://raw.githubusercontent.com/wekan/wekan/master/support-at-wekan.team_pgp-publickey.asc ) and not by
3
4
creating a GitHub issue. We will respond swiftly to fix verifiable security issues.
4
5
5
6
We thank you with a place at our hall of fame page, that is
6
- at https://wekan.github.io/hall-of-fame . Others have just posted public GitHub issue,
7
- so they are not at that hall-of-fame page.
7
+ at https://wekan.github.io/hall-of-fame
8
8
9
9
## How should reports be formatted?
10
10
@@ -34,60 +34,12 @@ and we don't have any permissions to do security scans on those donated servers
34
34
Please don't perform research that could impact other users. Secondly, please keep
35
35
the reports short and succinct. If we fail to understand the logics of your bug, we will tell you.
36
36
37
- You can [ Install Wekan] ( https://github.com/wekan/wekan/releases ) to your own computer
37
+ You can [ Install Wekan] ( https://github.com/wekan/wekan-php /releases ) to your own computer
38
38
and scan it's vulnerabilities there.
39
39
40
- ## About Wekan versions
40
+ ## About Wekan-php versions
41
41
42
- There are only 2 versions of Wekan: Standalone Wekan, and Sandstorm Wekan.
43
-
44
- ### Standalone Wekan Security
45
-
46
- Standalone Wekan includes all non-Sandstorm platforms. Some Standalone Wekan platforms
47
- like Snap and Docker have their own specific sandboxing etc features.
48
-
49
- Standalone Wekan by default does not load any files from Internet, like fonts, CSS, etc.
50
- This also means all Standalone Wekan functionality works in offline local networks.
51
- Wekan is used by companies that have [ thousands of users] ( https://github.com/wekan/wekan/wiki/AWS ) and at healthcare.
52
-
53
- Wekan uses xss package for input fields like cards, as you can see from
54
- [ package.json] ( https://github.com/wekan/wekan/blob/devel/package.json ) . Other used versions can be seen from
55
- [ Meteor versions file] ( https://github.com/wekan/wekan/blob/devel/.meteor/versions ) .
56
- Forms can include markdown links, html, image tags etc like you see at https://wekan.github.io .
57
- It's possible to add attachments to cards, and markdown/html links to files.
58
-
59
- Wekan attachments are not accessible without logging in. Import from Trello works by copying
60
- Trello export JSON to Wekan Trello import page, and in Trello JSON file there is direct links to all publicly
61
- accessible Trello attachment files, that Standalone Wekan downloads directly to Wekan MongoDB database in
62
- [ CollectionFS] ( https://github.com/wekan/wekan/pull/875 ) format. When Wekan board is exported in
63
- Wekan JSON format, all board attachments are included in Wekan JSON file as base64 encoded text.
64
- That Wekan JSON format file can be imported to Sandstorm Wekan with all the attachments, when we get
65
- latest Wekan version working on Sandstorm, only couple of bugs are left before that. In Sandstorm it's not
66
- possible yet to import from Trello with attachments, because Wekan does not implement Sandstorm-compatible
67
- access to outside of Wekan grain.
68
-
69
- Standalone Wekan only has password auth currently, there is work in progress to add
70
- [ oauth2] ( https://github.com/wekan/wekan/pull/1578 ) , [ Openid] ( https://github.com/wekan/wekan/issues/538 ) ,
71
- [ LDAP] ( https://github.com/wekan/wekan/issues/119 ) etc. If you need more login security for Standalone Wekan now,
72
- it's possible add additional [ Google Auth proxybouncer] ( https://github.com/wekan/wekan/wiki/Let's-Encrypt-and-Google-Auth ) in front of password auth, and then use Google Authenticator for Google Auth. Standalone Wekan does have [ brute force protection with eluck: accounts-lockout and browser-policy clickjacking protection] ( https://github.com/wekan/wekan/blob/devel/CHANGELOG.md#v080-2018-04-04-wekan-release ) . You can also optionally use some [ WAF] ( https://en.wikipedia.org/wiki/Web_application_firewall )
73
- like for example [ AWS WAF] ( https://aws.amazon.com/waf/ ) .
74
-
75
- [ All Wekan Platforms] ( https://github.com/wekan/wekan/wiki/Platforms )
76
-
77
- ### Sandstorm Wekan Security
78
-
79
- On Sandstorm platform using environment variable Standalone Wekan features like Admin Panel etc are
80
- turned off, because Sandstorm platform provides SSO for all apps running on Sandstorm.
81
-
82
- [ Sandstorm] ( https://sandstorm.io ) is separate Open Source platform that has been
83
- [ security audited] ( https://sandstorm.io/news/2017-03-02-security-review ) and found bugs fixed.
84
- Sandstorm also has passwordless login, LDAP, SAML, Google etc auth options already.
85
- At Sandstorm code is read-only and signed by app maintainers, only grain content can be modified.
86
- Wekan at Sandstorm runs in sandboxed grain, it does not have access elsewhere without user-visible
87
- PowerBox request or opening randomly-generated API key URL.
88
- Also read [ Sandstorm Security Practices] ( https://docs.sandstorm.io/en/latest/using/security-practices/ ) and
89
- [ Sandstorm Security non-events] ( https://docs.sandstorm.io/en/latest/using/security-non-events/ ) .
90
- For Sandstorm specific security issues you can contact [ kentonv] ( https://github.com/kentonv ) by email.
42
+ There is only one prototype of Wekan-php, that does not even work yet.
91
43
92
44
## What Wekan bugs are eligible?
93
45
@@ -101,24 +53,11 @@ a security issue, we'd like to know about it, and also how to fix it:
101
53
- Authentication bypass
102
54
- Server-side code execution
103
55
104
- ## What Wekan bugs are NOT eligible?
56
+ ## What Wekan-php bugs are NOT eligible?
105
57
106
58
Typical already known or "no impact" bugs such as:
107
59
108
- - Brute force password guessign. Currently there is
109
- [ brute force protection with eluck: accounts-lockout ] ( https://github.com/wekan/wekan/blob/devel/CHANGELOG.md#v080-2018-04-04-wekan-release ) .
110
- - Security issues related to that Wekan uses Meteor 1.6.0.1 related packages, and upgrading to newer
111
- Meteor 1.6.1 is complicated process that requires lots of changes to many dependency packages.
112
- Upgrading [ has been tried many times, spending a lot of time] ( https://github.com/meteor/meteor/issues/9609 )
113
- but there still is issues. Helping with package upgrades is very welcome.
114
- - [ Wekan API old tokens not replaced correctly] ( https://github.com/wekan/wekan/issues/1437 )
115
- - Missing Cookie flags on non-session cookies or 3rd party cookies
116
- - Logout CSRF
117
- - Social engineering
118
- - Denial of service
119
- - SSL BEAST/CRIME/etc. Wekan does not have SSL built-in, it uses Caddy/Nginx/Apache etc at front.
120
- Integrated Caddy support is updated often.
121
- - Email spoofing, SPF, DMARC & DKIM. Wekan does not include email server.
60
+ - Well, nothing yet, because Wekan-php does not work at all yet.
122
61
123
62
Wekan is Open Source with MIT license, and free to use also for commercial use.
124
63
We welcome all fixes to improve security by email to security (at) wekan.team .
0 commit comments