CVE-2024-48952

CVE-2024-48952 is a medium-severity vulnerability in Logpoint Soar with a CVSS 3.x base score of 6.4. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-306.

Key facts

Description

An issue was discovered in Logpoint before 7.5.0. SOAR uses a static JWT secret key to generate tokens that allow access to SOAR API endpoints without authentication. This static key vulnerability enables attackers to create custom JWT secret keys for unauthorized access to these endpoints.

Frequently asked questions

What is CVE-2024-48952?
An issue was discovered in Logpoint before 7.5.0. SOAR uses a static JWT secret key to generate tokens that allow access to SOAR API endpoints without authentication. This static key vulnerability enables attackers to create custom JWT secret keys for unauthorized access to these endpoints.
How severe is CVE-2024-48952?
CVE-2024-48952 has a CVSS 3.x base score of 6.4, rated medium severity. It is exploitable over an adjacent network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity low, and availability low.
Is CVE-2024-48952 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (19th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2024-48952?
CVE-2024-48952 affects Logpoint Soar. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2024-48952?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2024-48952 have an EU (EUVD) identifier?
Yes. CVE-2024-48952 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-43146.
When was CVE-2024-48952 published?
CVE-2024-48952 was published on 2024-11-07 and last updated on 2026-06-17.

References

Affected products (1)

Other CWE-306 (Missing Authentication for Critical Function) vulnerabilities

Browse all CWE-306 (Missing Authentication for Critical Function) vulnerabilities →