Security Resilience

CVE-2024-22334

Ibm Devops Deploy 8.0.0.0 – 8.0.1.0

Published
12 April 2024
Modified
29 January 2025
Patch / advisory
CVSS Score v3.1 4.4
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:H/A:N
EPSS Score 0.0044 38th percentile
Risk Priority 35 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS scores by FIRST (EPSS SIG), generated by Empirical Security. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2024-22334 is a medium-severity Incorrect Permission Assignment for Critical Resource (CWE-732) vulnerability in Ibm Devops Deploy. Its CVSS base score is 4.4 (Medium).

Operationally, ranked at the 38th 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-3 (Access Enforcement) and AC-6 (Least Privilege) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

IBM UrbanCode Deploy (UCD) 7.0 through 7.0.5.20, 7.1 through 7.1.2.16, 7.2 through 7.2.3.9, 7.3 through 7.3.2.4 and IBM DevOps Deploy 8.0 through 8.0.0.1 could be vulnerable to incomplete revocation of permissions when deleting a custom security resource type. When deleting…

more

a custom security type, associated permissions of objects using that type may not be fully revoked. This could lead to incorrect reporting of permission configuration and unexpected privileges being retained. IBM X-Force ID: 279974.

CWE(s)

Related Threats

CVEs Like This One

CVE-2026-12086Same product: Ibm Devops Deploy
CVE-2024-51472Same product: Ibm Devops Deploy
CVE-2025-1998Same product: Ibm Devops Deploy
CVE-2025-36360Same product: Ibm Devops Deploy
CVE-2024-22339Same product: Ibm Devops Deploy
CVE-2024-22331Same product: Ibm Devops Deploy
CVE-2025-1997Same product: Ibm Devops Deploy
CVE-2024-54176Same product: Ibm Devops Deploy
CVE-2024-56469Same product: Ibm Devops Deploy
CVE-2024-55904Same product: Ibm Devops Deploy

Affected Assets

ibm
devops deploy
8.0.0.0 — 8.0.1.0
ibm
urbancode deploy
7.0.0.0 — 7.0.5.21 · 7.1.0.0 — 7.1.2.17 · 7.2.0.0 — 7.2.3.10

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Enforces the access control policy that defines permissions on resources, thereby stopping incorrect assignments from remaining exploitable.

Directly requires assignment of only the minimum necessary permissions, preventing overly broad grants on critical 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

A.5.15 directly requires determining access needs, defining and communicating an access control policy, implementing rules that map rights/restrictions to entities (including consistency with classification), and considering need-to-know, privileged restrictions, segregation, formal authorization, and dynamic factors — which squarely stops most incorrect permission assignments from being exploitable; the bounded remainder is misconfigurations that violate the policy itself.

blocks

A.5.18 directly governs the provisioning, review, adjustment and revocation of logical access rights (including for critical resources) according to business needs, policy, SoD and risk, which stops most unintended actors from reading/modifying via incorrect permissions; the bounded remainder is incorrect permission assignments that are not access-right decisions at all (e.g. filesystem umask, ACL syntax errors).

blocks

A.8.2 directly controls the allocation, review, expiry, and use of privileged rights (including least-privilege, temporary grants, no generic IDs, and higher authentication), which stops most unintended read/modify cases named by CWE-732; the bounded remainder is non-privileged incorrect permission assignments (e.g. on files or objects that never require privilege).

blocks

Requiring explicit configuration of access controls and permissions for files, applications and services counters the assignment of overly permissive default or incorrect file-system rights.

blocks

A.8.32's formal change process (impact assessment, authorization, testing per 8.29, documentation, and enforcement across the SDLC) prevents most incorrect permission assignments on critical resources by catching them before or during implementation; the bounded remainder is ad-hoc/emergency changes or post-deployment permission drift outside the managed process.

blocks

A.8.4 strictly controls read/write access to source code and associated critical resources per roles/business needs (with audit and change-control integration), directly preventing most unintended read/modify cases in CWE-732; the bounded remainder is misconfigured permissions on non-source-code critical resources (e.g. configs, keys, or runtime artifacts) outside the clause's explicit scope.

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-732, a class-level weakness. Rules are authored against its narrower children: CWE-276, CWE-277, CWE-281.

References