dbcve.org
CWE-250Weakness · CWE-250

CVE-2024-50590

HIGH · 7.8 CVSS v3.1 Published 2024-11-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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
Attackers with local access to the medical office computer can escalate their Windows user privileges to "NT AUTHORITY\SYSTEM" by overwriting one of two Elefant service binaries with weak permissions. The default installation directory of Elefant is "C:\Elefant1" which is writable for all users. In addition, the Elefant installer registers two Firebird database services which are running as “NT AUTHORITY\SYSTEM”.  Path: C:\Elefant1\Firebird_2\bin\fbserver.exe Path: C:\Elefant1\Firebird_2\bin\fbguard.exe Both service binaries are user writable. This means that a local attacker can rename one of the service binaries, replace the service executable with a new executable, and then restart the system. Once the system has rebooted, the new service binary is executed as "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 confidence

Local privilege escalation in Elefant CMS where attackers with standard user access can replace Firebird database service binaries (fbserver.exe or fbguard.exe) in the writable 'C:\Elefant1' directory with a malicious executable. Since these services run as NT AUTHORITY\SYSTEM, the attacker's code executes with highest privileges after a service restart or system reboot.

MitigationRestrict file permissions on 'C:\Elefant1' and its service binaries to prevent non-privileged users from writing or replacing executables. Configure services to run under a dedicated service account with minimal required privileges rather than NT AUTHORITY\SYSTEM.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Elefant CMS installation exists
    Confirm the presence of the 'C:\Elefant1' directory on the system, which is the default Elefant CMS installation path mentioned in the vulnerability summary.
    Affected if The directory 'C:\Elefant1' exists on the system.
  2. Locate Firebird service binaries
    Check if 'fbserver.exe' or 'fbguard.exe' exist within the 'C:\Elefant1' directory. These are the Firebird database service executables that can be replaced.
    Affected if The Firebird service binaries (fbserver.exe or fbguard.exe) are present in 'C:\Elefant1'.
  3. Check write permissions on C:\Elefant1 for standard users
    Use icacls or Get-Acl to inspect permissions on 'C:\Elefant1'. Verify whether standard (non-privileged) users have write, modify, or full control permissions to this directory.
    Affected if Standard user accounts have write or modify permissions to 'C:\Elefant1', allowing replacement of service binaries.
  4. Verify Firebird service configuration
    Query the Firebird service configuration using 'sc qc' or Get-Service for Firebird services. Check the BINARY_PATH_NAME to confirm it points to 'C:\Elefant1' and check the SERVICE_START_NAME to verify it runs as NT AUTHORITY\SYSTEM.
    Affected if Firebird services are configured to run from 'C:\Elefant1' as NT AUTHORITY\SYSTEM.
  5. Inspect service binary file permissions
    Use icacls or Get-Acl on 'C:\Elefant1\fbserver.exe' and 'C:\Elefant1\fbguard.exe' to verify which users can modify or replace these executables.
    Affected if Non-privileged users can modify or replace the Firebird service executable files.

A user is affected if Elefant CMS is installed with Firebird services in 'C:\Elefant1', and standard users have write access to that directory or its service binaries, allowing replacement of executables that run as SYSTEM.

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

Restrict file permissions on 'C:\Elefant1' and its service binaries to prevent non-privileged users from writing or replacing executables. Configure services to run under a dedicated service account with minimal required privileges rather than NT AUTHORITY\SYSTEM.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

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