CVE-2024-35114
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 Control Center 6.2.1 and 6.3.1 could allow a remote attacker to enumerate usernames due to an observable discrepancy between login attempts.
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 Control Center versions 6.2.1 and 6.3.1 contain a username enumeration vulnerability where the application returns different responses (timing, error messages, or behavior) for valid versus invalid usernames during login. This allows remote attackers to systematically discover valid usernames through brute-force or automated enumeration.
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= 6.2.1.0= 6.3.1.0CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 Control Center versionCheck the installed product version through the administration console, about page, or installation metadata. Common paths include the product's built-in version display or system information panel.Affected if The installed version matches exactly 6.2.1.0 or 6.3.1.0
-
Test login response for invalid usernameAttempt to log in with a clearly invalid username that does not exist in the user directory. Record the exact error message, HTTP response code, and response time.Affected if An error message is returned indicating the username does not exist or similar non-specific feedback about username validity
-
Test login response for valid username with wrong passwordAttempt to log in using a known-valid username but with an incorrect password. Record the exact error message, HTTP response code, and response time.Affected if The error message differs from step 2, such as explicitly mentioning password incorrect versus username not found, or returns a different HTTP status code
-
Compare response timing between valid and invalid usernamesSend multiple login requests for both a nonexistent username and a valid username with wrong password. Measure and compare average response times across multiple attempts.Affected if There is a measurable and consistent timing difference between the two types of failed login attempts
-
Check for behavioral differences in login flowObserve the complete login flow including redirects, session handling, and any intermediate responses. Note if valid usernames trigger different intermediate pages or session behaviors.Affected if The application behaves differently (different redirects, session cookies, or flow) for valid usernames versus invalid usernames even on failed authentication
Your environment is affected if you are running IBM Control Center version 6.2.1.0 or 6.3.1.0 and the login process reveals different error messages, timing, or behavior for valid versus invalid usernames during authentication failures.
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.
From vendor dataImplement uniform error responses and timing for both valid and invalid username attempts, ensuring no observable difference exists between login failures due to nonexistent users versus incorrect passwords for valid users.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-35114 — 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-2024-35114 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