Security Resilience

CVE-2024-37759

Datagear ≤ 5.0.0

Public PoC
Published
24 June 2024
Modified
13 June 2025
CVSS Score v3.1 9.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.028 86th percentile
Risk Priority 97 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2024-37759 is a critical-severity Injection (CWE-74) vulnerability in Datagear Datagear. Its CVSS base score is 9.8 (Critical).

Operationally, ranked in the top 14% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — 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.

DataGear v5.0.0 and earlier contains a SpEL expression injection vulnerability in its Data Viewing interface, tracked as CWE-74. The flaw allows untrusted input to be evaluated as Spring Expression Language expressions, resulting in a CVSS 3.1 score of 9.8 that reflects network-accessible attack vectors without authentication or user interaction.

An unauthenticated remote attacker can supply crafted expressions through the affected interface to execute arbitrary code on the server, achieving full read/write access and service disruption. The high CVSS vector confirms that successful exploitation can impact confidentiality, integrity, and availability simultaneously.

Public references include a working proof-of-concept repository and an open issue filed against the DataGear project on GitHub, but no vendor advisory or patch details are provided in the available sources. The associated EPSS score has reached 0.8067 at peak with no documented low-to-high trajectory, indicating substantial exploitation interest following disclosure.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

DataGear v5.0.0 and earlier was discovered to contain a SpEL (Spring Expression Language) expression injection vulnerability via the Data Viewing interface.

CWE(s)

Related Threats

CVEs Like This One

CVE-2023-7299Same product: Datagear Datagear
CVE-2024-23830Shared CWE-74
CVE-2023-35075Shared CWE-74
CVE-2025-3026Shared CWE-74
CVE-2024-29896Shared CWE-74
CVE-2025-67486Shared CWE-74
CVE-2024-47764Shared CWE-74
CVE-2023-48835Shared CWE-74
CVE-2025-20337Shared CWE-74
CVE-2025-20284Shared CWE-74

Affected Assets

datagear
datagear
≤ 5.0.0

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SI-10 directly requires validation of information inputs to reject malformed or special-element content before it reaches downstream parsers.

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.15 Logging partial match
finds

Logging supports detection of injection attempts but does not prevent the weakness.

finds

Monitoring activities can identify active injection attacks after they occur.

blocks

A.8.25 mandates a secure SDLC process that includes secure coding guidelines, security requirements, checkpoints, testing (scans/penetration), and developer training to reduce injection flaws, but does not itself enforce or guarantee neutralization of special elements at runtime.

blocks

Application security requirements explicitly call for controls against injection attacks in software design.

blocks

A.8.27 mandates security-by-design principles (including distrust external input, data validation/sanitization, secure architecture layers, and design reviews against attack patterns) that reach injection when applied to output construction; this stops exploitation for a minority slice (e.g. where principles drive sanitization) but leaves most code-level injection defects untouched without further implementation rigor.

prevents

Secure coding standards require proper neutralization of special elements, directly addressing CWE-74.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-74, a class-level weakness, and none of its children carries one either.

References