Sl1 vulnerabilities
27 known vulnerabilities in Sl1 from ScienceLogic. 27 are rated high or critical, and 1 has been exploited in real attacks. Each entry lists the affected versions and the release that fixes it, where the vendor has published one.
Latest first
- 7.2 High severity
SL1: Improper Neutralization of Special Elements used in an SQL Command
index.em7 in ScienceLogic SL1 before 12.1.1 allows SQL Injection via a parameter in a request. NOTE: this is disputed by the Supplier because it "inaccurately describes the vulnerability."
- 9.8 Critical severity
ScienceLogic SL1 Unspecified Exploited
ScienceLogic SL1 (formerly EM7) is affected by an unspecified vulnerability involving an unspecified third-party component packaged with SL1. The vulnerability is addressed in SL1 versions 12.1.3+, 12.2.3+, and 12.3+. Remediations have been made available for
- 8.8 High severity
SL 1: Improper Neutralization of Special Elements used in an SQL Command
A SQL injection vulnerability exists in the “logging export” feature of the ScienceLogic SL1 that takes unsanitized user‐controlled input and passes it directly to a SQL query. This allows for the injection of arbitrary SQL before being executed against the da
- 8.8 High severity
SL 1: Improper Neutralization of Special Elements used in an SQL Command
A SQL injection vulnerability exists in the “message viewer iframe” feature of the ScienceLogic SL1 that takes unsanitized user‐controlled input and passes it directly to a SQL query. This allows for the injection of arbitrary SQL before being executed against
- 8.8 High severity
SL 1: Improper Neutralization of Special Elements used in an SQL Command
A SQL injection vulnerability exists in the “message viewer print” feature of the ScienceLogic SL1 that takes unsanitized user‐controlled input and passes it directly to a SQL query. This allows for the injection of arbitrary SQL before being executed against
- 8.8 High severity
SL 1: Improper Neutralization of Special Elements used in an SQL Command
A SQL injection vulnerability exists in the “network print report” feature of the ScienceLogic SL1 that takes unsanitized user‐controlled input and passes it directly to a SQL query. This allows for the injection of arbitrary SQL before being executed against
- 8.8 High severity
SL 1: Improper Neutralization of Special Elements used in an SQL Command
A SQL injection vulnerability exists in the “notes view” feature of the ScienceLogic SL1 that takes unsanitized user‐controlled input and passes it directly to a SQL query. This allows for the injection of arbitrary SQL before being executed against the databa
- 8.8 High severity
SL 1: Improper Neutralization of Special Elements used in an SQL Command
A SQL injection vulnerability exists in the “reporter events type” feature of the ScienceLogic SL1 that takes unsanitized user‐controlled input and passes it directly to a SQL query. This allows for the injection of arbitrary SQL before being executed against
- 8.8 High severity
SL 1: Improper Neutralization of Special Elements used in an SQL Command
A SQL injection vulnerability exists in the “reporter events type date” feature of the ScienceLogic SL1 that takes unsanitized user‐controlled input and passes it directly to a SQL query. This allows for the injection of arbitrary SQL before being executed aga
- 8.8 High severity
SL 1: Improper Neutralization of Special Elements used in an SQL Command
A SQL injection vulnerability exists in the “ticket event report” feature of the ScienceLogic SL1 that takes unsanitized user‐controlled input and passes it directly to a SQL query. This allows for the injection of arbitrary SQL before being executed against t
- 8.8 High severity
SL 1: Improper Neutralization of Special Elements used in an SQL Command
A SQL injection vulnerability exists in the “ticket queue watchers” feature of the ScienceLogic SL1 that takes unsanitized user‐controlled input and passes it directly to a SQL query. This allows for the injection of arbitrary SQL before being executed against
- 8.8 High severity
SL 1: Improper Neutralization of Special Elements used in an SQL Command
A SQL injection vulnerability exists in the “ticket template watchers” feature of the ScienceLogic SL1 that takes unsanitized user‐controlled input and passes it directly to a SQL query. This allows for the injection of arbitrary SQL before being executed agai
- 8.8 High severity
SL 1: Improper Neutralization of Special Elements used in an SQL Command
A SQL injection vulnerability exists in the “ticket watchers email” feature of the ScienceLogic SL1 that takes unsanitized user‐controlled input and passes it directly to a SQL query. This allows for the injection of arbitrary SQL before being executed against
- 8.8 High severity
SL 1: Improper Neutralization of Special Elements used in an SQL Command
A SQL injection vulnerability exists in the “topology data service” feature of the ScienceLogic SL1 that takes unsanitized user‐controlled input and passes it directly to a SQL query. This allows for the injection of arbitrary SQL before being executed against
- 8.8 High severity
SL 1: Improper Neutralization of Special Elements used in an SQL Command
A SQL injection vulnerability exists in the vendor_country parameter of the “vendor print report” feature of the ScienceLogic SL1 that takes unsanitized user‐controlled input and passes it directly to a SQL query. This allows for the injection of arbitrary SQL
- 8.8 High severity
SL 1: Improper Neutralization of Special Elements used in an SQL Command
A SQL injection vulnerability exists in the vendor_state parameter of the “vendor print report” feature of the ScienceLogic SL1 that takes unsanitized user‐controlled input and passes it directly to a SQL query. This allows for the injection of arbitrary SQL b
- 8.8 High severity
SL 1: Improper Neutralization of Special Elements used in an SQL Command
A SQL injection vulnerability exists in the “admin dynamic app mib errors” feature of the ScienceLogic SL1 that takes unsanitized user‐controlled input and passes it directly to a SQL query. This allows for the injection of arbitrary SQL before being executed
- 8.8 High severity
SL 1: Improper Neutralization of Special Elements used in an SQL Command
A SQL injection vulnerability exists in the “reporting job editor” feature of the ScienceLogic SL1 that takes unsanitized user‐controlled input and passes it directly to a SQL query. This allows for the injection of arbitrary SQL before being executed against
- 8.8 High severity
SL 1: Improper Neutralization of Special Elements used in an SQL Command
A SQL injection vulnerability exists in the “schedule editor decoupled” feature of the ScienceLogic SL1 that takes unsanitized user‐controlled input and passes it directly to a SQL query. This allows for the injection of arbitrary SQL before being executed aga
- 8.8 High severity
SL 1: Improper Neutralization of Special Elements used in an SQL Command
A SQL injection vulnerability exists in the “schedule editor” feature of the ScienceLogic SL1 that takes unsanitized user‐controlled input and passes it directly to a SQL query. This allows for the injection of arbitrary SQL before being executed against the d
- 8.8 High severity
SL 1: Improper Neutralization of Special Elements used in an SQL Command
A SQL injection vulnerability exists in the “json walker” feature of the ScienceLogic SL1 that takes unsanitized user‐controlled input and passes it directly to a SQL query. This allows for the injection of arbitrary SQL before being executed against the datab
- 8.8 High severity
SL 1: Improper Neutralization of Special Elements used in an SQL Command
A SQL injection vulnerability exists in the “admin brand portal” feature of the ScienceLogic SL1 that takes unsanitized user‐controlled input and passes it directly to a SQL query. This allows for the injection of arbitrary SQL before being executed against th
- 8.8 High severity
SL 1: Improper Neutralization of Special Elements used in an OS Command
A command injection vulnerability exists in the download and convert report feature of the ScienceLogic SL1 that takes unsanitized user‐controlled input and passes it directly to a shell command. This allows for the injection of arbitrary commands to the under
- 8.8 High severity
SL 1: Improper Neutralization of Special Elements used in an OS Command
A command injection vulnerability exists in the dashboard scheduler feature of the ScienceLogic SL1 that takes unsanitized user‐controlled input and passes it directly to a shell command. This allows for the injection of arbitrary commands to the underlying op
- 8.8 High severity
SL 1: Improper Neutralization of Special Elements used in an OS Command
A command injection vulnerability exists in the ticket report generate feature of the ScienceLogic SL1 that takes unsanitized user controlled input and passes it directly to a shell command. This allows for the injection of arbitrary commands to the underlying
- 8.8 High severity
SL 1: Improper Neutralization of Special Elements used in an OS Command
A command injection vulnerability exists in the “dash export” feature of the ScienceLogic SL1 that takes unsanitized user controlled input and passes it directly to a shell command. This allows for the injection of arbitrary commands to the underlying operatin
- 8.8 High severity
SL 1: Improper Neutralization of Special Elements used in an OS Command
A command injection vulnerability exists in the ARP ping device tool feature of the ScienceLogic SL1 that takes unsanitized user controlled input and passes it directly to a shell command. This allows for the injection of arbitrary commands to the underlying o