dbcve.org
Informix Dynamic ServerApplication · Ibm

CVE-2010-4069

HIGH · 8.5 CVSS v2.0 Published 2010-10-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
Stack-based buffer overflow in IBM Informix Dynamic Server (IDS) 7.x through 7.31, 9.x through 9.40, 10.00 before 10.00.xC10, 11.10 before 11.10.xC3, and 11.50 before 11.50.xC3 allows remote authenticated users to execute arbitrary code via long DBINFO keyword arguments in a SQL statement, aka idsdb00165017, idsdb00165019, idsdb00165021, idsdb00165022, and idsdb00165023.

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 confidence

Stack-based buffer overflow vulnerability in IBM Informix Dynamic Server's DBINFO function allows remote authenticated users to execute arbitrary code via overly long keyword arguments in SQL statements. The vulnerability affects versions 7.x-7.31, 9.x-9.40, 10.00 before 10.00.xC10, 11.10 before 11.10.xC3, and 11.50 before 11.50.xC3.

MitigationApply vendor-supplied patches (10.00.xC10, 11.10.xC3, 11.50.xC3 or later) or upgrade to a supported version. Minimize exposure by restricting database access to trusted authenticated users only and isolating the database server behind appropriate network controls.

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
Informix Dynamic ServerApplication
Affected:= 7.31= 9.40.tc5= 9.40.uc1= 9.40.uc2= 9.40.uc3= 9.40.uc5= 9.40.xc5= 9.40.xc7= 10.00= 10.00.tc3tl= 10.00.xc1= 10.00.xc2

CVSS 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
M
Authentication
Single
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/Au:S/C:C/I:C/A:C

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 checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed IBM Informix Dynamic Server version
    Run 'onstat -' or connect to the database and execute: SELECT FIRST 1 DBINFO('version'); via dbaccess or isql. The output displays the exact version string.
    Affected if The version is 7.31, any 7.x version, any 9.x version up to and including 9.40, any 10.00 version before 10.00.xC10, any 11.10 version before 11.10.xC3, or any 11.50 version before 11.50.xC3.
  2. Confirm DBINFO function is available
    Execute a simple DBINFO query: SELECT DBINFO('version') FROM systables WHERE tabid=1; If the query executes without error, the function is present and usable.
    Affected if The DBINFO function executes successfully, indicating it is enabled and accessible in the environment.
  3. Verify remote authenticated access is permitted
    Review network configuration files (sqlhosts, onconfig) and firewall rules to determine if remote TCP connections to the Informix port (typically 9088 or 1526) are allowed. Check for 'NETTYPE' entries in sqlhosts that permit TCP/IP connections.
    Affected if Remote TCP/IP connections to the Informix listener port are permitted to unauthenticated or all authenticated users.
  4. Check for presence of vulnerable specific versions
    Cross-reference the detected version against known vulnerable builds: 7.31; 9.40.tc5, 9.40.uc1, 9.40.uc2, 9.40.uc3, 9.40.uc5, 9.40.xc5, 9.40.xc7; 10.00, 10.00.tc3tl, 10.00.xc1, 10.00.xc2. These are explicitly listed as affected.
    Affected if The installed version exactly matches one of these specific vulnerable build identifiers.

You are affected if IBM Informix Dynamic Server is running a version in the 7.x-7.31, 9.x-9.40, 10.00 pre-xC10, 11.10 pre-xC3, or 11.50 pre-xC3 ranges AND the DBINFO function is accessible to remote authenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied patches (10.00.xC10, 11.10.xC3, 11.50.xC3 or later) or upgrade to a supported version. Minimize exposure by restricting database access to trusted authenticated users only and isolating the database server behind appropriate network controls.

Fix this in Informix Dynamic Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,472.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2010-4069 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2010-4069 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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