osTicket Plugins audit/class.audit.php getOrder order sql injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.5 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in osTicket Plugins and classified as critical. This impacts the function getOrder of the file audit/class.audit.php. This manipulation of the argument order causes sql injection.
This vulnerability is registered as CVE-2022-31890. No exploit is available.
It is suggested to install a patch to address this issue.
Details
A vulnerability was found in osTicket Plugins (Ticket Tracking Software) (the affected version unknown). It has been declared as critical. Affected by this vulnerability is the function getOrder of the file audit/class.audit.php. The manipulation of the argument order with an unknown input leads to a sql injection vulnerability. The CWE definition for the vulnerability is CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
SQL Injection vulnerability in audit/class.audit.php in osTicket osTicket-plugins before commit a7842d494889fd5533d13deb3c6a7789768795ae via the order parameter to the getOrder function.
The weakness was published 04/06/2023 as 0b59afbd2d4ccd0522552198a9aaf1ec05b5071e. The advisory is shared at github.com. This vulnerability is known as CVE-2022-31890 since 05/31/2022. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1505 for this issue.
By approaching the search of inurl:audit/class.audit.php it is possible to find vulnerable targets with Google Hacking.
Applying the patch 0b59afbd2d4ccd0522552198a9aaf1ec05b5071e is able to eliminate this problem. The bugfix is ready for download at github.com.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.6
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
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: Sql injectionCWE: CWE-89 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
Google Hack: 🔍
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: PatchStatus: 🔍
0-Day Time: 🔍
Patch: 0b59afbd2d4ccd0522552198a9aaf1ec05b5071e
Timeline
05/31/2022 🔍04/06/2023 🔍
04/06/2023 🔍
02/14/2025 🔍
Sources
Advisory: 0b59afbd2d4ccd0522552198a9aaf1ec05b5071eStatus: Confirmed
CVE: CVE-2022-31890 (🔍)
GCVE (CVE): GCVE-0-2022-31890
GCVE (VulDB): GCVE-100-225025
Entry
Created: 04/06/2023 08:40Updated: 02/14/2025 06:04
Changes: 04/06/2023 08:40 (44), 02/14/2025 06:04 (26)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.