PrivX up to 31.2/32.2/33.0 REST API denial of service
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.7 | $0-$5k | 0.00 |
Summary
A vulnerability was found in PrivX up to 31.2/32.2/33.0. It has been classified as problematic. This issue affects some unknown processing of the component REST API. The manipulation leads to denial of service. This vulnerability is documented as CVE-2024-30170. There is not any exploit available. Upgrading the affected component is recommended.
Details
A vulnerability was found in PrivX up to 31.2/32.2/33.0. It has been rated as problematic. This issue affects an unknown code block of the component REST API. The manipulation with an unknown input leads to a denial of service vulnerability. Using CWE to declare the problem leads to CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. Impacted is availability. The summary by CVE is:
PrivX before 34.0 allows data exfiltration and denial of service via the REST API. This is fixed in minor versions 33.1, 32.3, 31.3, and later, and in major version 34.0 and later,
The advisory is shared at privx.docs.ssh.com. The identification of this vulnerability is CVE-2024-30170 since 03/24/2024. Neither technical details nor an exploit are publicly available.
Upgrading to version 31.3, 32.3, 33.1 or 34.0 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.7VulDB Meta Temp Score: 6.7
VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.1
NVD Vector: 🔍
CNA Base Score: 7.5
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: Denial of serviceCWE: CWE-404
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: PrivX 31.3/32.3/33.1/34.0
Timeline
03/24/2024 🔍08/06/2024 🔍
08/06/2024 🔍
08/13/2024 🔍
Sources
Advisory: privx.docs.ssh.comStatus: Confirmed
CVE: CVE-2024-30170 (🔍)
GCVE (CVE): GCVE-0-2024-30170
GCVE (VulDB): GCVE-100-273761
Entry
Created: 08/06/2024 17:01Updated: 08/13/2024 06:16
Changes: 08/06/2024 17:01 (54), 08/13/2024 06:16 (22)
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.