Cyber Resilience

CVE-2025-36363

Hcltech Devops Plan 3.0.0 – 3.0.6

Published
03 March 2026
Modified
27 July 2026
Patch / advisory
CVSS Score v3.1 5.9
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS Score 0.0024 15th percentile
Risk Priority 45 floored blend · peak EPSS

Summary

CVE-2025-36363 is a medium-severity Improper Restriction of Excessive Authentication Attempts (CWE-307) vulnerability in Hcltech Devops Plan. Its CVSS base score is 5.9 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Brute Force (T1110); ranked at the 15th 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-7 (Unsuccessful Logon Attempts) — 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-2025-36363 is a vulnerability in IBM DevOps Plan versions 3.0.0 through 3.0.5 stemming from an inadequate account lockout setting (CWE-307). This flaw enables a remote attacker to brute force account credentials due to insufficient protections against repeated login attempts. The issue carries a CVSS v3.1 base score of 5.9 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N), indicating network accessibility, high attack complexity, no privileges required, no user interaction, unchanged scope, high confidentiality impact, and no integrity or availability impact.

A remote attacker without privileges can exploit this vulnerability by conducting brute force attacks against login credentials. Success grants unauthorized access to sensitive account data, potentially compromising confidentiality, though the high attack complexity limits feasibility for low-sophistication adversaries.

IBM has issued an advisory detailing mitigations at https://www.ibm.com/support/pages/node/7261934. Security practitioners should consult this page for patch information and recommended configurations to enforce proper account lockout mechanisms.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

IBM DevOps Plan 3.0.0 through 3.0.5 uses an inadequate account lockout setting that could allow a remote attacker to brute force account credentials.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1110 Brute Force Credential Access
Adversaries may use brute force techniques to gain access to accounts when passwords are unknown or when password hashes are obtained.
T1110.001 Password Guessing Credential Access
Adversaries with no prior knowledge of legitimate credentials within the system or environment may guess passwords to attempt access to accounts.
T1110.003 Password Spraying Credential Access
Adversaries may use a single or small list of commonly used passwords against many different accounts to attempt to acquire valid account credentials.
T1110.004 Credential Stuffing Credential Access
Adversaries may use credentials obtained from breach dumps of unrelated accounts to gain access to target accounts through credential overlap.
T1078 Valid Accounts Stealth
Adversaries may obtain and abuse credentials of existing accounts as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-37507Same product: Hcltech Devops Plan
CVE-2026-4096Same product: Hcltech Devops Plan
CVE-2024-42176Same vendor: Hcltech
CVE-2023-37508Same product: Hcltech Devops Plan
CVE-2025-36364Same product: Hcltech Devops Plan
CVE-2025-31991Same vendor: Hcltech
CVE-2026-25113Shared CWE-307
CVE-2026-35597Shared CWE-307
CVE-2025-1496Shared CWE-307
CVE-2025-12896Shared CWE-307

Affected Assets

hcltech
devops plan
3.0.0 — 3.0.6

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)
  • 2 hardening rules · 1 OS baseline
Validate
Prove the fix (OWASP ASVS)

Mitigating Controls (NIST 800-53 r5) AI

AC-7 directly enforces limits on consecutive failed logons, structurally blocking brute-force exploitation of the weakness.

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.AA-03 mostly match
prevents

Authentication enforcement directly includes lockout, throttling, and MFA policies that prevent brute-force attempts.

DE.CM-03 partial match
prevents

Behavioral monitoring of authentication activity can detect excessive failed attempts after they occur.

PR.PS-04 partial match
prevents

Generating auth logs enables later detection or forensics but does not itself restrict attempts.

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

CAPTCHA, account lock-out after repeated failures, and alerts on excessive attempts directly stop automated brute-force guessing of credentials.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).

RHEL 7 (2 rules)
  • V-204427 The Red Hat Enterprise Linux operating system must be configured to lock accounts for a minimum of 15 minutes after three unsuccessful logon attempts within a 15-minute timeframe. prevents CWE-307
  • V-204428 The Red Hat Enterprise Linux operating system must lock the associated account after three unsuccessful root logon attempts are made within a 15-minute period. prevents CWE-307

References