B0Yd

The issue allows local privilege escalation via vectors involving `pconfig` and the `+RESTART -host` options.

A SQL injection issue exists in the “logging export” feature, where unsanitized user-controlled input is passed directly to a SQL query, allowing the injection of arbitrary SQL before execution against the database.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

A SQL injection issue exists in the “network print 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.

A SQL injection issue exists in the "message viewer print" feature, where unsanitized user-controlled input is passed directly to a SQL query, allowing the injection of arbitrary SQL before execution against the database.

A SQL injection issue exists in the “message viewer iframe” feature, where unsanitized user-controlled input is passed directly to a SQL query, allowing the injection of arbitrary SQL before execution against the database.

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.

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.

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.

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.