| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.3 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in SysAid On-Premise. This affects an unknown part. This manipulation causes path traversal. The identification of this vulnerability is CVE-2023-47246. Furthermore, there is an exploit available. You should upgrade the affected component.
Details
A vulnerability has been found in SysAid On-Premise and classified as critical. Affected by this vulnerability is some unknown functionality. The manipulation with an unknown input leads to a path traversal vulnerability. The CWE definition for the vulnerability is CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
In SysAid On-Premise before 23.3.36, a path traversal vulnerability leads to code execution after an attacker writes a file to the Tomcat webroot, as exploited in the wild in November 2023.
The weakness was shared 11/10/2023. It is possible to read the advisory at documentation.sysaid.com. This vulnerability is known as CVE-2023-47246 since 11/04/2023. Technical details are unknown but an exploit is available. The attack technique deployed by this issue is T1006 according to MITRE ATT&CK.
It is declared as attacked. The CISA Known Exploited Vulnerabilities Catalog lists this issue since 11/13/2023 with a due date of 12/04/2023:
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.Upgrading to version 23.3.36 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at Zero-Day.cz (831). 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.4VulDB Meta Temp Score: 8.3
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CNA Base Score: 9.8
CNA 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: Path traversalCWE: CWE-22
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Attacked
EPSS Score: 🔍
EPSS Percentile: 🔍
KEV Added: 🔍
KEV Due: 🔍
KEV Remediation: 🔍
KEV Ransomware: 🔍
KEV Notice: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Zero-Day.cz: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: On-Premise 23.3.36
Timeline
11/04/2023 🔍11/10/2023 🔍
11/10/2023 🔍
09/09/2024 🔍
Sources
Advisory: documentation.sysaid.comStatus: Confirmed
CVE: CVE-2023-47246 (🔍)
GCVE (CVE): GCVE-0-2023-47246
GCVE (VulDB): GCVE-100-244939
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 11/10/2023 07:04Updated: 09/09/2024 22:30
Changes: 11/10/2023 07:04 (39), 12/06/2023 08:29 (11), 04/30/2024 05:45 (23), 06/05/2024 23:42 (2), 07/08/2024 16:49 (13), 09/09/2024 22:30 (2)
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.