CVE-2025-1991
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,14.10, and15.0 could allow a remote attacker to cause a denial of service due to an integer underflow when processing packets.
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 Informix Dynamic Server versions 12.10, 14.10, and 15.0 contain an integer underflow vulnerability in packet processing that allows remote attackers to cause a denial of service.
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.10= 15.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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 Informix Dynamic Server versionRun the 'onstat -' command or check the Informix version file (typically $INFORMIXDIR/etc/onconfig) to retrieve the installed version numberAffected if version matches 12.10, 14.10, or 15.0 exactly
-
Confirm Informix network listener is activeCheck for Informix listening ports (default 9088 for DRDA, 1526 for sqlinet, or custom ports) using 'netstat -an' or 'ss -tlnp' to see if the server is bound to network interfacesAffected if Informix is listening on accessible network ports (not localhost-only)
-
Verify packet processing is enabledReview Informix configuration parameters in $INFORMIXDIR/etc/onconfig or oncfg file, specifically network-related settings such as NETTYPE, MAX_INCOMPLETE_CONNECTIONS, or similar packet handling parametersAffected if network packet processing is enabled and server accepts remote connections
-
Check for recent connection attempts or crashesReview Informix online log files (typically in $INFORMIXDIR/logs/online.log or messages log) for entries indicating crashes, signal 11 errors, or unusual packet handling failuresAffected if logs show recent unexpected terminations or packet processing errors matching this vulnerability pattern
A user is affected if their Informix Dynamic Server is version 12.10, 14.10, or 15.0 and the server is exposed to network packet processing, since the integer underflow triggers when handling incoming network packets.
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 dataApply IBM-supplied patches for this vulnerability or upgrade to a patched version; implement network segmentation to limit exposure to untrusted networks.
- Consultation3.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-1991 — 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-1991 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