CVE-2024-36074
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 Endpoint Protector and Unify agent in the way that the EasyLock dependency is acquired from the server. An attacker with administrative access to the Endpoint Protector or Unify server can cause a client to acquire and execute a malicious file resulting in remote code execution.
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 confidenceThis is a supply-chain vulnerability in Endpoint Protector and Unify agents where the EasyLock dependency is fetched from the server without adequate integrity verification. An attacker with administrative access to the server can replace the legitimate dependency with a malicious file, which client agents will then download and execute, achieving remote code execution on all connected clients.
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 Endpoint Protector or Unify agentCheck installed software listings or service status for 'Endpoint Protector' or 'Unify' agent processesAffected if Either Endpoint Protector or Unify agent is installed on the system
-
Determine if EasyLock dependency is in useInspect client configuration files or logs for references to EasyLock, or examine the agent's loaded modules and dependenciesAffected if EasyLock is loaded or configured as a dependency for the agent
-
Verify server-side administrative access controlsReview server access logs, user accounts, and RBAC policies for the Endpoint Protector/Unify server to confirm who has administrative privilegesAffected if Multiple accounts have administrative access or weak authentication is in place on the server
-
Inspect dependency integrity verificationCheck client and server configuration for cryptographic verification settings (such as signature validation, checksum verification, or signed package policies) for downloaded dependenciesAffected if No integrity verification or signature validation is configured for EasyLock or other client-side dependencies
-
Review server dependency filesExamine the server's dependency distribution directory for EasyLock and verify file hashes or signatures against known-good values if availableAffected if Dependency files lack verifiable integrity checks or originate from an untrusted source
If Endpoint Protector or Unify agent with EasyLock is installed and dependencies are fetched without cryptographic integrity verification, the environment is vulnerable to supply-chain compromise via malicious server-side dependency replacement.
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 administrative access to the Endpoint Protector/Unify server using strong authentication and RBAC; implement cryptographic verification (e.g., signed packages) for all client-side dependencies; apply vendor patches when available.
- Consultation6.0 h
- Implementation20.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,288.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-36074 — 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-36074 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