Most recent entries from all https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 11 Oct 2026 08:12:53 +0000 cnvd-2017-35384 https://vulnerability.circl.lu/vuln/cnvd-2017-35384 cnvd-2017-35384 https://vulnerability.circl.lu/vuln/cnvd-2017-35384 fkie_cve-2017-1000221 https://vulnerability.circl.lu/vuln/fkie_cve-2017-1000221 <p>In Opencast 2.2.3 and older if user names overlap, the Opencast search service used for publication to the media modules and players will handle the access control incorrectly so that users only need to match part of the user name used for the access restriction. For example, a user with the role ROLE_USER will have access to recordings published only for ROLE_USER_X.</p> <p>In Opencast 2.2.3 and older if user names overlap, the Opencast search service used for publication to the media modules and players will handle the access control incorrectly so that users only need to match part of the user name used for the access restriction. For example, a user with the role ROLE_USER will have access to recordings published only for ROLE_USER_X.</p> https://vulnerability.circl.lu/vuln/fkie_cve-2017-1000221 GHSA-hx44-c87v-p6xg — Opencast has Incorrect Permission Assignment https://vulnerability.circl.lu/vuln/ghsa-hx44-c87v-p6xg <p><strong>Affected:</strong> Maven: org.opencastproject:opencast-kernel</p> <p>In Opencast 2.2.3 and older if user names overlap, the Opencast search service used for publication to the media modules and players will handle the access control incorrectly so that users only need to match part of the user name used for the access restriction. For example, a user with the role ROLE_USER will have access to recordings published only for ROLE_USER_X.</p> <p><strong>Affected:</strong> Maven: org.opencastproject:opencast-kernel</p> <p>In Opencast 2.2.3 and older if user names overlap, the Opencast search service used for publication to the media modules and players will handle the access control incorrectly so that users only need to match part of the user name used for the access restriction. For example, a user with the role ROLE_USER will have access to recordings published only for ROLE_USER_X.</p> https://vulnerability.circl.lu/vuln/ghsa-hx44-c87v-p6xg gsd-2017-1000221 https://vulnerability.circl.lu/vuln/gsd-2017-1000221 gsd-2017-1000221 https://vulnerability.circl.lu/vuln/gsd-2017-1000221