Spiceworks Help Desk Server up to 1.3.2 database_query.rb order_by_for_ticket sort deserialization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.2 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Spiceworks Help Desk Server up to 1.3.2. Affected by this vulnerability is the function order_by_for_ticket of the file app/models/reporting/database_query.rb. Performing a manipulation of the argument sort results in deserialization.
This vulnerability is reported as CVE-2021-43609. The attack is possible to be carried out remotely. No exploit exists.
You should upgrade the affected component.
Details
A vulnerability classified as critical has been found in Spiceworks Help Desk Server up to 1.3.2. This affects the function order_by_for_ticket of the file app/models/reporting/database_query.rb. The manipulation of the argument sort with an unknown input leads to a deserialization vulnerability. CWE is classifying the issue as CWE-502. The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
An issue was discovered in Spiceworks Help Desk Server before 1.3.3. A Blind Boolean SQL injection vulnerability within the order_by_for_ticket function in app/models/reporting/database_query.rb allows an authenticated attacker to execute arbitrary SQL commands via the sort parameter. This can be leveraged to leak local files from the host system, leading to remote code execution (RCE) through deserialization of malicious data.
The weakness was disclosed 11/09/2023. It is possible to read the advisory at community.spiceworks.com. This vulnerability is uniquely identified as CVE-2021-43609 since 11/12/2021. Technical details of the vulnerability are known, but there is no available exploit.
Upgrading to version 1.3.3 eliminates this vulnerability. The upgrade is hosted for download at community.spiceworks.com.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.3VulDB Meta Temp Score: 8.2
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.8
NVD Vector: 🔍
CNA Base Score: 9.9
CNA Vector (MITRE): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: DeserializationCWE: CWE-502 / CWE-20
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Help Desk Server 1.3.3
Timeline
11/12/2021 🔍11/09/2023 🔍
11/09/2023 🔍
12/05/2023 🔍
Sources
Advisory: community.spiceworks.comStatus: Confirmed
CVE: CVE-2021-43609 (🔍)
GCVE (CVE): GCVE-0-2021-43609
GCVE (VulDB): GCVE-100-244827
Entry
Created: 11/09/2023 03:55Updated: 12/05/2023 13:30
Changes: 11/09/2023 03:55 (52), 12/05/2023 13:30 (11)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.