Cyber Resilience

CVE-2024-51451

Ibm Concert 1.0.0 – 2.2.0

Published
04 February 2026
Modified
05 February 2026
Patch / advisory
CVSS Score v3.1 6.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
EPSS Score 0.0022 12th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2024-51451 is a medium-severity Improper Neutralization of HTTP Headers for Scripting Syntax (CWE-644) vulnerability in Ibm Concert. Its CVSS base score is 6.5 (Medium).

Operationally, ranked at the 12th 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

IBM Concert 1.0.0 through 2.1.0 is vulnerable to HTTP header injection, caused by improper validation of input by the HOST headers. This could allow an attacker to conduct various attacks against the vulnerable system, including cross-site scripting, cache poisoning or…

more

session hijacking.

CWE(s)

Related Threats

CVEs Like This One

CVE-2025-33089Same product: Ibm Concert
CVE-2025-33102Same product: Ibm Concert
CVE-2024-52366Same product: Ibm Concert
CVE-2025-12771Same product: Ibm Concert
CVE-2024-52367Same product: Ibm Concert
CVE-2025-33099Same product: Ibm Concert
CVE-2024-43180Same product: Ibm Concert
CVE-2025-36440Same product: Ibm Concert
CVE-2025-33090Same product: Ibm Concert
CVE-2024-41785Same product: Ibm Concert

Affected Assets

ibm
concert
1.0.0 — 2.2.0

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)
  • V4.2.3

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.

detects

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.

prevents

Secure coding standards require proper escaping or rejection of scripting syntax in HTTP headers.

References