dbcve.org
Code InjectionWeakness · CWE-94

CVE-2024-36075

MEDIUM · 6.5 CVSS v3.1 Published 2024-06-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
The CoSoSys Endpoint Protector through 5.9.3 and Unify agent through 7.0.6 is susceptible to an arbitrary code execution vulnerability due to the way an archive obtained from the Endpoint Protector or Unify server is extracted on the endpoint. An attacker who is able to modify the archive on the server could obtain remote code execution as an administrator on an endpoint.

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

The vulnerability is a path traversal flaw in the archive extraction routine of the CoSoSys Endpoint Protector and Unify agent clients. When the endpoint receives and extracts an archive (update or configuration package) from the server, it does not properly validate file paths within the archive, allowing specially crafted archives to write files to arbitrary locations on the filesystem. An attacker who compromises the server can modify the archive to achieve remote code execution with administrator privileges on connected endpoints.

MitigationUpdate Endpoint Protector to version 5.9.4 or later and Unify agent to version 7.0.7 or later. Until patches are applied, consider network segmentation and strict server access controls to reduce the risk of server compromise.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

CVSS:3.1/AV:N/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 if Endpoint Protector is installed
    Check for the presence of Endpoint Protector installation directories or running services. On Windows, look for 'C:\Program Files\CoSoSys\Endpoint Protector' or the 'Endpoint Protector' service. On Linux, check /opt/CoSoSys/ or similar paths.
    Affected if The product is installed and version is below 5.9.4
  2. Identify if Unify agent is installed
    Check for the presence of the Unify agent. Look for installation directories named 'Unify' or related CoSoSys client directories, and check for associated services or processes.
    Affected if The product is installed and version is below 7.0.7
  3. Determine installed Endpoint Protector version
    Query the installed version through the product's UI, check version info in the installation directory, or use system inventory tools to find the Endpoint Protector version number.
    Affected if Installed version is earlier than 5.9.4 (vulnerable)
  4. Determine installed Unify agent version
    Query the installed version through the product's UI, check version info in the installation directory, or use system inventory tools to find the Unify agent version number.
    Affected if Installed version is earlier than 7.0.7 (vulnerable)
  5. Check if automatic updates are enabled
    Examine the client configuration settings to determine if automatic download and installation of updates or configuration packages from the server is enabled. This is typically found in the client's policy or update settings.
    Affected if Auto-update is enabled and connects to a server that could serve malicious archives

You are affected if either Endpoint Protector below version 5.9.4 or Unify agent below version 7.0.7 is installed with automatic updates from the server enabled.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Endpoint Protector to version 5.9.4 or later and Unify agent to version 7.0.7 or later. Until patches are applied, consider network segmentation and strict server access controls to reduce the risk of server compromise.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-36075 — 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-36075 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