CVE-2019-4732
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 SDK, Java Technology Edition Version 7.0.0.0 through 7.0.10.55, 7.1.0.0 through 7.1.4.55, and 8.0.0.0 through 8.0.6.0 could allow a local authenticated attacker to execute arbitrary code on the system, caused by DLL search order hijacking vulnerability in Microsoft Windows client. By placing a specially-crafted file in a compromised folder, an attacker could exploit this vulnerability to execute arbitrary code on the system. IBM X-Force ID: 172618.
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 confidenceA DLL search order hijacking vulnerability in IBM SDK Java versions 7.0.0.0-7.0.10.55, 7.1.0.0-7.1.4.55, and 8.0.0.0-8.0.6.0 on Windows allows a local authenticated attacker to execute arbitrary code by placing a malicious DLL in a folder that the Java process searches when loading dynamic libraries.
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>= 7.0.0.0, <= 7.0.10.55>= 7.1.0.0, <= 7.1.4.55>= 8.0.0.0, <= 8.0.6.0= 7.0= 8.0= 8.5= 9.0CVSS 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
- High
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/UI:R/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.
-
Check if IBM SDK Java is installed on WindowsLook for IBM Java installation directories such as C:\Program Files\IBM\Java\ or check the system PATH for IBM Java binaries. Run 'java -version' from command prompt and examine the output for IBM JDK information.Affected if IBM SDK Java is found on the system
-
Determine the installed IBM SDK Java versionRun 'java -version' and capture the full version string, or check the file version of java.exe in the IBM Java bin directory. Look for version numbers in the format 7.0.x.x, 7.1.x.x, or 8.0.x.x.Affected if Version falls within 7.0.0.0-7.0.10.55, 7.1.0.0-7.1.4.55, or 8.0.0.0-8.0.6.0
-
Check if IBM WebSphere Application Server is installedLook for WebSphere installation directories such as C:\IBM\WebSphere\ or check for WebSphere profile directories under the installation path. Run 'versionInfo.bat' or check the installation manifest files.Affected if WebSphere version 7.0, 8.0, 8.5, or 9.0 is installed and uses the vulnerable IBM Java SDK
-
Verify the Java process runs on WindowsConfirm the operating system is Windows since this vulnerability only affects IBM Java on Windows platforms.Affected if Running on Windows with the vulnerable IBM Java versions installed
A user is affected if IBM SDK Java versions 7.0.0.0-7.0.10.55, 7.1.0.0-7.1.4.55, or 8.0.0.0-8.0.6.0 are installed on Windows, or if WebSphere Application Server 7.0, 8.0, 8.5, or 9.0 with bundled vulnerable Java is in use.
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 the IBM JDK updates that address this vulnerability (upgrade to a fixed version beyond 8.0.6.0), or ensure the Java process uses safe DLL loading mechanisms by configuring SetDllDirectory to prevent search order hijacking.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.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,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-4732 — 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-2019-4732 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