Cyber Resilience

CVE-2024-22348

Hcltech Devops Velocity 5.0.0

Published
20 January 2025
Modified
27 July 2026
Patch / advisory
View 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.0035 28th percentile
Risk Priority 44 floored blend · peak EPSS

Summary

CVE-2024-22348 is a medium-severity Permissive Cross-domain Security Policy with Untrusted Domains (CWE-942) vulnerability in Hcltech Devops Velocity. Its CVSS base score is 5.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Drive-by Compromise (T1189); ranked at the 28th 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 AC-4 (Information Flow Enforcement) and SC-7 (Boundary Protection) — 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.

CVE-2024-22348 is a Cross-Origin Resource Sharing (CORS) misconfiguration vulnerability affecting IBM DevOps Velocity 5.0.0 and IBM UrbanCode Velocity versions 4.0.0 through 4.0.25. The flaw arises because the software does not limit the domain name to only trusted domains, enabling improper CORS policies. It has a CVSS v3.1 base score of 5.3 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N) and is associated with CWE-942 (Permissive Cross-domain Policy with Untrusted Domains). The vulnerability was published on 2025-01-20.

An unauthenticated attacker with network access can exploit this vulnerability with low complexity and no user interaction required. Successful exploitation allows the attacker to carry out privileged actions and retrieve sensitive information by bypassing intended CORS restrictions.

IBM has published a security bulletin at https://www.ibm.com/support/pages/node/7172750 providing details on the vulnerability, affected versions, and recommended mitigation steps, including applying available patches.

OWASP Top 10 for Web (2025)

A02:2025 Security Misconfiguration

EU & UK References

Vulnerability Data

IBM DevOps Velocity 5.0.0 and IBM UrbanCode Velocity 4.0.0 through 4.0. 25 uses Cross-Origin Resource Sharing (CORS) which could allow an attacker to carry out privileged actions and retrieve sensitive information as the domain name is not being limited to…

more

only trusted domains.

CWE(s)
CWE-942

Related Threats

MITRE ATT&CK Enterprise Techniques

T1189 Drive-by Compromise Initial Access
Adversaries may gain access to a system through a user visiting a website over the normal course of browsing.
attack.mitre.org →
T1557 Adversary-in-the-Middle Credential Access
Adversaries may attempt to position themselves between two or more networked devices using an adversary-in-the-middle (AiTM) technique to support follow-on behaviors such as [Network Sniffing](https://attack.
attack.mitre.org →
T1659 Content Injection Initial Access
Adversaries may gain access and continuously communicate with victims by injecting malicious content into systems through online network traffic.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-22347Same product: Hcltech Devops Velocity
CVE-2024-22349Same product: Hcltech Devops Velocity
CVE-2025-55274Same vendor: Hcltech
CVE-2026-12084Same vendor: Ibm
CVE-2024-45642Same vendor: Ibm
CVE-2023-37401Same vendor: Ibm
CVE-2025-13984Shared CWE-942
CVE-2026-50088Shared CWE-942
CVE-2026-24435Shared CWE-942
CVE-2026-5302Shared CWE-942

Affected Assets

hcltech
devops velocity
5.0.0
ibm
urbancode velocity
4.0.0 — 4.0.15

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)
  • V3.4.3
  • V3.4.6
  • V3.5.2

Mitigating Controls (NIST 800-53 r5) AI

AC-4 Information Flow Enforcement good match

Information flow enforcement requires approved authorizations and would reject policies permitting untrusted domains.

SC-7 Boundary Protection partial match

Boundary protection at external interfaces stops unauthorized cross-domain communication allowed by permissive policies.

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-01 mostly match
prevents

Hardened configuration baselines and reviews directly prevent permissive CSP or cross-domain policies.

PR.PS-06 mostly match
prevents

Secure SDLC activities include review and testing of web security policies to avoid untrusted domains.

ID.RA-01 partial match
prevents

Vulnerability identification processes can surface permissive policy misconfigurations.

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.29 Security testing in development and acceptance mostly match
finds

Security testing can detect overly permissive cross-domain policies but does not prevent their initial introduction.

A.8.20 Networks security partial match
degrades

Network security policies can restrict cross-domain communication but do not specifically mandate strict CSP or cross-domain policy configuration.

A.8.21 Security of network services partial match
degrades

Security of network services includes defining allowed endpoints, which can limit untrusted domains but does not directly address web-client policy files.

A.8.23 Web filtering partial match
degrades

Web filtering can block untrusted domains at the network level, partially mitigating permissive cross-domain policies.

A.8.26 Application security requirements partial match
prevents

Application security requirements should specify secure CSP and cross-domain policy settings, directly addressing the weakness.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles include defining trust boundaries, which can reduce permissive cross-domain allowances.

References