CVE-2024-49342
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 Informix Dynamic Server 12.10 and 14.10 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 · high confidenceIBM Informix Dynamic Server versions 12.10 and 14.10 contain a weak account lockout mechanism (or lack thereof) that permits unlimited login attempts, enabling remote attackers to conduct brute force attacks against user credentials.
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= 12.10= 14.10CVSS 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 Informix versionRun 'onstat -' or check Informix version via 'onmode -version' or query the sysmaster database for version informationAffected if Installed version is 12.10 or 14.10
-
Check authentication configuration fileLocate and inspect the Informix configuration file (onconfig or sqlhosts) for authentication-related settings, specifically looking for account lockout, password policy, or login attempt limitsAffected if No account lockout or login attempt limits are configured, or configuration is missing entirely
-
Verify account lockout policy settingsQuery Informix's authentication settings via 'onmode -secure' or check the $INFORMIXDIR/etc/$ONCONFIG file for CONNECTION_AUTHENTICATION, USEOSTIME, or similar security parametersAffected if The authentication configuration does not enforce account lockout after failed login attempts (typically should lock after 3-5 attempts)
-
Inspect security audit logsReview Informix logs (online.log orMessage Log) for repeated failed login attempts against user accountsAffected if Logs show multiple failed login attempts without any account being locked out, indicating unlimited attempts are allowed
You are affected if you run Informix Dynamic Server version 12.10 or 14.10 and your authentication configuration lacks enforced account lockout after failed login attempts, allowing unlimited 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.
From vendor dataImplement and enforce a proper account lockout policy by configuring Informix's authentication settings to lock accounts after a reasonable number of failed login attempts (typically 3-5) for a defined duration.
- 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-2024-49342 — 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-49342 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