Project

General

Profile

Security issues » History » Version 57

Yannick Warnier, 31/05/2018 17:27

1 1 Yannick Warnier
h1. Security issues
2
3 6 Yannick Warnier
{{>toc}}
4
5 26 Yannick Warnier
h2. Security track record
6
7
Chamilo LMS has a great track record for fixing reported security issues, working together with security actors, publishing fixes prior to the official publication of the vulnerabilities on official sites. 
8
9 41 Yannick Warnier
So far, in the history of the project (since late 2009), all (but one) vulnerabilities have been fixed less than 72h after they were reported to us, and the process of code revision by packagers before inclusion (no unchecked plugin) has always been followed, making it *the most secure open source e-learning platform* to date.
10 26 Yannick Warnier
11 1 Yannick Warnier
You can see a graphical representation of the reports and fixes here (with corresponding links to check details): http://www.cvedetails.com/product/26528/Chamilo-Chamilo-Lms.html?vendor_id=12983 (navigate and check other LMSes to compare their security track record).
12 31 Yannick Warnier
13
If you consider using another LMS, please (for your own sake) check its security track (sometimes, months can pass before fixes are provided publicly, like here http://securitytracker.com/id/1029437)
14 26 Yannick Warnier
15 47 Yannick Warnier
Check [[Secure_development_policy]] for more info.
16 26 Yannick Warnier
17 17 Yannick Warnier
h2. Security flaws reporting procedure
18 1 Yannick Warnier
19 17 Yannick Warnier
If you have found a new security flaw in Chamilo, please send us an e-mail at security@chamilo.org and info@chamilo.org, including "Chamilo Vulnerability" in your topic line. We *will* respond quickly to these (usually within 24h), so if you don't receive an answer, please consider it might not have been received and send it again.
20
In the worst case, open an issue in this issues tracking system to call for our attention, but please do not publish the flaw until a patch has been developed.
21
22
h2. Security flaws fixing procedure
23
24
Security matters to us. A lot. So when we receive a security flaw report, we will treat it very quickly (usually in a matter of 1 to 4 days).
25
Our procedure is as follows:
26
# we will report these issues in a private part of this issue tracker
27
# one of us (developers) will be put in charge of providing a patch
28
# the developer will publish the patch in our source code repository (that's the first publication)
29
# if relevant credits information has been sent to us, we will add this information to the code and the commit message to 
30
31
h2. Security flaws publication procedure
32
33
# we will then prepare (and publish below) a full report and the corresponding patch to secure your platform. We will also provide the patch in the form of a zip to unzip into your Chamilo directory for the latest stable version
34
# if you don't use the latest version, you will have to upgrade first *or* apply the patch by yourself in your version
35
# we will send an e-mail to security@lists.chamilo.org and through our @chamilosecurity Twitter account
36
# if the security flaw has been passed to a security reporting authority, we will send them an e-mail
37
38
h2. Reported flaws
39
40 57 Yannick Warnier
h3. Issue '#25' - 2018-05-31 - Moderate risk - Data leak
41
42
A flaw in the logic of the "Who is online" page made it possible for unauthenticated users to get a list of names and pictures of the users currently online on the Chamilo portal. We consider it a moderate risk as it is available to the public but only through using specific URLs not directly visible to the public, and because it only makes names and pictures available (no other private information) and only for users connected now or in the past few minutes.
43
44
This affects versions 1.11 of Chamilo and possibly previous versions.
45
46
This was kindly mentioned by Jurjen de Jonge of HVA.nl on 23/5/2018 but only received by us (due to e-mail issues on our side) on the 31/5/2018. A fix was provided a few hours after finally receiving the report. The fix removes the information if the option "see connected users from the portal homepage" has been disabled. By default, this option is enabled in Chamilo, so for security reasons, we recommend admins to disable it when installing their portal.
47
48
* For 1.11.x
49
** https://github.com/chamilo/chamilo-lms/commit/d400657bfa7ca08ca7a26abb73f607244cc48e73
50
51
No fix was provided for 1.10.x at this point as we consider this security issue a moderate risk.
52
53
These security patches will be made available as part of Chamilo 1.11.8 and superior.
54
55 56 Yannick Warnier
h3. Issue '#24' - 2018-04-09 - Low risk - Data leak
56
57
A flaw in the logic of the assignments tool in Chamilo made it possible for *registered users* to access the assignments provided by all other users in the same course.
58
59
This affects versions 1.11 of Chamilo (and probably previous versions), *but* you need a user account, to have access to a course and that the assignments tool be enabled in order to abuse this flaw. If all these conditions are combined, you could effectively download assignments from all other students even if you configured that assignments are not shared.
60
61
This was kindly reported by Jan Derriks of HVA.nl on the 9/4/2018. A fix for 1.11 was provided 40 minutes later. 
62
63
* For 1.11.x
64
** https://github.com/chamilo/chamilo-lms/commit/00f3e4a6506035674a58ccdf4ebe098bd6f607e3
65
66
No fix was provided for 1.10.x at this point as we consider this security issue a low risk.
67
68
These security patches will be made available as part of Chamilo 1.11.8 and superior.
69
70 55 Yannick Warnier
h3. Issue '#23' - 2017-02-09 - Moderate risk - PHP File Upload
71
72
A flaw in the elfinder extension to CKeditor in Chamilo was reported to us by Sandro "guly" Zaccarini.
73
74
This affects versions 1.10 and 1.11 of Chamilo, *but* you need a user account, that the social network be enabled *and* a special script to hack the upload method. This is why, although a PHP file upload issue would usually be marked as "High" or "Very high" risk, this has been lowered to "Moderate" risk.
75
76
We have made patches available to development versions of both 1.10 and 1.11:
77
78
* For 1.10.x
79
** https://github.com/chamilo/chamilo-lms/commit/501d19fed7773c7f5749cfa8d97cc8c7441fc7b1
80
* For 1.11.x
81
** https://github.com/chamilo/chamilo-lms/commit/337c3e6d254a2eae161f6e1405b8ab2fc01ef35f
82
** https://github.com/chamilo/chamilo-lms/commit/ac8a66b240bcf92a9e83ec2f4c7e829747269a00
83
84
These security patches will be made available as part of Chamilo 1.11.4.
85
86 53 Yannick Warnier
h3. Issue '#22' - 2016-12-26 - Moderate risk - PHPMailer shell escaping flaw
87
88 54 Julio Montoya
A flaw in the PHPMailer library, used in Chamilo LMS <=1.* was reported to us by Peter Bex of more-magic.net, and initially identified by Hanno Böck.
89 1 Yannick Warnier
90 54 Julio Montoya
Fixes for different versions of Chamilo are provided below, matching our max 72h response time policy: 
91
92
* For 1.9.x
93
** https://github.com/chamilo/chamilo-lms/commit/816a809da5446866fbb4b2101898027ec328e9b9
94
* For 1.10.x
95
**  https://github.com/chamilo/chamilo-lms/commit/ea335267dd96e6a3ea2bec53022c86115f55fe32
96
* For 1.11.x
97
** https://github.com/chamilo/chamilo-lms/commit/069845f08759cce4aa3693235e8d0a9a131ca35b
98
99 53 Yannick Warnier
100 50 Yannick Warnier
h3. Issue '#21' - 2016-07-15 - Moderate risk - User Input Sanitation 
101
102 51 Yannick Warnier
A series of user input data were reported as unsanitized in 1.10.6. This was reported by Echelon team (npo-echelon.ru) and  automatically detected by static code analyzer "AppChecker":https://cnpo.ru/en/solutions/appchecker.php. As far as we could check, these require course access and, as such, will not affect non-public courses. You either have to have an open-access platform or an open course inside your platform to be affected.
103 50 Yannick Warnier
104
Fixes for these vulnerabilities can be found here: https://github.com/chamilo/chamilo-lms/commit/52ef413e2719be2da521beb83a476d91468ef5e7
105
We have added additional filtering as well, available here: https://github.com/chamilo/chamilo-lms/commit/2a47c02329fb8dee04a6b6425c9ee7601c6f32e2
106
107
These fixes have been included in Chamilo 1.10.8 and all future versions.
108 49 Yannick Warnier
109
h3. Issue '#20' - 2016-02-15 - Moderate risk - (messageId) 
110
111
A rogue (not reported through official canals and include a public exploit) security issue was reported on 17/02/2016 by Lawrence Amer about being able to hijack another person's session through the handling of a crafted work in the assignments tool. This requires low-permissions access (student in a course) but could allow a student to hijack a teacher or admin's session.
112
113
Fixes for different versions of Chamilo are provided below, matching our max 72h response time policy:
114
* For 1.9.x
115
** https://github.com/chamilo/chamilo-lms/commit/d24f81b60e0a788a1dea4272ebe4a342f8874623
116
* For 1.10.x
117
** https://github.com/chamilo/chamilo-lms/commit/c3b9a10e7c9ad04e1cc3437848a99867cb5067ad
118
119 48 Yannick Warnier
h3. Issue '#19' - 2016-02-15 - Moderate risk - (messageId) Delete Post Vulnerability
120
121
A rogue (not reported through official canals and include a public procedure on how to exploit) security issue was reported on 15/02/2016 by Lawrence Amer about accessing other people's messages in the Chamilo social network, and giving the ability to delete the others' messages. Given the fact that messages are also sent by e-mail, we do not consider the deletion of other people's messages a high risk. However, accessing the messages themselves can be considered a high private information access vulnerability.
122
123
Fixes for different versions of Chamilo are provided below, matching our max 72h response time policy:
124
* For 1.9.x
125
** https://github.com/chamilo/chamilo-lms/commit/9b9de176d3651f5a9a59fd3ae0bf63a098392027
126
* For 1.10.x
127
** https://github.com/chamilo/chamilo-lms/commit/e45079df7a1bf31bbcdd9b1d22d8c23cf76fd1db
128
129 46 Yannick Warnier
h3. Issue '#18' - 2015-05-02 - Low-Moderate risk - URL hijacking/spoofing
130
131
A URL spoofing vulnerability has been reported by Luis Eduardo Jácome V. in Chamilo LMS 1.9.10.2 and all previous versions, allowing malintentionned crackers to modify an URL like:
132
* http://chamilo.org/main/link/link_goto.php?[...]&link_url=[original-redirect-url]
133
to
134
* http://chamilo.org/main/link/link_goto.php?[...]&link_url=[malign-redirect-url]
135
136
Because the change is clearly visible in the URL, we don't consider this vulnerability to represent a high risk to the user, but we still consider this a valid vulnerability, which is why we have provided the following fix, that you can freely apply to your 1.9.* installation. These changes will effectively ignore the link_url parameter and only take into account the link_id which is stored in the database, making it impossible to hack through the same channel. Very complicated circumstances prevented us from publishing the fix on this page in a timely manner, but the commits were sent several days ago already.
137
138
https://github.com/chamilo/chamilo-lms/commit/aa052c08b9f4bbde686572c66dc0301ac7a480b8
139
https://github.com/chamilo/chamilo-lms/commit/23f2e7520be2c0c9e77e58d508023f39afb82f6c
140
https://github.com/chamilo/chamilo-lms/commit/aeac10a06115a810bd630f04d55f452c51be35d5
141
https://github.com/chamilo/chamilo-lms/commit/84bba539d632957447832a01cf2e2c4035ed6dbf
142
143
Or, in more details:
144
<pre>
145
diff --git a/main/inc/lib/link.lib.php b/main/inc/lib/link.lib.php
146
index 875f048..eb3b156 100755
147
--- a/main/inc/lib/link.lib.php
148
+++ b/main/inc/lib/link.lib.php
149
@@ -103,6 +103,28 @@ class Link extends Model
150
151
         return false;
152
     }
