Cyber Resilience

CVE-2024-57971

Published
16 February 2025
Modified
15 April 2026
CVSS Score v3.1 9.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
EPSS Score 0.0070 50th percentile
Risk Priority 60 floored blend · peak EPSS

Summary

CVE-2024-57971 is a critical-severity Resource Injection (CWE-99) vulnerability in Readthedocs (inferred from references). Its CVSS base score is 9.1 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 50th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and AC-3 (Access Enforcement) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2024-57971 is a vulnerability in DataSourceResource.java within the SpagoBI API support of Knowage Server in KNOWAGE versions before 8.1.30. The flaw arises because the component fails to validate that JNDI names begin with "java:comp/env/jdbc/", allowing improper handling of resource identifiers (CWE-99). It has a CVSS v3.1 base score of 9.1 (AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H), indicating critical severity due to its potential for high-impact network-accessible exploitation.

A high-privileged remote attacker (PR:H) can exploit this vulnerability with low complexity and no user interaction required. Successful exploitation enables high confidentiality, integrity, and availability impacts across a changed scope (S:C), potentially allowing the attacker to manipulate JNDI lookups beyond intended data source contexts.

Mitigation is addressed in KNOWAGE version 8.1.30, as detailed in the GitHub commit f7d0362f737e1b0db1cc9cc95b1236d62d83dd0c and the release comparison between v8.1.29 and v8.1.30. Security practitioners should upgrade to the patched version and review JNDI configurations in affected deployments. Additional details are available in the Knowage documentation at spagobi.readthedocs.io.

OWASP Top 10 for Web (2025)

A05:2025 Injection

EU & UK References

Vulnerability Data

DataSourceResource.java in the SpagoBI API support in Knowage Server in KNOWAGE before 8.1.30 does not ensure that java:comp/env/jdbc/ occurs at the beginning of a JNDI Name.

CWE(s)
CWE-99

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-1575Shared CWE-99
CVE-2026-7303Shared CWE-99
CVE-2026-10299Shared CWE-99
CVE-2025-0625Shared CWE-99
CVE-2026-5414Shared CWE-99
CVE-2026-10168Shared CWE-99
CVE-2025-2410Shared CWE-99
CVE-2023-3517Shared CWE-99
CVE-2026-62910Shared CWE-99
CVE-2025-9619Shared CWE-99

Affected Assets

Readthedocs
—
inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.3.8
  • V1.3.9
  • V1.3.11
  • V9.2.2

Mitigating Controls (NIST 800-53 r5) AI

SI-10 Information Input Validation good match

Directly requires validation of inputs before they are accepted as resource identifiers.

AC-3 Access Enforcement partial match

Enforces authorizations on resource access so an injected identifier cannot reach outside the intended sphere.

AC-4 Information Flow Enforcement partial match

Enforces information flow rules that block use of untrusted identifiers to reach unauthorized resources.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input validation and sanitization that prevent resource-identifier injection flaws.

PR.AA-05 partial match
prevents

Least-privilege access policy and enforcement limits damage from injected resource identifiers even when input validation is absent.

PR.IR-01 partial match
prevents

Network segmentation and unauthorized-access controls reduce the blast radius of successful resource injection.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect resource-injection flaws but does not itself implement preventive controls.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC mandates input validation and resource-identifier sanitization that directly prevents resource injection.

A.8.26 Application security requirements partial match
prevents

Application security requirements explicitly call for controls on external identifiers used to access resources.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles reduce attack surface for resource injection but do not prescribe identifier validation.

A.8.28 Secure coding partial match
prevents

Secure coding standards require strict validation and whitelisting of all resource identifiers before use.

A.8.3 Information access restriction partial match
mitigates

Information-access-restriction policies limit which resources can be referenced, indirectly reducing injection impact.

References