CVE-2017-1677
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 Data Server Driver for JDBC and SQLJ (IBM DB2 for Linux, UNIX and Windows 9.7, 10.1, 10.5, and 11.1) deserializes the contents of /tmp/connlicj.bin which leads to object injection and potentially arbitrary code execution depending on the classpath. IBM X-Force ID: 133999.
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 confidenceThe IBM Data Server Driver for JDBC and SQLJ deserializes the contents of /tmp/connlicj.bin without validation, leading to Java object injection. An attacker with local filesystem access can replace this file with a malicious serialized Java object to achieve arbitrary code execution, depending on vulnerable classes in the classpath.
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
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 IBM DB2 versionRun 'db2level' command or check /opt/ibm/db2/version/DB2_INSTALLATION_PATH/version.txt. On Windows, check Registry key HKLM\SOFTWARE\IBM\DB2\InstalledCopiesAffected if Version matches 9.7, 10.1, 10.5, or 11.1 exactly
-
Locate the vulnerable license fileCheck if the file /tmp/connlicj.bin exists on the system using 'ls -la /tmp/connlicj.bin'Affected if The file exists on the system
-
Verify file permissions on connlicj.binRun 'ls -la /tmp/connlicj.bin' and check the permission bits. The file should not be world-writable or group-writable for the attacker groupAffected if File is writable by users other than the DB2 service account (permissions other than -rw------- or -rw-r-----)
-
Check JDBC driver usageIdentify if Java applications are using the IBM Data Server Driver by examining classpath or loaded JARs (db2jcc4.jar or db2jcc.jar)Affected if The IBM JDBC driver (db2jcc4.jar or db2jcc.jar) is loaded in a running Java process using a vulnerable DB2 version
-
Audit Java classpath for deserialization gadgetsReview the Java application classpath for third-party libraries that contain exploitable deserialization gadgets (common ones include Apache Commons Collections, Groovy, Spring Beans, etc.)Affected if Vulnerable gadgets exist in the classpath alongside the IBM JDBC driver
A system is affected if it runs IBM DB2 version 9.7, 10.1, 10.5, or 11.1 with the IBM JDBC driver, where /tmp/connlicj.bin exists and is writable by non-privileged users, and the Java classpath contains exploitable deserialization gadgets.
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 dataRestrict file permissions on /tmp/connlicj.bin to prevent unauthorized modification and upgrade to a patched IBM DB2 version. Review and harden the Java classpath to remove potentially exploitable deserialization gadgets.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-1677 — 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-2017-1677 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