CVE-2017-14196
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 · uneditedAn issue was discovered in Squiz Matrix from 5.3 through to 5.3.6.1 and 5.4.1.3. An information disclosure caused by a Path Traversal issue in the 'File Bridge' plugin allowed the existence of files outside of the bridged path to be confirmed.
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 confidenceA path traversal vulnerability in the File Bridge plugin of Squiz Matrix allows attackers to confirm the existence of files outside the intended bridged directory through directory traversal sequences, leading to information disclosure about the filesystem structure.
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>= 5.3.0.0, <= 5.3.6.1= 5.4.1.3CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/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 Squiz Matrix versionLocate the version file or check the admin interface system information page (typically at /_admin/system_info or via the CMS dashboard)Affected if The displayed version matches 5.3.0.0 through 5.3.6.1, or equals exactly 5.4.1.3
-
Confirm File Bridge plugin is enabledAccess the Squiz Matrix admin panel, navigate to System Management > Plugins or Bridge Settings, and verify the File Bridge plugin statusAffected if File Bridge plugin is listed as active or enabled in the plugin management interface
-
Check for exposed File Bridge endpointLook for the File Bridge asset or endpoint in your Squiz Matrix installation, typically accessible via URLs containing '/file_bridge/' or similar bridge asset pathsAffected if The File Bridge functionality is accessible over HTTP/HTTPS without additional authentication barriers
-
Review filesystem access patternsExamine web server access logs for requests containing '../' sequences targeting the File Bridge endpoint (e.g., patterns like '/file_bridge/..%2F..%2Fetc/')Affected if Log analysis reveals traversal attempts against the File Bridge, indicating active targeting of this vulnerability
You are affected if Squiz Matrix version is between 5.3.0.0 and 5.3.6.1 inclusive, or exactly 5.4.1.3, AND the File Bridge plugin is enabled and accessible.
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 to a patched version of Squiz Matrix that addresses the path traversal vulnerability, or implement strict path validation in the File Bridge plugin to ensure all file access is confined to the designated bridged path.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-14196 — 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-14196 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