dbcve.org
Skysea Client ViewApplication · Skygroup

CVE-2024-21805

HIGH · 7.8 CVSS v3.1 Published 2024-03-12
Fix available
A fix is available. Upgrade to 19.300.09h or later.
See remediation →
81/100
Remediation priority · High
No privileges

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
Improper access control vulnerability exists in the specific folder of SKYSEA Client View versions from Ver.16.100 prior to Ver.19.2. If this vulnerability is exploited, an arbitrary file may be placed in the specific folder by a user who can log in to the PC where the product's Windows client is installed. In case the file is a specially crafted DLL file, arbitrary code may be executed with SYSTEM privilege.

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 confidence

Improper access control in SKYSEA Client View versions prior to 19.2 allows authenticated local users to place arbitrary files in a specific folder. When the application loads a specially crafted DLL from this folder, it executes with SYSTEM privileges, enabling local privilege escalation.

MitigationUpdate SKYSEA Client View to Ver.19.2 or later to remediate the improper access control vulnerability.

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
Skysea Client ViewApplication
Affected:>= 16.100.06f, < 19.300.09h

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

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 checks

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

  1. Identify installed SKYSEA Client View version
    Use the system's installed programs list, registry, or product-specific command to retrieve the SKYSEA Client View version number (e.g., via Add/Remove Programs, HKLM\Software\SKYSEA\ClientView, or vendor diagnostic tool)
    Affected if The version number is greater than or equal to 16.100.06f AND less than 19.300.09h
  2. Verify authenticated local user access
    Confirm the user has authenticated local access to the Windows system where SKYSEA Client View is installed
    Affected if The user has valid local credentials to log into the system where the vulnerable software is running
  3. Confirm application is running with elevated privileges
    Verify that the SKYSEA Client View service or process is running under the SYSTEM account or another privileged user account
    Affected if The SKYSEA Client View process runs with higher privileges than the authenticated local user, enabling the privilege escalation path
  4. Check for the vulnerable DLL loading behavior
    Examine the application behavior to confirm it loads DLLs from a user-writable folder that can be exploited
    Affected if SKYSEA Client View loads DLLs from a folder where an authenticated local user can write arbitrary files, allowing DLL hijacking to achieve SYSTEM-level code execution

A user is affected if SKYSEA Client View version is between 16.100.06f and 19.300.09h (exclusive), the application runs with elevated privileges, and an authenticated local user can place files in the specific folder the application uses for DLL loading.

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.

dbcve · scoped
Upgrade available Upgrade to 19.300.09h or later
Fixed in 19.300.09h
Interim mitigation

Update SKYSEA Client View to Ver.19.2 or later to remediate the improper access control vulnerability.

Recommended fix High confidence

19.300.09h or later

  1. 1. Obtain the latest version of Skysea Client View (version 19.300.09h or later) from the official vendor website or your licensed download channel.
  2. 2. Ensure you have a complete backup of your current configuration and important data.
  3. 3. Stop any running Skysea Client View services on the affected Windows client machines.
  4. 4. Run the installer for version 19.300.09h or later with appropriate administrative privileges.
  5. 5. Follow the vendor's installation wizard to complete the upgrade.
  6. 6. Verify the installed version matches 19.300.09h or later.
  7. 7. Restart the Skysea Client View services and confirm normal operation.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Skysea Client View Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-21805 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2024-21805 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