CVE-2002-1450
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 UniVerse with UV/ODBC allows attackers to cause a denial of service (client crash or server CPU consumption) via a query with an invalid link between tables, possibly via a buffer overflow.
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 UniVerse UV/ODBC driver contains a vulnerability where malformed SQL queries containing invalid links between tables can trigger either client crashes or excessive server CPU consumption, potentially due to a buffer overflow condition in the ODBC driver when processing malformed table join queries.
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 dataall versionsCVSS 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
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/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.
-
Identify IBM UniVerse installationSearch for IBM UniVerse or U2 Universe installation directories or check system for installed software named 'UniVerse' or 'U2 Universe'Affected if IBM UniVerse or U2 Universe software is found on the system
-
Locate the UV/ODBC driver filesSearch for ODBC driver files associated with UniVerse, such as uvodbc.dll or similar ODBC driver libraries in the UniVerse installation directory or system driver foldersAffected if UV/ODBC driver files are present on the system
-
Check for configured ODBC data sourcesReview Windows ODBC Data Source Administrator (ODBCAD32.exe) or Unix ODBC configuration files for data sources using the UniVerse ODBC driverAffected if Any ODBC data sources are configured to connect to UniVerse databases
-
Verify ODBC connectivity is enabledConfirm the ODBC driver is registered and accessible by attempting to enumerate ODBC drivers or checking driver manager configurationAffected if The UniVerse ODBC driver is registered and available for connections
-
Review ODBC driver versionIf the driver is present, identify its version through driver properties or file version information and compare against any available patch informationAffected if The ODBC driver version cannot be determined or is unpatched
The environment is affected if IBM UniVerse with the UV/ODBC driver is installed and ODBC data sources are configured, since all versions of this product are vulnerable to malformed SQL query handling issues.
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 UniVerse patches or updates to address this vulnerability. If no patches are available, consider restricting ODBC access to trusted clients and implementing query validation or timeout mechanisms to mitigate DoS conditions.
- 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-1450 — 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-1450 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