Ryan Wincey

**Nome do software vulnerável e versões afetadas** Okta Verify para Windows, versões anteriores à 5.0.2 **Descrição** O problema diz respeito a uma vulnerabilidade de escalonamento de privilégios por meio de sequestro de DLL. A vulnerabilidade foi corrigida na versão 5.0.2. **Recomendações** Para versões anteriores à 5.0.2, atualize para a versão 5.0.2 ou superior para resolver o problema.

**Nome do software vulnerável e versões afetadas** Okta Verify para Windows (versões afetadas não especificadas) **Descrição** O problema está relacionado ao serviço de atualização automática do Okta Verify para Windows, que está vulnerável a duas falhas que podem ser combinadas para executar código arbitrário. Isso poderia permitir que um invasor remoto realizasse ações maliciosas. O número estimado de dispositivos potencialmente afetados em todo o mundo não foi especificado. Não há informações sobre incidentes reais em que essa vulnerabilidade tenha sido explorada. **Recomendações** No momento, não há informações sobre uma versão mais recente que contenha uma correção para essa vulnerabilidade.

**Name of the Vulnerable Software and Affected Versions** BMC PATROL Agent versions prior to 20.08.00 **Description** The issue allows local privilege escalation via vectors involving `pconfig` and the `+RESTART -host` options. **Recommendations** For versions prior to 20.08.00, update to version 20.08.00 or later to resolve the issue.

**Name of the Vulnerable Software and Affected Versions** ScienceLogic SL1 (affected versions not specified) **Description** A SQL injection issue exists in the “notes view” feature of the ScienceLogic SL1. This feature takes unsanitized user-controlled input and passes it directly to a SQL query, allowing for the injection of arbitrary SQL before being executed against the database. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** ScienceLogic SL1 (affected versions not specified) **Description** A SQL injection issue exists in the “topology data service” feature, where unsanitized user-controlled input is passed directly to a SQL query, allowing the injection of arbitrary SQL before execution against the database. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** ScienceLogic SL1 (affected versions not specified) **Description** A SQL injection issue exists in the “reporter events type” feature of the ScienceLogic SL1. This feature takes unsanitized user-controlled input and passes it directly to a SQL query, allowing for the injection of arbitrary SQL before being executed against the database. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** ScienceLogic SL1 (affected versions not specified) **Description** A SQL injection issue exists in the "ticket event report" feature, where unsanitized user-controlled input is passed directly to a SQL query, allowing the injection of arbitrary SQL before execution against the database. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** ScienceLogic SL1 (affected versions not specified) **Description** A SQL injection issue exists in the "ticket queue watchers" feature of the ScienceLogic SL1. This feature takes unsanitized user-controlled input and passes it directly to a SQL query, allowing for the injection of arbitrary SQL before being executed against the database. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** ScienceLogic SL1 (affected versions not specified) **Description** A SQL injection issue exists in the "ticket template watchers" feature, where unsanitized user-controlled input is passed directly to a SQL query, allowing the injection of arbitrary SQL before execution against the database. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** ScienceLogic SL1 (affected versions not specified) **Description** A command injection issue exists in the download and convert report feature, where unsanitized user-controlled input is passed directly to a shell command, allowing the injection of arbitrary commands to the underlying operating system. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** ScienceLogic SL1 (affected versions not specified) **Description** A SQL injection issue exists in the "admin dynamic app mib errors" feature, where unsanitized user-controlled input is passed directly to a SQL query, allowing the injection of arbitrary SQL that is then executed against the database. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** ScienceLogic SL1 (affected versions not specified) **Description** A SQL injection issue exists in the `vendor state` parameter of the "vendor print report" feature, allowing arbitrary SQL injection before execution against the database. This occurs because the feature takes unsanitized user-controlled input and passes it directly to a SQL query. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** ScienceLogic SL1 (affected versions not specified) **Description** A SQL injection issue exists in the “admin brand portal” feature of the ScienceLogic SL1. This feature takes unsanitized user-controlled input and passes it directly to a SQL query, allowing for the injection of arbitrary SQL before being executed against the database. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** ScienceLogic SL1 (affected versions not specified) **Description** A SQL injection issue exists in the `vendor country` parameter of the "vendor print report" feature. This feature takes unsanitized user-controlled input and passes it directly to a SQL query, allowing for the injection of arbitrary SQL before being executed against the database. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** ScienceLogic SL1 (affected versions not specified) **Description** A SQL injection issue exists in the "schedule editor" feature of the ScienceLogic SL1. This feature takes unsanitized user-controlled input and passes it directly to a SQL query, allowing for the injection of arbitrary SQL before being executed against the database. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** ScienceLogic SL1 (affected versions not specified) **Description** A SQL injection issue exists in the "ticket watchers email" feature, where unsanitized user-controlled input is passed directly to a SQL query, allowing the injection of arbitrary SQL before execution against the database. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** ScienceLogic SL1 (affected versions not specified) **Description** A SQL injection issue exists in the “reporting job editor” feature of the ScienceLogic SL1. This feature takes unsanitized user-controlled input and passes it directly to a SQL query, allowing for the injection of arbitrary SQL before being executed against the database. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** ScienceLogic SL1 (affected versions not specified) **Description** A SQL injection issue exists in the "schedule editor decoupled" feature, where unsanitized user-controlled input is passed directly to a SQL query, allowing the injection of arbitrary SQL that is then executed against the database. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** ScienceLogic SL1 (affected versions not specified) **Description** A SQL injection issue exists in the "json walker" feature, where unsanitized user-controlled input is passed directly to a SQL query, allowing the injection of arbitrary SQL that is then executed against the database. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** ScienceLogic SL1 (affected versions not specified) **Description** A SQL injection issue exists in the “reporter events type date” feature of the ScienceLogic SL1. This feature takes unsanitized user-controlled input and passes it directly to a SQL query, allowing for the injection of arbitrary SQL before being executed against the database. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.