Security Resilience

CVE-2023-47163

DoS in Remarshal Project Remarshal ≤ 0.17.1

Published
13 November 2023
Modified
21 November 2024
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.0097 61th percentile
Risk Priority 59 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-2023-47163 is a high-severity Uncontrolled Recursion (CWE-674) vulnerability in Remarshal Project Remarshal. Its CVSS base score is 7.5 (High).

Operationally, ranked in the top 39% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

EU & UK References

Vulnerability Data

Remarshal prior to v0.17.1 expands YAML alias nodes unlimitedly, hence Remarshal is vulnerable to Billion Laughs Attack. Processing untrusted YAML files may cause a denial-of-service (DoS) condition.

CWE(s)

Related Threats

CVEs Like This One

CVE-2026-47306Shared CWE-674
CVE-2024-31228Shared CWE-674
CVE-2026-14803Shared CWE-674
CVE-2025-67899Shared CWE-674
CVE-2026-69378Shared CWE-674
CVE-2026-63737Shared CWE-674
CVE-2026-89418Shared CWE-674
CVE-2025-50420Shared CWE-674
CVE-2024-58102Shared CWE-674
CVE-2026-64194Shared CWE-674

Affected Assets

remarshal project
remarshal
≤ 0.17.1

Mitigating Controls

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-674

Supports resumption at alternate site when uncontrolled recursion causes primary site failure or crash.

addresses: CWE-674

Prevents uncontrolled recursion that exhausts stack or CPU resources.

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.

blocks

Secure development life cycle requires controls that prevent uncontrolled recursion through design and code review.

blocks

A.8.26 only requires that security requirements (including resilience against attacks such as buffer overflows) be identified and specified during development or acquisition; it does not itself enforce, implement, or prevent uncontrolled recursion from being exploitable in the resulting application.

blocks

A.8.27 mandates establishing and applying secure engineering principles (defense-in-depth, least privilege, security by design, input distrust, hardening, design reviews) but does not itself stop uncontrolled recursion from being introduced or from consuming excessive resources when present; the weakness can still be exploited.

prevents

Secure coding standards directly prohibit or constrain recursive constructs that could exhaust stack or memory.

finds

Security testing in development can detect excessive recursion via static analysis or fuzzing.

finds

Capacity management includes monitoring and limits that mitigate resource exhaustion from runaway recursion.

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

References