CVE-2002-0555
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 Web DataBlade 4.12 unescapes user input even if an application has escaped it, which could allow remote attackers to execute SQL code in a web form even when the developer has attempted to escape it.
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 Web DataBlade 4.12 contains a vulnerability where the application unconditionally unescapes user input, even when the application developer has already applied escaping to prevent SQL injection. This circumvents developer-implemented SQL injection defenses, allowing remote attackers to inject and execute arbitrary SQL code through web form inputs.
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= 4.10= 4.11= 4.12= 4.13CVSS 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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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.
-
Confirm IBM Informix Web DataBlade installationLocate the Web DataBlade installation on the Informix server - check the DataBlade installation directory, registry, or query the Informix server for installed DataBlade modulesAffected if Web DataBlade is present on the system
-
Determine Web DataBlade versionQuery the installed version of Web DataBlade using Informix administration tools or check version files - compare against the affected versions 4.10, 4.11, 4.12, and 4.13Affected if Version is 4.10, 4.11, 4.12, or 4.13
-
Identify web forms accepting user inputReview web applications that use the Informix database to determine if they utilize Web DataBlade to process user-submitted data through web formsAffected if Web forms that accept user input and pass it to Web DataBlade are in use
-
Verify dynamic SQL usage with web inputExamine application code or configuration to determine if web form inputs are incorporated into dynamic SQL queries - the vulnerability bypasses any developer-applied escaping when user input is processedAffected if Web form inputs are used in dynamic SQL queries that rely on application-level escaping for protection
The environment is affected if Web DataBlade version 4.10, 4.11, 4.12, or 4.13 is installed and web applications use it to process user input in SQL queries.
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 vendor patch/upgrade from Web DataBlade 4.12 to a patched version, or if unsupported, implement input validation and SQL injection mitigation at the web application firewall or application layer to compensate for the flawed escaping behavior.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2002-0555 — 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-2002-0555 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