Hide last authors
Ricardo Rodríguez 9.1 1 {{box cssClass="floatinginfobox" title="**Contents**"}}
2 {{toc/}}
3 {{/box}}
Silvia Macovei 5.1 4
Caleb James DeLisle 6.1 5 = Security related features =
Ricardo Rodríguez 9.1 6
Caleb James DeLisle 6.1 7 XWiki offers some features for protecting security and some features which have security implications.
vmassol 1.2 8
Caleb James DeLisle 6.1 9 == Admin password ==
Ricardo Rodríguez 9.1 10
Vincent Massol 13.2 11 The default password for the ##Admin## user is ##admin##. Make sure you change the password.
Vincent Massol 2.1 12
Thomas Mortagne 13.1 13 You could also remove that user but first you need to make sure it's not used as author of any page as it might create issue otherwise (some standard pages require their author to have enough right to be taken into account).
14
Caleb James DeLisle 6.1 15 == Superadmin account ==
Ricardo Rodríguez 9.1 16
Vincent Massol 13.2 17 XWiki provides a ##superadmin## account. It is special, because:
Thomas Mortagne 13.1 18
Sergiu Dumitriu 1.3 19 * It is not stored in the database
20 * It cannot be modified in any way
21 * It always has full access, regardless of the rights settings
22
Silvia Macovei 5.1 23 {{warning}}
Manuel Smeria 12.5 24 Because the Superadmin account is so powerful, it is not safe to leave it enabled for a long time.
Silvia Macovei 5.1 25 {{/warning}}
Sergiu Dumitriu 1.5 26
Manuel Smeria 12.5 27 By default, this account is disabled. To enable it, you have to edit ##<xwiki-dir>/WEB-INF/xwiki.cfg##, uncomment the ##xwiki.superadminpassword=system## line and set a proper password. To disable it, just comment this line. Remember to restart the servlet container after changing ##xwiki.cfg##.
Sergiu Dumitriu 1.3 28
Silvia Macovei 5.1 29 {{info}}
30 Using this superadmin account is useful when you cannot log in anymore, for example when you forgot your admin user password, if you messed up some rights or if you have deleted your admin user by mistake.
31 {{/info}}
Vincent Massol 1.4 32
Caleb James DeLisle 6.1 33 == Cookies ==
Ricardo Rodríguez 9.1 34
Caleb James DeLisle 6.1 35 By default XWiki (as with most of the web) identifies users who have already logged in by setting cookies. These can be the target of attacks.
vmassol 1.1 36
Caleb James DeLisle 6.1 37 === Cookie Encryption Keys ===
Ricardo Rodríguez 9.1 38
Ecaterina Moraru (Valica) 21.4 39 When a user logs in, three cookies are saved on his machine containing the username, password and a "nothing up my sleeve" hash. The cookies are encrypted so that nobody having access to them can see the username/password. This encryption is done using 2 configuration parameters located in the //xwiki.cfg// configuration file. This file is located in //WEB-INF/// in the XWiki WAR (see the [[Installation guide>>Documentation.AdminGuide.Installation]] for where it's installed).
40 It's important you edit the //[[xwiki.cfg>>Documentation.AdminGuide.Configuration#HSamplexwiki.cfg]]// file to modify the cookie authentication and encryption keys as they use default values when you install XWiki and these predefined values could be used by an attacker to decipher the username and password. To prevent this, change the following 2 configuration parameters:
Thomas Mortagne 13.1 41
Silvia Macovei 5.1 42 * //xwiki.authentication.validationKey//
43 * //xwiki.authentication.encryptionKey//
vmassol 1.1 44
Vincent Massol 22.1 45 See the [[Authentication parameters section>>Documentation.AdminGuide.Authentication.WebHome#HAuthenticationparameters]] for more details.
Caleb James DeLisle 6.1 46
Thomas Mortagne 17.1 47 In future versions we'd like to generate random and host-dependent key pairs at installation time (see the following [[issue>>https://jira.xwiki.org/browse/XWIKI-542]] for details).
Caleb James DeLisle 6.1 48
49 === Encrypt cookies using IP address ===
Ricardo Rodríguez 9.1 50
Vincent Massol 23.2 51 Even if the password cannot be extracted from the cookie, the cookies might be stolen (see [[XSS>>Documentation.AdminGuide.Security#HCrossSiteScripting]]) and used as they are. To limit this by default, the cookies are blocked from being used except by the same IP address that was used to create them.
Caleb James DeLisle 6.1 52
Vincent Massol 23.2 53 You can disable this by setting the [[##xwiki.cfg##>>Documentation.AdminGuide.Configuration#HSamplexwiki.cfg]] parameter ##xwiki.authentication.useip## to false.
54
Alex Busenius 7.1 55 == Override version information ==
56
Ecaterina Moraru (Valica) 20.1 57 By default, the exact XWiki version is shown in the footer of every page. This is not harmful by itself, but can provide useful information to the attacker, who can use known vulnerabilities against this version.
Alex Busenius 7.1 58
Simon Urli 23.3 59 You can change the version string shown in the footer using the [[Administration Application>>extensions:Extension.Administration Application]]. Click on the ##Presentation## icon and change the version string in the //Version// field. Please note that with this solution, the version can still be find through a REST request on the wiki.
Alex Busenius 7.1 60
Manuel Smeria 12.5 61 If you want to be sure the version is definitely not leaked somewhere else, you can replace the file //WEB-INF/version.properties// by your own version with the following content: {{code}}version=your version string here{{/code}}.
Alex Busenius 7.1 62
Caleb James DeLisle 6.1 63 = Discussion of attack vectors =
Ricardo Rodríguez 9.1 64
Caleb James DeLisle 6.1 65 Perfect security is generally considered impossible. With simple static HTML servers we can have near perfect security but those are not very useful. This document discusses different threat models and how to fortify against each. These attacks are grouped by type of access gained if successful. More dangerous attacks are near the top yet the most common attacks are less dangerous (and easier to perform) and will be seen at the bottom.
66
67 == Server root attacks ==
Ricardo Rodríguez 9.1 68
Caleb James DeLisle 6.1 69 This attack is characterized by assent of power in the operating system and is largely beyond the scope of this document as it is the responsibility of the operating system to prevent users ascending power.
70
71 === Likelihood / Known Issues ===
Ricardo Rodríguez 9.1 72
Caleb James DeLisle 6.1 73 Not a very common attack method.
74
75 === Mitigation Methods ===
Ricardo Rodríguez 9.1 76
Caleb James DeLisle 6.1 77 * Run a decent operating system
Manuel Smeria 12.5 78 * Run the Java VM with XWiki under its own username, only give this user permissions to files needed for the operation of XWiki and make sure this user doesn't have sudo access
Caleb James DeLisle 6.1 79 * Don't run extraneous processes on the server
80 * Run services on non-standard ports (ssh)
81 * Firewall all ports not explicitly needed
82
83 == Java VM attacks ==
Ricardo Rodríguez 9.1 84
Caleb James DeLisle 6.1 85 This attack is characterized by the attacker running arbitrary code on Java and perhaps using Java level security flaws to execute native code thus gaining access in the user level of the Java VM process.
86
87 === Likelihood / Known Issues ===
Ricardo Rodríguez 9.1 88
Manuel Smeria 12.5 89 * XWiki requires reflection of private fields and variables for the [[component module>>extensions:Extension.Component Module]] This means that jsr223 scripts such as Groovy and Python are able to read and write any field or variable in the system which may lead to execution of native code via Java Native Access. Virtual wikis are not insulated against this attack method and as such virtual wiki administrators cannot be given programming permission (note that there is another reason for not giving wiki admin programming rights in a farm, it is because you may access any document without rights being checked, even in another wiki). This flaw could lead to dumping of connected databases, however user passwords are SHA-512 hashed (see [[this issue>>http://jira.codehaus.org/browse/GROOVY-1875]] for more details.
90 ** This attack method requires the use of a registered username which has programming rights
Caleb James DeLisle 6.1 91
92 === Mitigation Methods ===
Ricardo Rodríguez 9.1 93
Manuel Smeria 12.5 94 * Enable a SecurityManager which peeks at the calling stack and only allows unchecked reflection if called by the component manager
95 * Disable Groovy entirely
96 * Guard programming rights closely, have a special username just for saving documents which contain approved Groovy scripts
Caleb James DeLisle 6.1 97
98 == Database Injection attacks ==
Ricardo Rodríguez 9.1 99
Caleb James DeLisle 6.1 100 Such an attack happens from inside of unsafe scripting and results in unintended information being given up by the database.
101
102 === Likelihood / Known Issues ===
Ricardo Rodríguez 9.1 103
Caleb James DeLisle 6.1 104 * XWiki uses Hibernate as a database controller so some of the injection methods are mitigated. XWiki gives you the capability to create safe scripts and unsafe scripts.
105 ** This attack method may often be performed without a registered username.
106
107 === Mitigation Methods ===
Ricardo Rodríguez 9.1 108
Thomas Mortagne 13.1 109 * You can use this groovy snippet to test your database to see if it supports [[stacked queries>>http://ferruh.mavituna.com/sql-injection-cheatsheet-oku/#StackingQueries]]. If your database does not support stacked queries, injection in a SELECT query can only lead to additional arbitrary SELECT queries:(((
Ricardo Rodríguez 9.1 110 {{code language="java"}}
Caleb James DeLisle 6.1 111 {{groovy}}
112 try {
113 session = xcontext.getContext().getWiki().getHibernateStore().getSessionFactory().openSession();
114 session.connection().createStatement().execute("begin transaction; rollback;");
115 println("Your database supports stacked queries.")
116 } catch (Exception e) {
117 println("Your database does not support stacked queries.");
118 } finally {
119 try {
120 session.close()
121 } catch (Exception e) {}
122 }
123 {{/groovy}}
124 {{/code}}
Manuel Smeria 12.5 125 )))
126 * Configure your database to log or if possible disable comment syntax {{code language="none"}} -- /* */ and # {{/code}}. Comments are not used by Hibernate and are central to most of the more dangerous SQL injection.
127 * When designing scripts avoid the temptation to concatenate user input into database queries
Caleb James DeLisle 6.1 128
129 **WRONG:**
130
131 {{code}}
132 #set($x = $xwiki.searchDocuments("where doc.fullName = '${userContent}'"))
133 {{/code}}
134
Manuel Smeria 12.5 135 If the user enters: {{code}} ' or doc.hidden = 1 or doc.fullName = ' {{/code}} your code will create the Hibernate query: {{code language="sql"}}where doc.fullName = '' or doc.hidden = 1 or doc.fullName = ''{{/code}}.
Caleb James DeLisle 6.1 136
137 This may not be a horrible outcome but it is not what you wanted and others surely can invent far more dangerous injections than this.
138 Fortunately Hibernate itself protects against the worst type of injection such as:
139
Ricardo Rodríguez 9.1 140 {{code language="sql"}}
Caleb James DeLisle 6.1 141 Embarrassing Mistake'); DROP TABLE xwikidoc;--
142 {{/code}}
143
Manuel Smeria 12.5 144 This is because it does not allow multiple commands in one call and does not allow the ~-~- comment syntax (can be bypassed in some versions; see above).
Caleb James DeLisle 6.1 145
Manuel Smeria 12.5 146 **RIGHT:**
Caleb James DeLisle 6.1 147
148 {{code}}
149 ## We are passing a ? in the query and then passing the parameter as a list (Velocity notation for list is [element, element] )
150 #set($x = $xwiki.searchDocuments("where doc.fullName = ?", [$userContent]))
151 {{/code}}
152
153 Your code will now instruct Hibernate to name the userContent parameter and pass it to the database separately from the query. The above injection trick will not work.
154
Manuel Smeria 12.5 155 * Avoid "Privileged API" whenever possible and only use non API when absolutely necessary. If each of your calls requires you to pass the context as a parameter, you're doing it wrong.
Caleb James DeLisle 6.1 156
Vincent Massol 21.3 157 For more information check the [[XWiki API Reference>>platform:DevGuide.API]].
Caleb James DeLisle 6.1 158
159 == Cross Site Scripting ==
Ricardo Rodríguez 9.1 160
Caleb James DeLisle 6.1 161 Cross site scripting or XSS is the least harmful to the server of all attack methods, however it is the most common.
Manuel Smeria 12.5 162 XSS can lead to users altering documents which they didn't want to or having their authentication cookies copied. XSS can also lead to exploitation of web browsers and plugins such as pdf or ActiveX. Such exploits often install malware.
Caleb James DeLisle 6.1 163
164 === Attack vectors (persistent injection) ===
Ricardo Rodríguez 9.1 165
Caleb James DeLisle 6.1 166 Persistent injection is characterized by saving content in the system which when loaded by the unwitting user, executes as javascript in their browser. This is the more dangerous variety because it sits in a page waiting for a victim.
167
168 1. Persistent injection through XWiki document content by editing the document.
169 2. Persistent injecting through comments.
170
171 ==== Likelihood / Known Issues ====
Ricardo Rodríguez 9.1 172
Caleb James DeLisle 6.1 173 * XWiki syntax 1.0 does not filter out HTML so script injection is possible
Thomas Mortagne 17.1 174 * XWiki syntax 2.0 contains html macro which when invoked allows injection of raw html and script. There is still no safe way to disable this (see [[this issue>>https://jira.xwiki.org/browse/XWIKI-3953]] for more information.
Manuel Smeria 12.5 175 ** This attack method requires the attacker to have a registered username (unless anonymous editing or commenting is allowed).
Caleb James DeLisle 6.1 176
177 ==== Mitigation Methods ====
Ricardo Rodríguez 9.1 178
Thomas Mortagne 13.1 179 * The only way to be sure that script cannot be injected in content (xwiki/1.0 or xwiki/2.0) is to make that content completely passive as follows:(((
Caleb James DeLisle 6.1 180 {{code}}
181 {{html}}
182 $escapetool.html($userContent)
183 {{/html}}
184 {{/code}}
Thomas Mortagne 13.1 185 )))There are however some methods to minimize the risk:
Manuel Smeria 12.5 186 * Disable creation of syntax 1.0 pages. **NOTE**: Pages which are already written in syntax 1.0 can still be altered and should be updated to syntax 2.0, otherwise they must have edit permission locked down so that only authorized users may edit them.
187 * Force unauthorized users to post through a script which escapes //~{~{// (double squigly brackets) because there is currently no way to prevent injection of html macro for unauthorized users.
188 * Set up ObservationManager to scan all page content and object property updates for HTML macro invocation and alert a moderator.
Ricardo Rodríguez 9.1 189
Caleb James DeLisle 6.1 190 === Attack vectors (reflective injection) ===
Ricardo Rodríguez 9.1 191
Caleb James DeLisle 6.1 192 Reflective injection is characterized by convincing a user to click on a specially crafted link which causes a page to generate javascript.
193
194 1. Reflective injection through form fields.
195
196 ==== Mitigation Methods ====
Ricardo Rodríguez 9.1 197
Manuel Smeria 12.5 198 Advise admins to use addons such as [[noscript>>https://addons.mozilla.org/en-US/firefox/addon/noscript/]] which will detect reflective injection attacks and warn the user when it suspects foul play and also avoid clicking on suspicious links.
Caleb James DeLisle 6.1 199
Manuel Smeria 12.5 200 * when content is loaded from request parameters into a form field, make sure it is escaped using [[EscapeTool>>http://velocity.apache.org/tools/devel/generic/EscapeTool.html]]
Caleb James DeLisle 6.1 201
202 **WRONG:**
203
Ricardo Rodríguez 9.1 204 {{code language="xml"}}
Caleb James DeLisle 6.1 205 <input type=text value="$request.get('name')" />
206 {{/code}}
207
208 **RIGHT:**
209
Ricardo Rodríguez 9.1 210 {{code language="xml"}}
Caleb James DeLisle 6.1 211 <input type=text value="$escapetool.html($request.get('name'))" />
212 {{/code}}
213
214 == Cross site request forgery (CSRF) ==
Ricardo Rodríguez 9.1 215
Caleb James DeLisle 6.1 216 The basis of this attack is that a foreign website can craft a malicious link or form which points to the save action in your system and when clicked by a logged in user will cause the user to save the page.
217
218 === Likelihood / Known Issues ===
Ricardo Rodríguez 9.1 219
Manuel Smeria 12.5 220 Currently there is no system implemented to prevent form submission from external sites. See discussion in mailing list about implementing [[secret tokens>>http://lists.xwiki.org/pipermail/devs/2010-March/017727.html]].
Caleb James DeLisle 6.1 221
222 === Mitigation Methods ===
Ricardo Rodríguez 9.1 223
Manuel Smeria 12.5 224 Advise admins to use addons such as [[noscript>>https://addons.mozilla.org/en-US/firefox/addon/noscript/]] which will help prevent automatic form submission by an attack site and also avoid clicking on suspicious links.
Vincent Massol 19.1 225
Vincent Massol 19.2 226 = Advisory Notices =
Vincent Massol 19.1 227
228 Here's a list of sites offering security advisory notices about XWiki:
Ecaterina Moraru (Valica) 20.1 229
Vincent Massol 19.1 230 * [[nvd.nist.gov>>https://nvd.nist.gov/vuln/search/results?adv_search=false&form_type=basic&results_type=overview&search_type=all&query=xwiki]]
231 * [[www.cvedetails.com>>http://www.cvedetails.com/product/6856/Xwiki-Xwiki.html?vendor_id=3885]]
232 * [[vuldb.com>>https://vuldb.com/fr/?search]] (need to search for ##xwiki##)
233 * [[vulners.com>>https://vulners.com/search?query=xwiki]]

Get Connected