Cyber Resilience

CVE-2023-34036

Vmware Spring Hateoas ≤ 1.5.5

Published
17 July 2023
Modified
21 November 2024
Patch / advisory
CVSS Score v3.1 5.3
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:L/A:N
EPSS Score 0.0047 39th percentile
Risk Priority 44 floored blend · peak EPSS

Summary

CVE-2023-34036 is a medium-severity Improper Neutralization of HTTP Headers for Scripting Syntax (CWE-644) vulnerability in Vmware Spring Hateoas. Its CVSS base score is 5.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Content Injection (T1659); ranked at the 39th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Reactive web applications that use Spring HATEOAS to produce hypermedia-based responses might be exposed to malicious forwarded headers if they are not behind a trusted proxy that ensures correctness of such headers, or if they don't have anything else in…

more

place to handle (and possibly discard) forwarded headers either in WebFlux or at the level of the underlying HTTP server. For the application to be affected, it needs to satisfy the following requirements: * It needs to use the reactive web stack (Spring WebFlux) and Spring HATEOAS to create links in hypermedia-based responses. * The application infrastructure does not guard against clients submitting (X-)Forwarded… headers.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1659 Content Injection Initial Access
Adversaries may gain access and continuously communicate with victims by injecting malicious content into systems through online network traffic.
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.
T1059 Command and Scripting Interpreter Execution
Adversaries may abuse command and script interpreters to execute commands, scripts, or binaries.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-41006Same product: Vmware Spring Hateoas
CVE-2026-41007Same product: Vmware Spring Hateoas
CVE-2023-35894Shared CWE-116, CWE-644
CVE-2024-10006Shared CWE-116, CWE-644
CVE-2023-47143Shared CWE-116, CWE-644
CVE-2023-26289Shared CWE-116, CWE-644
CVE-2024-39736Shared CWE-116, CWE-644
CVE-2024-21499Shared CWE-116, CWE-644
CVE-2024-47549Shared CWE-116, CWE-644
CVE-2023-36921Shared CWE-116, CWE-644

Affected Assets

vmware
spring hateoas
2.1.0 · ≤ 1.5.5 · 2.0.0 — 2.0.5

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.1.2
  • V1.2.1
  • V1.2.3
  • V4.2.3

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-116

Validating that output matches expected content directly mitigates failures to properly encode or escape data for its destination context.

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 proper output encoding and header sanitization to prevent scripting 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.

prevents

Secure coding standards explicitly require correct output encoding and escaping to preserve message structure.

finds

Security testing catches header-injection issues before release, covering most of the weakness.

prevents

Secure development lifecycle mandates input validation and output encoding that directly prevents header-injection flaws.

prevents

Application security requirements explicitly call for neutralizing untrusted data in HTTP headers.

prevents

Secure architecture principles reduce injection surfaces but do not prescribe header-specific controls.

References