First published: Mon May 19 2014(Updated: )
Mahara before 1.5.12, 1.6.x before 1.6.7, and 1.7.x before 1.7.3 does not properly restrict access to artefacts, which allows remote authenticated users to read arbitrary artefacts via the (1) artefact id in an upload action when creating a journal or (2) instconf_artefactid_selected[ID] parameter in an upload action when editing a block.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
Mahara Mahara | <=1.5.11 | |
Mahara Mahara | =1.5-rc1 | |
Mahara Mahara | =1.5-rc2 | |
Mahara Mahara | =1.5.0 | |
Mahara Mahara | =1.5.1 | |
Mahara Mahara | =1.5.2 | |
Mahara Mahara | =1.5.3 | |
Mahara Mahara | =1.5.4 | |
Mahara Mahara | =1.5.6 | |
Mahara Mahara | =1.5.7 | |
Mahara Mahara | =1.5.8 | |
Mahara Mahara | =1.5.9 | |
Mahara Mahara | =1.5.10 | |
Mahara Mahara | =1.7.-rc1 | |
Mahara Mahara | =1.7.0 | |
Mahara Mahara | =1.7.1 | |
Mahara Mahara | =1.7.2 | |
Mahara Mahara | =1.6.0 | |
Mahara Mahara | =1.6.1 | |
Mahara Mahara | =1.6.2 | |
Mahara Mahara | =1.6.3 | |
Mahara Mahara | =1.6.4 | |
Mahara Mahara | =1.6.5 | |
Mahara Mahara | =1.6.6 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.