SQL Injection in Znuny Ticket Search Allowing Data Theft
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Znuny | Znuny | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Znuny | Znuny |
|
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.300% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Title | SQL Injection in Znuny Ticket Search Allowing Data Theft |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Znuny through 7.3.6 constructs a ticket-search database query by directly concatenating user-supplied input into the SQL statement. This lack of proper sanitization or the use of parameterized queries allows an attacker to inject arbitrary SQL commands, leading to data theft, modification, or denial of service. Specifically this is in Kernel::System::Ticket::TicketSearch and Kernel::System::Ticket::ArticleSearchIndex::DB via the ContentSearch parameter. The parameter is expected to be either "AND" or "OR", but its value was concatenated directly into the generated SQL query without validation. | |
| First Time appeared |
Znuny
Znuny znuny |
|
| Weaknesses | CWE-89 | |
| CPEs | cpe:2.3:a:znuny:znuny:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Znuny
Znuny znuny |
|
| References |
| |
| Metrics |
cvssV4_0
|