CVE-2024-38456
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 · uneditedHIGH-LEIT V05.08.01.03 and HIGH-LEIT V04.25.00.00 to 4.25.01.01 for Windows from Vivavis contain an insecure file and folder permissions vulnerability in prunsrv.exe. A regular user (non-admin) can exploit the weak folder and file permissions to escalate privileges and execute arbitrary code in the context of NT AUTHORITY\SYSTEM.
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 confidenceThe HIGH-LEIT software for Windows contains weak file and folder permissions on the prunsrv.exe service executable. A non-privileged local user can modify or replace this executable to achieve code execution with SYSTEM-level privileges, effectively enabling full local privilege escalation.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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.
-
Locate prunsrv.exe on the systemSearch for prunsrv.exe using: Get-ChildItem -Path "C:\" -Recurse -Filter "prunsrv.exe" -ErrorAction SilentlyContinue. Also check common installation paths like C:\Program Files\, C:\Program Files (x86)\, or the application's installation directory.Affected if The file exists on the system (indicating HIGH-LEIT or a related Apache Commons Daemon-based service is installed)
-
Check file permissions on prunsrv.exeRight-click prunsrv.exe, go to Properties > Security tab. Click on "Advanced" to view detailed permissions. Identify which users and groups have Write or Modify permissions on the file.Affected if Any user account other than Administrators or SYSTEM has Write, Modify, or Full Control permissions on prunsrv.exe
-
Check folder permissions on the prunsrv.exe directoryRight-click the parent folder containing prunsrv.exe, go to Properties > Security tab. Click on "Advanced" to view detailed permissions. Identify which users and groups have permissions on the folder.Affected if Any user account other than Administrators or SYSTEM has Write, Modify, or Full Control permissions on the directory containing prunsrv.exe
-
Check if the service is registered and runningOpen Services console (services.msc) and search for a service using prunsrv.exe, or run: Get-Service | Where-Object {$_.Status -eq "Running"}. Check the executable path in the service properties.Affected if A Windows service is configured to run prunsrv.exe (even if stopped, the configuration exists)
-
Verify non-privileged user write accessUse icacls command: icacls "C:\path\to\prunsrv.exe" (replace with actual path). Review the output to see if Authenticated Users, Users, or specific user accounts have (F) Full, (M) Modify, or (W) Write permissions.Affected if Authenticated Users, Users group, or any non-admin user account is listed with Write or Modify permissions in the ACL
If non-privileged users have Write or Modify permissions on prunsrv.exe or its parent folder, a local attacker can replace the executable to achieve SYSTEM-level privilege escalation.
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 file and folder permissions on prunsrv.exe and its directory to only allow Administrators and SYSTEM accounts write access; remove any permissions granted to regular users or authenticated users.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-38456 — 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-38456 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