153
+    
154
+    /**
155
+    *
156
+    * Get link info
157
+    * @param int link id
158
+    * @return array link info
159
+    *
160
+    **/
161
+    public static function get_link_info($id)
162
+    {
163
+        $tbl_link = Database:: get_course_table(TABLE_LINK);
164
+        $course_id = api_get_course_int_id();
165
+        $sql = "SELECT * FROM " . $tbl_link . "
166
+                WHERE c_id = $course_id AND id='" . intval($id) . "' ";
167
+        $result = Database::query($sql);
168
+        $data = array();
169
+        if (Database::num_rows($result)) {
170
+            $data = Database::fetch_array($result);
171
+        }
172
+        
173
+        return $data;
174
+    }
175
 }
176
177
 /**
178
diff --git a/main/link/link_goto.php b/main/link/link_goto.php
179
index 75163bb..101967f 100755
180
--- a/main/link/link_goto.php
181
+++ b/main/link/link_goto.php
182
@@ -21,16 +21,20 @@
183
 require_once '../inc/global.inc.php';
184
 $this_section = SECTION_COURSES;
185
186
-$link_url = html_entity_decode(Security::remove_XSS($_GET['link_url']));
187
-$link_id = intval($_GET['link_id']);
188
+require_once api_get_path(LIBRARY_PATH).'link.lib.php';
189
190
+$this_section = SECTION_COURSES;
191
+
192
+$linkId = intval($_GET['link_id']);
193
+
194
+$linkInfo = Link::get_link_info($linkId);
195
+$linkUrl = html_entity_decode(Security::remove_XSS($linkInfo['url']));
196
 // Launch event
197
-event_link($link_id);
198
+event_link($linkId);
199
200
 header("Cache-Control: no-store, no-cache, must-revalidate");   // HTTP/1.1
201
 header("Cache-Control: post-check=0, pre-check=0", false);
202
 header("Pragma: no-cache");                                     // HTTP/1.0
203
-header("Location: $link_url");
204
-
205
-// To be sure that the script stops running after the redirection
206
+header("Location: $linkUrl");
207
 exit;
208
</pre>
209
210
The fix has already been applied in prevision of version 1.10.0 and future versions.
211
212 44 Yannick Warnier
h3. Issue '#17' - 2015-03-19 - Moderate risk - XSS & CSRF vulnerabilies
213
214
A series of XSS and CSRF vulnerabilities were reported on the 2/3/2015 by Rehan Ahmed. After careful consideration and a fruitful exchange, we released different patches (find them individually in the Chamilo changelog for 1.9.10.2) that cover these vulnerabilities.
215
216 45 Yannick Warnier
In the official report, the author mentions the patch release to be 1.9.11. However, our bugfix releases policy enforces the use of the 1.9.10.2 number for this release. As of this writing, 1.9.11 does not (and will not) exist, it is a misnaming of 1.9.10.2.
217
218 44 Yannick Warnier
This is considered a moderate risk because most of these require to be an authenticated user in order to exploit them. On privately-managed portals, this is usually not an issue, but on open campuses, it is.
219
220
Initial report: received by e-mail on 2/3/2015
221
Proper report: #7564
222
Fix: The fix is to upgrade to Chamilo LMS 1.9.10.2, released today. The changelog contains the individual commits required to fix the vulnerabilities manually.
223
Affected versions: These vulnerabilities are likely to affect all previous versions of Chamilo LMS 
224
225
If you are using *any* 1.9.x version of Chamilo, 1.9.10.2 is a minor version, so upgrading is *only* a matter of overwriting the current Chamilo code (removing the home/ directory in the *new* version package is recommended before you overwrite, in case you have a customized homepage).
226
227
If you require assistance applying those fixes, Chamilo Official Providers are trained to help you out in a professional manner.
228
229 40 Yannick Warnier
h3. Issue '#16' - 2015-01-25 - High risk - SQL injection vulnerability in several queries
230
231
A series of security issues have been reported on the 9/12/2014 by Kacper Szurek. Because these vulnerabilities potentially affected numerous parts of the code, we took some time to finish a complete review of Chamilo and decided to publish the fix as part of Chamilo LMS 1.9.10.
232
233
This is considered high-risk because we could not measure precisely the impact it might have had, but we urge all our users to upgrade to Chamilo LMS 1.9.10 as soon as possible to avoid any problematic incidence.
234
235
Initial report: received by e-mail on 9/12/2014
236
Proper report: #7440
237
Fix: The fix is to upgrade to Chamilo LMS 1.9.10, released today. A standalone patch cannot be easily provided because it is too likely to break other parts of the code.
238
Affected versions: These vulnerabilities are likely to affect all previous versions of Chamilo LMS
239
240
If you are using *any* 1.9.x version of Chamilo, 1.9.10 is a minor version, so upgrading is *only* a matter of overwriting the current Chamilo code (removing the home/ directory in the *new* version package is recommended before you overwrite, in case you have a customized homepage).
241
242 42 Yannick Warnier
If you would like to apply a patch manually (and although we *don't* have a complete and secure patch at the moment), you can use the 3 main changes that were applied to fix it. This might not be an exhaustive list and, as always, Chamilo or BeezNest are not responsible for what might happen to your platform (see the GNU/GPLv3 license for details):
243
* https://github.com/chamilo/chamilo-lms/commit/3463b0465f60e07ae03d41c6bd9fd8a8d030de4d
244
* https://github.com/chamilo/chamilo-lms/commit/e01f044d58a7698b44fdda3a73c83eb8181a4910
245
* https://github.com/chamilo/chamilo-lms/commit/28baec78d282baec9aaa2c85f4736921375c3f6a
246
247 37 Yannick Warnier
h3. Issue '#15' - 2014-08-25 - Moderate-high risk - SQL injection in mySpace/users.php
248
249
A security issue has been reported by NeoSys on our forum, which allows a person with access to a course's users tool to pass a specially-crafted "status" parameter to get more results than expected, and potentially access (and modify) other parts of the database.
250
251 38 Yannick Warnier
This is considered moderate-high because it is limited to users having access to it, but because it as possibly high impact.
252 37 Yannick Warnier
253
Initial report: http://www.chamilo.org/phpBB3/viewtopic.php?f=15&t=5443&p=23969#p23969
254
Proper report: #7242
255 1 Yannick Warnier
Fix: (very easy one-liner) https://github.com/chamilo/chamilo-lms/commit/8a75f654066e4ff74567e5b427230117667325d1
256 38 Yannick Warnier
Affected versions: this doesn't *seem* to affect versions of Chamilo LMS previous to 1.9.8.0, as this code was introduced recently, but please make sure you check your own installation to avoid any uncomfortable situation.
257 37 Yannick Warnier
This patch will be included in release 1.9.8.3.
258
259
h3. Issue '#14' - 2014-06-18 - Moderate risk - XSS vulnerability in online editor
260 1 Yannick Warnier
261 39 Yannick Warnier
A security issue has been published for FCKeditor very shortly after the release of Chamilo LMS 1.9.8. Considering we are including a vulnerable version of FCKeditor in our software, we cannot leave this issue unattended, and as such we are releasing Chamilo LMS 1.9.8.1, a patch version for 1.9.8, with just one file patched. See https://github.com/chamilo/chamilo-lms/commit/2b6686e620407ab8d4ceb8951de4ce978917fc93 for more details or if you want to apply the patch manually. This covers CVE-2014-4037.
262 36 Yannick Warnier
263
Considering the relatively short period of time between the release of 1.9.8 and 1.9.8.1, we will still release 1.9.8.1 under the "commercial" name of 1.9.8, and will *link* all previous 1.9.8 links to the new 1.9.8.1 package. The changelog has been updated.
264
Considering you will be updating to 1.9.8.1 anyway, you'll notice that we've added a few (around 5) minor (mostly visual) issues that we caught just after the release of 1.9.8. So you kill 2 birds with one stone.
265
266
As always, being a minor version, you can just overwrite your previous installation with the files from this new package.
267
268 35 Yannick Warnier
h3. Issue '#13' - 2014-05-06 - Moderate risk - XSS vulnerability in user profile fields
269
270
Javier Bloem, independent white hat hacker from Venezuela, reported multiple possible attack vectors in description fields of Chamilo. Although these attacks require at minimum an access as a registered user to the portal, they do represent a vulnerability for those portals that are accepting open registration.
271
272
Patches have been commited to Github as commits:
273
* https://github.com/chamilo/chamilo-lms/commit/94706d7f99f7cb563c2a4f201c016caf7589fce1
274
* https://github.com/chamilo/chamilo-lms/commit/dd9bcd64fee588637914eec529cb489a8e89f2df
275
* https://github.com/chamilo/chamilo-lms/commit/a22589a9b909b32c89fe532d07b621d84b77fb34
276
277
Please update your portal(s) if you are in this case.
278
The fix is available in Chamilo 1.9.8 starting from Beta 1.
279
280 32 Yannick Warnier
h3. Issue '#12' - 2014-03-05 - High risk - File injection through FCKEditor
281
282 33 Noa Orizales Iglesias
Eric Marguin, from agence-codecouleurs.fr, reported an attack related to flaw #11, confirming it at the same time, whereby a skilled attacker injected a php file through an unprotected entry point in our implementation of FCKEditor.
283 32 Yannick Warnier
284
Affected versions: 1.8.*, 1.9.*
285
286 34 Julio Montoya
To fix, please update files:
287
288
<pre>
289
main/inc/lib/fckeditor/editor/plugins/ImageManager/config.inc.php 
290
main/inc/lib/fckeditor/editor/plugins/MP3/fck_mp3.php
291
</pre>
292
293
by adding the following line after the global.inc.php call.
294
295 32 Yannick Warnier
<pre>
296
api_block_anonymous_users();
297
</pre>
298
299
Note that this issue, together with issue #11, are fixed from 1.9.8 onwards.
300
301
h3. Issue '#11' - 2013-12-09 - High risk - File injection through FCKEditor - CONFIRMED
302 30 Yannick Warnier
303
Stijn Michels, one of Chamilo LMS users, reportes in #6860, that he has been attacked through a likely flaw in one of FCKEditor's plugins used in Chamilo LMS, through the fact that it is not checking identification from the user before uploading a file. The attack could not be reproduced. However, we think that preventive correction is important, and we have worked together to publish a patch that can be applied to any 1.8 or 1.9 version of Chamilo.
304
305
Affected versions: 1.8.*, 1.9.*
306
307
To fix, please update your main/inc/lib/fckeditor/editor/plugins/ajaxfilemanager/inc/config.php file adding the following on line 19:
308
<pre>
309
api_block_anonymous_users();
310
</pre>
311
and main/inc/lib/fckeditor/editor/filemanager/connectors/php/config.php to add 
312
<pre>
313
// Disabling access for anonymous users.
314
api_block_anonymous_users();
315
</pre>
316
317 52 Yannick Warnier
h3. Issue '#10' - 2013-11-06 - Moderate risk - SQL Injection in specific:
318
319
(unrecommended case to add the following on lines 33 and 34)
320 25 Yannick Warnier
321
High-Tech Bridge reported an SQL-injection-type security flaw in version 1.9.6 of Chamilo LMS (which also affects previous versions).
322
This flaw *only affect* Chamilo LMS platforms which use non-encrypted passwords mode (a mode that is available as a non-default option only during Chamilo LMS's installation process and is difficult to change afterwards).
323
If non-encrypted mode is selected (voluntarily) *and* malicious users have access to the profile edition form (which requires an active registered user account on the platform), then this issue represents a very high risk for you!
324
We believe and hope that most of our platform administrators have chosen the default recommended encrypted mode on their platform, but it is important to us to cover all risks. This is why we will be issuing a fix very shortly.
325
326
As a very quick fix, you can just open main/auth/profile.php, go to line 366 (function check_user_password()) and transform the following line:
327
<pre>
328
$password = api_get_encrypted_password($password);
329
</pre>
330
into this:
331
<pre>
332
$password = Database::escape_string(api_get_encrypted_password($password));
333
</pre>
334 1 Yannick Warnier
335 26 Yannick Warnier
This vulnerability has been assigned CVE-2013-6787.
336
337
See https://www.htbridge.com/advisory/HTB23182 for the original official report.
338 25 Yannick Warnier
339 24 Yannick Warnier
h3. Issue '#9' - 2013-08-10 - Low risk - XSS in course title
340
341
Javier Bloem from Venezuela reported (through the Venezuela local group) one XSS flaw, involving the edition of a course title. This was fixed in commit https://github.com/chamilo/chamilo-lms/commit/3c770c201dbe1ce96480a3e51ff25d0b70c83514 (you can update a 1.9.* install just by using the file at https://raw.github.com/chamilo/chamilo-lms/3c770c201dbe1ce96480a3e51ff25d0b70c83514/main/course_info/infocours.php ).
342
This flaw is considered "low risk" because it is an XSS (so stealing sessions is the kind of risk you get) *and* it is only accessible if you have the permission to create and edit courses, which you only get if you're a teacher.
343
It is, however, duly considered as flaw, as the default Chamilo installation *does* allow anybody to create a new teacher user, so it does represent a security risk for all people NOT READING the many recommendations on disabling this possibility as soon as they enter production.
344
345
Download the main/course_info/infocours.php script and replace it in your 1.9 installation from here: https://raw.github.com/chamilo/chamilo-lms/3c770c201dbe1ce96480a3e51ff25d0b70c83514/main/course_info/infocours.php 
346
347 17 Yannick Warnier
h3. Issue '#8' - 2013-03-04 - Moderate risk - Several moderate security flaws
348
349 19 Yannick Warnier
Fernando Muñoz, via Secunia SVCRP., kindly reported 3 flaws through Secunia, affecting at least version 1.9.4 (and most probably all previous versions) of Chamilo LMS.
350 17 Yannick Warnier
351
In order to ensure maximum responsivity of our Chamilo administrators around the world, we provide 2 fix mechanisms that we give here by order of increasing level of required skills. We should be publishing 1.9.6 soon, which will include this fix. The patches below are provided for version 1.9.4. You can find the details of the changes here: http://code.google.com/p/chamilo/source/detail?r=c9e8a27f8cde1f04dbe69d3f52a2e34c422bd679&name=1.9.x&repo=classic
352
353 20 Julio Montoya
* Download and apply the files replacement provided here: http://support.chamilo.org/attachments/download/3997/chamilo-1.9.4-vuln-8.zip Put the file directly into the root directory of Chamilo and uncompress there.
354
* Apply the patch provided here: 
355
  For 1.9.4 http://support.chamilo.org/attachments/download/3999/chamilo-1.9.4-vuln-8.patch
356 21 Julio Montoya
  For 1.9.2 and 1.9.0 http://support.chamilo.org/attachments/download/4007/chamilo-1.9.2-vuln-8.patch
357 20 Julio Montoya
  For 1.8.8.6 http://support.chamilo.org/attachments/download/4008/chamilo-1.8.8.6-vuln-8.patch
358 22 Julio Montoya
  For 1.8.8.2 http://support.chamilo.org/attachments/download/4013/chamilo-1.8.8.2-vuln-8.patch
359 23 Julio Montoya
  For 1.8.7.1 http://support.chamilo.org/attachments/download/4014/chamilo-1.8.7.1-vuln-8.patch
360 17 Yannick Warnier
361 18 Yannick Warnier
If you require special assistance, please contact providers@chamilo.org to hire an expert, or ask for help on the forum: http://www.chamilo.org/forum
362
363 17 Yannick Warnier
h3. Issue '#7' - 2012-07-16 - Moderate risk - Several moderate security flaws
364 15 Yannick Warnier
365
Fernando Muñoz kindly reported a series of moderate security flaws in Chamilo 1.8.8.4 (most likely also affecting all previous versions), of two XSS risks and one unauthorized file deletion risk. This has been registered in private task #5202.
366 1 Yannick Warnier
367 15 Yannick Warnier
In order to ensure maximum responsivity of our Chamilo administrators around the world, we provide 3 fix mechanisms that we give here by order of increasing level of required skills:
368
369 20 Julio Montoya
* Download and apply the files replacement provided here: http://support.chamilo.org/attachments/download/2864/patch-1.8.8.6.tgz Put the file directly into the root directory of Chamilo and uncompress there.
370 16 Yannick Warnier
* Download version 1.8.8.6 and follow the normal upgrade procedure: http://code.google.com/p/chamilo/downloads/detail?name=chamilo-1.8.8.6.tar.gz&can=2&q=
371 15 Yannick Warnier
* Apply the patch provided here: http://support.chamilo.org/attachments/download/2863/chamilo-1.8.8.4-to-1.8.8.6.patch
372
373 14 Yannick Warnier
We considered the report was sufficiently serious for us to publish a new minor version of the software. Please apply using one of the three methods above AS SOON AS POSSIBLE.
374 1 Yannick Warnier
375 14 Yannick Warnier
376 17 Yannick Warnier
h3. Issue '#6" - 2011-06-15 - High risk - Several security flaws
377 14 Yannick Warnier
378
Petr Skoda (<security _at_ skodak _dot_ org>) recently reported a series of flaws in Chamilo 1.8.8.2, which have been duly reported here http://support.chamilo.org/issues/3600 and here http://support.chamilo.org/issues/3601 and fixed in prevision for a special corrective 1.8.8.4 release within a few days (probably on the 18th of June). This release will come together with a series of improvements to the code and no upgrade procedure needed.
379
Patches are already available here:
380
381 13 Julio Montoya
* http://code.google.com/p/chamilo/source/detail?r=9ab36506b7099d29c005f4d4860a600e6734c166&repo=classic
382
* http://code.google.com/p/chamilo/source/detail?r=2b9e225f1659d253a8e458dabea5b71e4b57ac9b&repo=classic
383
* http://code.google.com/p/chamilo/source/detail?r=eef0cf45ceb4da084b3c61651fefae61d4e49fe2&repo=classic
384 1 Yannick Warnier
* http://code.google.com/p/chamilo/source/detail?r=7ccba74a526d52c7831781e05ed52311439cf922&repo=classic
385 13 Julio Montoya
386
387 17 Yannick Warnier
h3. Issue '#5' - 2011-01-31 - High risk - Filesystem traversal flaw
388 13 Julio Montoya
389
Fernando Muñoz kindly reported a major security flaw in the document system, by which a user could gain access to the database on lightly-hearted configured servers. 
390
* To fix it, please replace the changes found at 
391
http://code.google.com/p/chamilo/source/browse/main/document/download.php?spec=svn.classic.3c071b2b6555552651a9617b1c92a9a983da875f&repo=classic&r=3c071b2b6555552651a9617b1c92a9a983da875f
392
and
393
http://code.google.com/p/chamilo/source/detail?r=f2254d813f3a44a0a1b1717876b3c81df72a6879&repo=classic
394
395
* To discuss, please connect to http://support.chamilo.org/issues/2722
396
397 1 Yannick Warnier
This flaw is being reported to our Twitter security account and to our mailing-list security@lists.chamilo.org
398 13 Julio Montoya
The fix will be included in Chamilo 1.8.8, to be released within 14 days, but we recommend applying the patch to any production system straight away.
399 11 Yannick Warnier
400
401 17 Yannick Warnier
h3. Issue '#4' - 2011-01-28 - High risk - Filesystem traversal flaw
402 11 Yannick Warnier
403
Fernando Muñoz kindly reported a major security flaw in the gradebook system, by which a user could gain access to the database on lightly-hearted configured servers. 
404
* To fix it, please apply the changes found at http://code.google.com/p/chamilo/source/detail?r=b81c9c8012fa414d246a973aafddbde305c6f6f7&repo=classic
405 1 Yannick Warnier
* To discuss, please connect to http://support.chamilo.org/issues/2705
406 11 Yannick Warnier
407
This flaw is being reported to our Twitter security account and to our mailing-list security@lists.chamilo.org
408 1 Yannick Warnier
The fix will be included in Chamilo 1.8.8, to be released within 14 days, but we recommend applying the patch to any production system straight away.
409 11 Yannick Warnier
410 17 Yannick Warnier
h3. Issue '#3' - 2010-12-09 - Low risk - Wiki and core weaknesses in specific configurations
411 11 Yannick Warnier
412
develop-it.be kindly scanned Chamilo 1.8.8 development version and found several minor issues, which we have fixed and included in 1.8.8 (to be released February 2011)
413 8 Yannick Warnier
414 17 Yannick Warnier
h3. Issue '#2' - 2010-09-29 - High risk - Course directory removal risk through tasks tool
415 4 Yannick Warnier
416 1 Yannick Warnier
At around 11:55, Belgian time, on 29/09/2010, a new security issue has been reported by user mdube "on the Chamilo forum":http://www.chamilo.org/en/node/827.
417
418 5 Yannick Warnier
* Risk level: high
419 1 Yannick Warnier
* Versions affected: *1.8.6.2, 1.8.7, 1.8.7.1*
420 4 Yannick Warnier
* Triggered by: teachers and administrators (no anonymous/student access)
421 1 Yannick Warnier
* Patch: "See patch":http://code.google.com/p/chamilo/source/detail?r=9cd63d72154d7c0ac0d7fb9858bc37e83c0ec44d&repo=classic
422
423
This security issue's risk level is considered *high* (on a scale of critical, high, moderate and low) in the sense you require edition permissions in the course to provoke it (relatively safe)  but it provokes highly painful damages: it deletes a course directory, entirely.
424
425
This bug affects versions 1.8.6.2, 1.8.7 and 1.8.7.1.
426 4 Yannick Warnier
427 1 Yannick Warnier
At 21:00, Belgian time (less than 12 hours later), Julio Montoya, on behalf of BeezNest, "developed a patch":http://code.google.com/p/chamilo/source/detail?r=9cd63d72154d7c0ac0d7fb9858bc37e83c0ec44d&repo=classic that you can "download as a file":http://classic.chamilo.googlecode.com/hg/main/work/work.php?r=9cd63d72154d7c0ac0d7fb9858bc37e83c0ec44d and apply to your Chamilo 1.8.7.1 portal.
428 9 Yannick Warnier
429 10 Yannick Warnier
For previous versions of Chamilo, you will have to look at the patch and apply the differences manually. Suggestions are provided below:
430
* "replacement work.php for 1.8.6.2":/attachments/download/1111/work.php.1862
431 1 Yannick Warnier
* "replacement work.php for 1.8.7":/attachments/download/1112/work.php.187
432
433
The problem can be reproduced by trying to delete an un-existing student work from a course. The delete URL can be crafted manually, but it can  also be triggered by a double click on the delete icon for a student work.
434
This means that if you have teachers accidentally double-clicking on the delete icon, they can delete the entire course directory. The only solution then is to restore the course directory quickly from your daily backup.
435 4 Yannick Warnier
436 1 Yannick Warnier
This bug was introduced "in November of 2009":http://code.google.com/p/chamilo/source/detail?r=d7ccd47395fe823bc521c9faeecb68e44d93197d&repo=classic&path=/main/work/work.php, while still working on Dok€os, by a then member of the BeezNest team trying to fix a complex issue by using the permanently_remove_deleted_files parameter to decide whether to delete the files permanently or to leave them on disk. This flaw could apply to Dok€os 2.0 (cannot be checked until the code is made available). The developer doesn't work with us anymore, and we have considerably improved the review process, but this specific kind of bug implies a peer review process, and this can only come with regular investment.
437 4 Yannick Warnier
438 1 Yannick Warnier
Using the services of an "official Chamilo provider":http://www.chamilo.org/en/providers guarantees your contributions go to Chamilo and help many other organizations and people around the world, just as
439
you benefit from contributions from many others. Contribute to the Chamilo project using our official providers services and encourage our healthy and socially responsible economical model!
440 2 Yannick Warnier
441 3 Yannick Warnier
Best regards,
442 2 Yannick Warnier
443 3 Yannick Warnier
Yannick Warnier
444 1 Yannick Warnier
Lead developer for Chamilo 1.8
445 7 Yannick Warnier
446 17 Yannick Warnier
h3. Issue '#1' - 2010-08-02 - Wiki issues
447 7 Yannick Warnier
448
Fixed in 1.8.7.1 package.