CVE-2025-36363
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIBM 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceIBM DevOps Plan versions 3.0.0 through 3.0.5 implements inadequate account lockout settings, enabling remote attackers to conduct brute force attacks against user credentials without account suspension or lockout after repeated failed authentication attempts.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 3.0.0, < 3.0.6CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify IBM DevOps Plan installationLocate the IBM DevOps Plan installation directory or check installed packages on the system where the application runsAffected if The application is installed and version cannot be determined or is within 3.0.0-3.0.5 range
-
Determine the installed versionUse the system's package manager, version command, or check the product's about/version information panel within the applicationAffected if The installed version is >= 3.0.0 and < 3.0.6
-
Verify account lockout policy configurationAccess the security or authentication settings in the IBM DevOps Plan administration console and review the account lockout threshold, lockout duration, and retry limitsAffected if No account lockout threshold is set, threshold is set to 0, or lockout is not enforced after failed login attempts
-
Check for authentication rate limitingReview the application's security configuration for any rate limiting, IP blocking, or CAPTCHA enforcement on failed login attemptsAffected if No rate limiting, IP-based throttling, or CAPTCHA is configured to slow brute force attempts
A user is affected if IBM DevOps Plan version 3.0.0 through 3.0.5 is installed and account lockout or rate limiting is not properly configured to prevent repeated authentication attempts.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped3.0.6
Implement and enforce a robust account lockout policy that temporarily or permanently disables accounts after a defined number of failed login attempts (e.g., 3-5 failed attempts triggering a 15-30 minute lockout).
IBM DevOps Plan 3.0.6
- Upgrade IBM DevOps Plan from any version 3.0.0-3.0.5 to version 3.0.6 or later
- After upgrading, verify that account lockout policies are properly enforced by testing with incorrect credentials
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-36363 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-36363 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data