CVE-2018-1428
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 GSKit (IBM DB2 for Linux, UNIX and Windows 9.7, 10.1, 10.5, and 11.1) uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information. IBM X-Force ID: 139073.
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 GSKit in IBM DB2 versions 9.7, 10.1, 10.5, and 11.1 uses weaker than expected cryptographic algorithms, which could allow an attacker to decrypt highly sensitive information stored or transmitted by the database.
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= 9.7= 10.1= 10.5= 11.1CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:L/AC:L/PR:L/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 installed DB2 versionRun 'db2level' command or check db2diag.log for version informationAffected if Version is 9.7, 10.1, 10.5, or 11.1 exactly as listed in affected versions
-
Locate GSKit installation directorySearch for gskit binaries such as 'gsk8capicmd_64' or 'gsk7capicmd' in DB2 installation path, typically under 'sqllib/gskit'Affected if GSKit is present and bundled with the affected DB2 version
-
Determine GSKit versionRun 'gsk8capicmd_64 -version' or check GSKit library files for version numberAffected if GSKit version corresponds to the vulnerable versions shipped with DB2 9.7, 10.1, 10.5, or 11.1
-
Review configured cipher suitesCheck DB2 configuration files (dbm cfg) and GSKit configuration for enabled cipher suites; look for weak algorithms such as SSLv3, TLS 1.0, or weak export-grade ciphersAffected if Weak or deprecated cipher suites (SSLv3, TLS 1.0, RC4, 3DES, export ciphers) are enabled in DB2 or GSKit configuration
-
Inspect SSL/TLS connectionsUse network capture or DB2 audit logs to observe which cipher suites are negotiated during client-server communicationsAffected if Connections are established using weak cryptographic algorithms
Your environment is affected if you are running DB2 version 9.7, 10.1, 10.5, or 11.1 with GSKit that has weak cryptographic algorithms enabled or configured.
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 dataUpgrade IBM DB2 to a patched version or apply IBM security patches that address the weak cryptographic algorithms in GSKit. Verify that only strong cipher suites are enabled.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1428 — 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-2018-1428 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