CVE-2017-7433
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 absolute path traversal vulnerability (CWE-36) in Micro Focus Vibe 4.0.2 and earlier allows a remote authenticated attacker to download arbitrary files from the server by submitting a specially crafted request to the viewFile endpoint. Note that the attack can be performed without authentication if Guest access is enabled (Guest access is disabled by default).
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 confidenceAbsolute path traversal vulnerability in Micro Focus Vibe 4.0.2 and earlier allows remote authenticated attackers to download arbitrary files from the server via the viewFile endpoint by submitting specially crafted requests with absolute paths. If Guest access is enabled (disabled by default), the attack can be performed without authentication.
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<= 4.0.2CVSS 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
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/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 Micro Focus Vibe installation versionLocate the Vibe installation directory and check for version files or use the Vibe administration interface to view the product version. Common locations include the installation root folder or within the administration console under 'About' or 'System Information'.Affected if The installed version is 4.0.2 or earlier (any version <= 4.0.2)
-
Confirm the viewFile endpoint existsCheck if the viewFile endpoint is accessible on the Vibe server. This is typically found at a URL path containing '/viewFile' or similar patterns in the Vibe web application. Review the deployed web application's routing configuration or proxy settings.Affected if The viewFile endpoint is exposed and accessible via HTTP/HTTPS
-
Determine if Guest access is enabledAccess the Vibe administration console and navigate to the authentication or user access settings. Look for a 'Guest' or 'Anonymous' access configuration option. This is often found under Security, Authentication, or User Management settings.Affected if Guest access is enabled, allowing unauthenticated exploitation of the path traversal
-
Verify authentication configuration for the viewFile endpointTest the viewFile endpoint with a request that does not include valid authentication credentials. Observe whether the server accepts the request or returns an authentication error.Affected if The endpoint accepts requests without requiring valid authentication
A user is affected if Micro Focus Vibe version 4.0.2 or earlier is installed AND the viewFile endpoint is accessible, especially if Guest access is enabled or if an attacker can obtain valid authentication.
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 vendor patch when available. Until then, disable Guest access if not required, implement strict input validation and path sanitization on the viewFile endpoint to prevent traversal sequences, and restrict file system permissions to limit exposure.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-7433 — 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-7433 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