BIRD through 2.0.7 does not provide functionality for password authentication of BGP peers. Because of this, products that use BIRD (which may, for example, include Tigera products in some configurations, as well as products of other vendors) may have been susceptible to route redirection for Denial of Service and/or Information Disclosure. NOTE: a researcher has asserted that the behavior is within Tigera’s area of responsibility; however, Tigera disagrees

2.15.1-alt1, sysvinit: unrecognized option: --expect-group

Уязвимость виртуальной обучающей среды Moodle, связанная с непринятием мер по защите структуры веб-страницы позволяющая нарушителю провести атаку межсайтового скриптинга (XSS)

Уязвимость виртуальной обучающей среды Moodle, связанная с непринятием мер по защите структуры веб-страницы позволяющая нарушителю провести атаку межсайтового скриптинга (XSS)

Уязвимость системы управления Moodle, связанная с недостаточной проверкой входных данных, позволяющая нарушителю выполнять произвольные команды

Уязвимость виртуальной обучающей среды Moodle, связанная с подделкой межсайтовых запросов, позволяющая нарушителю осуществить CSRF-атаку

Уязвимость виртуальной обучающей среды Moodle, связанная с использованием ключа после истечения срока его действия, позволяющая нарушителю получить несанкционированный доступ к защищаемой информации

Уязвимость виртуальной обучающей среды Moodle, связанная с предоставлением конфиденциальной информации неавторизованному лицу, позволяющая нарушителю получить несанкционированный доступ к защищаемой информации

Уязвимость виртуальной обучающей среды Moodle, связанная с неправильной нейтрализацией входных данных во время генерации веб-страницы, позволяющая нарушителю выполнять атаки межсайтового скриптинга

Moodle 4.3 allows /grade/report/grader/index.php?searchvalue= reflected XSS when logged in as a teacher. NOTE: the Moodle Security FAQ link states "Some forms of rich content [are] used by teachers to enhance their courses ... admins and teachers can post XSS-capable content, but students can not."

No data currently available.

No data currently available.

No data currently available.

No data currently available.

No data currently available.

No data currently available.

No data currently available.

No data currently available.

No data currently available.

No data currently available.

Insufficient file size checks resulted in a denial of service risk in the file picker's unzip functionality.

The URL parameters accepted by forum search were not limited to the allowed parameters.

Separate Groups mode restrictions were not honored in the H5P attempts report, which would display users from other groups. By default this only provided additional access to non-editing teachers.

Separate Groups mode restrictions were not honored when performing a forum export, which would export forum data for all groups. By default this only provided additional access to non-editing teachers.

The link to update all installed language packs did not include the necessary token to prevent a CSRF risk.

Insufficient checks in a web service made it possible to add comments to the comments block on another user's dashboard when it was not otherwise available (e.g., on their profile page).

Incorrect validation of allowed event types in a calendar web service made it possible for some users to create events with types/audiences they did not have permission to publish to.

Additional sanitizing was required when opening the equation editor to prevent a stored XSS risk when editing another user's equation.

Insufficient escaping of participants' names in the participants page table resulted in a stored XSS risk when interacting with some features.

The referrer URL used by MFA required additional sanitizing, rather than being used directly.

ID numbers displayed in the lesson overview report required additional sanitizing to prevent a stored XSS risk.

Actions in the admin preset tool did not include the necessary token to prevent a CSRF risk.

In a shared hosting environment that has been misconfigured to allow access to other users' content, a Moodle user with both access to restore feedback modules and direct access to the web server outside of the Moodle webroot could execute a local file include.

In a shared hosting environment that has been misconfigured to allow access to other users' content, a Moodle user with both access to restore workshop modules and direct access to the web server outside of the Moodle webroot could execute a local file include.

In a shared hosting environment that has been misconfigured to allow access to other users' content, a Moodle user with both access to restore wiki modules and direct access to the web server outside of the Moodle webroot could execute a local file include.

In a shared hosting environment that has been misconfigured to allow access to other users' content, a Moodle user with both access to restore database activity modules and direct access to the web server outside of the Moodle webroot could execute a local file include.

The site log report required additional encoding of event descriptions to ensure any HTML in the content is displayed in plaintext instead of being rendered.

The logout option within MFA did not include the necessary token to avoid the risk of users inadvertently being logged out via CSRF.

Actions in the admin management of analytics models did not include the necessary token to prevent a CSRF risk.

Insufficient checks whether ReCAPTCHA was enabled made it possible to bypass the checks on the login page. This did not affect other pages where ReCAPTCHA is utilized.

Insufficient capability checks meant it was possible for users to gain access to BigBlueButton join URLs they did not have permission to access.

Insufficient escaping of calendar event titles resulted in a stored XSS risk in the event deletion prompt.

The cURL wrapper in Moodle retained the original request headers when following redirects, so HTTP authorization header information could be unintentionally sent in requests to redirect URLs.

Incorrect CSRF token checks resulted in multiple CSRF risks.

A unique key should be generated for a user's QR login key and their auto-login key, so the same key cannot be used interchangeably between the two.

Moodle CSRF risks due to misuse of confirm_sesskey

Uncontrolled Resource Consumption in moodle

Moodle broken access control when setting calendar event type

Moodle CSRF risk in analytics management of models

Improper Handling of Parameters in moodle

Cross-Site Request Forgery in moodle

Moodle Logout CSRF in admin/tool/mfa/auth.php

Moodle Cross-site Scripting (XSS)

Moodle stored Cross-site Scripting (XSS)

Authorization Bypass in moodle

Improper Access Control in moodle

Moodle CSRF risk in admin preset tool management of presets

Moodle ReCAPTCHA can be bypassed on the login page

Improper Access Control in moodle

Moodle Authenticated LFI risk in some misconfigured shared hosting environments

Moodle Authenticated LFI risk in some misconfigured shared hosting environments

Moodle HTTP authorization header is preserved between "emulated redirects"

Moodle stored XSS via calendar's event title when deleting the event

Moodle Authenticated LFI risk in some misconfigured shared hosting environments

Moodle Improper Input Validation

Moodle uses the same key for QR login and auto-login

Moodle Authenticated LFI risk in some misconfigured shared hosting environments

Moodle Unsanitized HTML in site log for config_log_created

Moodle BigBlueButton web service leaks meeting joining information

Moodle Cross-site Scripting (XSS)