CVE-2019-4035
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 could allow attackers to direct web traffic to a malicious site. If attackers make a fake IBM Content Navigator site, they can send a link to ICN users to send request to their Edit client directly. Then Edit client will download documents from the fake ICN website. IBM X-Force ID: 156001.
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 in its Edit client that allows attackers to redirect document download requests to a malicious ICN server. By tricking users into clicking links to a fake ICN site, the Edit client will download documents from the attacker's server instead of the legitimate one, exploiting the client's implicit trust in ICN servers.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 IBM Content Navigator installationSearch for IBM Content Navigator installation directories or check system inventory/scan for icn, contentnavigator, or IBM navigator related processes or servicesAffected if IBM Content Navigator is installed on the system
-
Verify the installed versionCheck the version of IBM Content Navigator by inspecting version files, About dialogs, or using the icnversion command if availableAffected if The installed version is exactly 3.0.0 (or a 3.0.x version within the 3.0CD release)
-
Confirm Edit client is enabledCheck ICN configuration files (such as web.xml, plugin configuration, or registry settings) for the Edit client plugin or feature being loaded/enabledAffected if The Edit client component is installed and enabled in the ICN configuration
-
Inspect ICN server configurationReview the ICN client configuration or preferences files for registered ICN server URLs; look for unexpected or untrusted server entriesAffected if Non-standard or suspicious ICN server URLs are configured in the Edit client settings
-
Examine client logs for redirection attemptsReview IBM Content Navigator client logs or browser console logs for any download requests to unexpected domains, particularly during user document access sessionsAffected if Logs show document downloads being redirected to servers outside the organization or to unrecognized ICN servers
You are affected if IBM Content Navigator version 3.0.0 is installed with the Edit client enabled and there are unrecognized or malicious ICN server configurations that could redirect document downloads.
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 dataUsers should be warned not to click untrusted links; the Edit client should implement server authenticity validation before downloading documents, and organizations should monitor for phishing campaigns using fake ICN sites.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-4035 — 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-4035 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