CVE-2019-4034
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 Content Navigator 3.0CD is could allow an attacker to execute arbitrary code on a user's workstation. When editing an executable file in ICN with Edit service, it will be executed on the user's workstation. IBM X-Force ID: 156000.
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 Content Navigator 3.0CD contains a vulnerability where the Edit service will execute arbitrary code on a user's workstation when editing executable files. An attacker could place a malicious executable file in ICN, trick a user into editing it via the Edit service, and achieve code execution on the victim's machine.
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= 3.0.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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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 IBM Content Navigator installation and versionCheck the IBM Content Navigator installation directory or use the 'about' feature in the ICN administration console to determine the exact version numberAffected if The installed version is exactly 3.0.0 (no patches or updates applied)
-
Locate the Edit service configurationAccess the IBM Content Navigator administration interface and navigate to the Desktop or Repository configuration settings to locate the Edit service settings, or inspect the 'PluginConfig.xml' or 'desktop-config.xml' files in the ICN configuration directoryAffected if The Edit service is enabled and configured for use
-
Verify executable file type associationsIn the ICN admin console, examine the file type mappings or MIME type configurations to see which file extensions are associated with the Edit serviceAffected if Executable file types (.exe, .bat, .cmd, .msi, .dll) are registered with the Edit action/operation
-
Check for executable content in repositoriesUse ICN search or browse repository contents to identify if executable file types are stored and accessible within the ICN-managed repositoriesAffected if Executable files (.exe, .bat, .cmd, .msi, .dll) exist in repositories that ICN manages and are accessible for editing
You are affected if you are running IBM Content Navigator version 3.0.0, the Edit service is enabled, and executable file types are configured to open with the Edit service in your environment.
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 dataDisable or restrict the Edit service functionality for executable file types (e.g., .exe, .bat, .cmd, .msi, .dll) in IBM Content Navigator, or implement proper sandboxing/validation to prevent execution during edit operations.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-4034 — 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-4034 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