CVE-2024-23847
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 · uneditedIncorrect default permissions issue exists in Unifier and Unifier Cast. If this vulnerability is exploited, arbitrary code may be executed with LocalSystem privilege. As a result, a malicious program may be installed, data may be altered or deleted.
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 confidenceIncorrect default permissions in Unifier and Unifier Cast allow arbitrary code execution with LocalSystem privileges. The vulnerability stems from improper permission configuration on the application or its components, enabling a local attacker to potentially install malicious programs or modify/delete data.
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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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.
-
Detect Unifier installationSearch for Unifier or Unifier Cast installation directories. Common locations include C:\Program Files\Unifier or C:\Program Files (x86)\Unifier. Also check for Unifier Cast in similar paths. Use commands like dir /s /b "C:\Program Files\*Unifier*" or check Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for entries containing 'Unifier'.Affected if Unifier or Unifier Cast software is found installed on the system
-
Check file system permissions on application directoryReview permissions on the detected Unifier installation folder. Use icacls command on the main application directory (e.g., icacls "C:\Program Files\Unifier"). Verify that non-admin users do not have Full Control or Modify permissions. Check for Everyone, Users, or Authenticated Users with excessive permissions.Affected if Users other than Administrators or SYSTEM have Full Control or Modify permissions on the application directory or its subdirectories
-
Inspect service configurationCheck if Unifier runs as a Windows service. Run sc queryex type= service state= all | findstr /i "Unifier" to enumerate Unifier services. Then use sc qc <service_name> to query the service configuration and check the binary path. Use icacls on the service executable to verify permissions.Affected if Unifier runs as a Windows service with LocalSystem privileges and the service executable or configuration files have weak permissions
-
Check for executable file permissionsIdentify all .exe and .dll files within the Unifier installation directory. Use icacls on key executables (e.g., icacls "C:\Program Files\Unifier\*.exe") to review who can read, write, or execute these files. Look for writable locations that could be replaced with malicious code.Affected if Non-privileged users have Write or Modify access to executable files within the Unifier installation directory
The environment is affected if Unifier or Unifier Cast is installed and either the application directory or its executables have overly permissive file system ACLs allowing non-admin users to modify or execute code with elevated (LocalSystem) privileges.
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 dataApply vendor-supplied patches or security updates that correct the default permission settings. If no patch available, manually review and restrict file system and service permissions to follow least-privilege principles.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2024-23847 — 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-23847 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