Bug 1692904 (CVE-2019-3848) - CVE-2019-3848 moodle: Logged in users could view all calendar events
Summary: CVE-2019-3848 moodle: Logged in users could view all calendar events
Keywords:
Status: CLOSED UPSTREAM
Alias: CVE-2019-3848
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1692905 1692906
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-26 16:37 UTC by Laura Pardo
Modified: 2022-10-02 21:48 UTC (History)
3 users (show)

Fixed In Version: moodle 3.6.3, moodle 3.5.5, moodle 3.4.8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-10 10:52:05 UTC
Embargoed:


Attachments (Terms of Use)

Description Laura Pardo 2019-03-26 16:37:47 UTC
A vulnerability was found in moodle before versions 3.6.3, 3.5.5 and 3.4.8. Permissions were not correctly checked before loading event information into the calendar's edit event modal popup, so logged in non-guest users could view unauthorised calendar events. (Note: It was read-only access, users could not edit the events.)


Upstream Bug:
https://tracker.moodle.org/browse/MDL-64830

Upstream Patch:
http://git.moodle.org/gw?p=moodle.git&a=search&h=HEAD&st=commit&s=MDL-64830

Comment 1 Laura Pardo 2019-03-26 16:37:50 UTC
Acknowledgments:

Name: Juan Leyva

Comment 2 Laura Pardo 2019-03-26 16:37:52 UTC
External References:

https://moodle.org/mod/forum/discuss.php?d=384011#p1547743

Comment 3 Laura Pardo 2019-03-26 16:38:22 UTC
Created moodle tracking bugs for this issue:

Affects: epel-all [bug 1692906]
Affects: fedora-all [bug 1692905]

Comment 4 Product Security DevOps Team 2019-06-10 10:52:05 UTC
This CVE Bugzilla entry is for community support informational purposes only as it does not affect a package in a commercially supported Red Hat product. Refer to the dependent bugs for status of those individual community products.


Note You need to log in before you can comment on or make changes to this bug.