Security Resilience

CVE-2024-47215

Snowplow Snowbridge

Published
03 April 2025
Modified
23 April 2025
Patch / advisory
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.0042 34th percentile
Risk Priority 58 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-47215 is a high-severity Improper Check or Handling of Exceptional Conditions (CWE-703) vulnerability in Snowplow Snowbridge. Its CVSS base score is 7.5 (High).

Operationally, ranked at the 34th 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 SC-24 (Fail in Known State) and SI-17 (Fail-safe Procedures) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

An issue was discovered in Snowbridge setups sending data to Google Tag Manager Server Side. It involves attaching an invalid GTM SS preview header to events, causing them to be retried indefinitely. As a result, the performance of forwarding events…

more

to GTM SS overall can be affected (latency, throughput).

CWE(s)

Related Threats

CVEs Like This One

CVE-2024-47212Same vendor: Snowplow
CVE-2024-47213Same vendor: Snowplow
CVE-2024-56528Same vendor: Snowplow
CVE-2024-47217Same vendor: Snowplow
CVE-2024-47214Same vendor: Snowplow
CVE-2025-24371Shared CWE-703
CVE-2026-34388Shared CWE-703
CVE-2023-5563Shared CWE-703
CVE-2024-31883Shared CWE-703
CVE-2024-51491Shared CWE-703

Affected Assets

snowplow
snowbridge
all versions

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Enforces failure to a known state while preserving required properties, limiting impact of unhandled exceptions.

Mandates explicit fail-safe procedures triggered by indicated failures, structurally preventing unhandled exceptional conditions.

Requires application of security engineering principles that include robust exception and error handling during design.

Requires generation of safe, actionable error messages that directly addresses proper handling of exceptional conditions.

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.

removes

A.8.26 only requires that security requirements (including resilience against attacks like SQL injection) be identified and specified during development or acquisition; it does not itself remove, fix, or eliminate any exceptional-condition handling defects already present in code.

removes

A.8.28 mandates secure coding practices, principles, defect removal during coding/review, and prohibiting insecure techniques that directly produce improper exception handling; this removes most instances of the first-party code defect, with a bounded remainder in incomplete adoption or edge-case defects not captured by the baseline.

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-703, a pillar-level weakness, and none of its children carries one either.

References