CVE-2025-31991
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 · uneditedRate Limiting for attempting a user login is not being properly enforced, making HCL DevOps Velocity susceptible to brute-force attacks past the unsuccessful login attempt limit. This vulnerability is fixed in 5.1.7.
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 · high confidenceHCL DevOps Velocity fails to properly enforce rate limiting for user login attempts, allowing attackers to bypass the configured limit on unsuccessful login attempts and conduct brute-force attacks against user credentials. The vulnerability exists in the authentication mechanism's rate limiting logic.
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< 5.1.7CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 installed HCL DevOps Velocity versionAccess the application administration console or check the product installation directory for version information. Typically found in 'About' or 'System Information' page in the web UI, or check version files in the installation directory.Affected if The installed version is earlier than 5.1.7 (e.g., 5.1.6, 5.0.x, etc.)
-
Locate rate limiting configurationNavigate to the authentication or security settings in the HCL DevOps Velocity administration interface. Look for rate limiting, login attempt limits, or brute-force protection settings.Affected if Rate limiting configuration exists but may not be properly enforced (this is the vulnerability condition)
-
Review authentication logs for login attempt patternsAccess the system logs or authentication audit logs. Search for repeated failed login attempts from the same source IP or for user accounts within a short time window.Affected if Multiple failed login attempts are recorded without apparent throttling or blocking, indicating rate limiting is not functioning
-
Verify rate limiting behavior with test attemptsIf permitted in a non-production environment, attempt multiple failed login attempts (using a wrong password) in rapid succession from a test account and observe whether the system blocks or throttles further attempts.Affected if More than the configured limit of failed attempts are allowed without triggering a lockout or delay
A user is affected if their HCL DevOps Velocity installation is version 5.1.6 or earlier AND rate limiting for login attempts is not being properly enforced, allowing unrestricted brute-force 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 · scoped5.1.7
Upgrade to HCL DevOps Velocity version 5.1.7 or later which contains the fix for proper rate limiting enforcement.
HCL DevOps Velocity 5.1.7
- 1. Back up the current HCL DevOps Velocity installation and database.
- 2. Download HCL DevOps Velocity version 5.1.7 from the HCL Software support portal at support.hcl-software.com.
- 3. Follow the standard HCL DevOps Velocity upgrade procedure documented in the product installation guide.
- 4. Verify the upgrade completed successfully.
- 5. Confirm rate limiting is now properly enforced by testing unsuccessful login attempts past the configured limit.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-31991 — 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-31991 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