Skybox Manager Client ApplicationApplication · Skyboxsecurity

CVE-2017-14771

MEDIUM · 5.5 CVSS v3.0 Published 2017-10-03
Fix available
A fix is available. Upgrade to after 8.5.500 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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 · unedited
Skybox Manager Client Application prior to 8.5.501 is prone to an arbitrary file upload vulnerability due to insufficient input validation of user-supplied files path when uploading files via the application. During a debugger-pause state, a local authenticated attacker can upload an arbitrary file and overwrite existing files within the scope of the affected application.

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 confidence

Skybox Manager Client Application prior to version 8.5.501 contains an arbitrary file upload vulnerability stemming from insufficient input validation of user-supplied file paths. An authenticated local attacker with the ability to trigger a debugger-pause state can upload arbitrary files and overwrite existing application files due to the lack of proper path traversal and file type validation.

MitigationUpgrade to Skybox Manager Client Application version 8.5.501 or later which addresses the input validation weakness. Until patched, restrict local access and disable debugging functionality where possible.

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
Skybox Manager Client ApplicationApplication
Affected:<= 8.5.500

CVSS 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Skybox Manager Client Application version
    Open the application and navigate to Help > About, or check the Windows Programs and Features list for the installed version number. Compare against the vulnerable version range <= 8.5.500
    Affected if The installed version is 8.5.500 or lower
  2. Verify if debugging functionality is accessible
    Check if the application exposes debugging options or interfaces that can be triggered to cause a debugger-pause state. Look for debug menus, verbose logging settings, or diagnostic ports in the application configuration
    Affected if Debug functionality is enabled or accessible to authenticated users
  3. Inspect application configuration files
    Examine configuration files in the application installation directory (typically in conf or config subfolders) for settings related to file upload, debug mode, or diagnostic features
    Affected if Configuration shows debug mode or unrestricted file upload functionality is enabled
  4. Review user permissions for file upload features
    Check if the application allows authenticated local users to access file import or upload features, particularly in the context of debugger or diagnostic functions
    Affected if Authenticated users have access to file upload capabilities within debugging or diagnostic features

You are affected if Skybox Manager Client Application version is 8.5.500 or lower AND debugging functionality that enables the debugger-pause state is accessible to authenticated local users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 8.5.500
Interim mitigation

Upgrade to Skybox Manager Client Application version 8.5.501 or later which addresses the input validation weakness. Until patched, restrict local access and disable debugging functionality where possible.

Fix this in Skybox Manager Client Application Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,170
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,072.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-14771 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-14771 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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