CVE-2024-36073
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 · uneditedNetwrix CoSoSys Endpoint Protector through 5.9.3 and CoSoSys Unify through 7.0.6 contain a remote code execution vulnerability in the shadowing component of the Endpoint Protector and Unify agent which allows an attacker with administrative access to the Endpoint Protector or Unify server to overwrite sensitive configuration and subsequently execute system commands with SYSTEM/root privileges on a chosen client 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 · high confidenceRemote code execution vulnerability in the shadowing component of Netwrix CoSoSys Endpoint Protector (through 5.9.3) and CoSoSys Unify (through 7.0.6). An attacker with administrative access to the server can overwrite sensitive configuration files, enabling arbitrary system command execution with SYSTEM/root privileges on targeted client endpoints.
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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed productCheck system for Netwrix CoSoSys Endpoint Protector or CoSoSys Unify installation. Look for service processes, installed directories, or check installed programs list.Affected if The system has Endpoint Protector version 5.9.3 or lower, or Unify version 7.0.6 or lower installed.
-
Verify product versionLocate the product version information in the installation directory, registry, or application interface. Compare against the affected ranges: Endpoint Protector through 5.9.3, Unify through 7.0.6.Affected if The installed version is 5.9.3 or lower for Endpoint Protector, or 7.0.6 or lower for Unify.
-
Confirm shadowing component is activeCheck if the shadowing feature is enabled in the product configuration. Look for shadowing-related services, scheduled tasks, or configuration settings.Affected if Shadowing component is enabled and configured on the server.
-
Inspect configuration file permissionsReview permissions on sensitive configuration files within the product installation directory. Check if the configuration files are writable by low-privilege accounts or if unauthorized modifications have occurred.Affected if Configuration files can be overwritten by the compromised administrative account or show recent unauthorized changes.
You are affected if Endpoint Protector 5.9.3 or lower or Unify 7.0.6 or lower is installed with the shadowing component enabled and an attacker with administrative server access could overwrite configuration files to execute commands on client endpoints.
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 dataRestrict and audit administrative access to the Endpoint Protector/Unify servers, monitor for unauthorized configuration changes, and apply vendor-supplied patches when released.
- Consultation5.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA5.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,416.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-36073 — 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-2024-36073 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