dbcve.org
Hard-coded CredentialsWeakness · CWE-798

CVE-2024-4844

HIGH · 7.5 CVSS v3.1 Published 2024-05-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable 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
Hardcoded credentials vulnerability in Trellix ePolicy Orchestrator (ePO) on Premise prior to 5.10 Service Pack 1 Update 2 allows an attacker with admin privileges on the ePO server to read the contents of the orion.keystore file, allowing them to access the ePO database encryption key. This was possible through using a hard coded password for the keystore. Access Control restrictions on the file mean this would not be exploitable unless the user is the system admin for the server that ePO is running on.

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

Hardcoded credentials vulnerability in Trellix ePolicy Orchestrator allows an attacker with admin privileges on the ePO server to read the orion.keystore file contents using a known hardcoded password, exposing the ePO database encryption key.

MitigationUpgrade to ePO 5.10 Service Pack 1 Update 2 or later to remediate. Ensure strict file system access controls on the ePO server are maintained.

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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/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. Identify if Trellix ePO is installed
    Check for ePolicy Orchestrator installation by looking for the ePO installation directory (commonly at C:\Program Files\McAfee\ePolicy Orchestrator or C:\Program Files\Trellix\ePolicy Orchestrator), or look for the 'Trellix ePolicy Orchestrator' or 'McAfee ePolicy Orchestrator' service in Windows Services.
    Affected if ePolicy Orchestrator is installed on the system
  2. Determine ePO version
    Open the ePO console and navigate to Dashboard > System Information, or check the file version of the orion.jar file in the ePO installation directory (e.g., C:\Program Files\McAfee\ePolicy Orchestrator\Server\conf\orion\orion.jar).
    Affected if Version is earlier than 5.10 Service Pack 1 Update 2 (5.10.0 through 5.10.1 are all affected)
  3. Locate the orion.keystore file
    Search for the orion.keystore file in the ePO installation directory, typically found under C:\Program Files\McAfee\ePolicy Orchestrator\Server\conf\orion\ or within the conf directory structure.
    Affected if The orion.keystore file exists and is readable by the ePO service account or by users with admin privileges on the server
  4. Verify file permissions on keystore
    Right-click the orion.keystore file, go to Properties > Security, and review which users and groups have Read access to the file.
    Affected if Non-administrator service accounts or unauthorized users have read access to the orion.keystore file

Your environment is affected if Trellix ePolicy Orchestrator is installed and the version is below 5.10 Service Pack 1 Update 2, combined with the presence of the orion.keystore file that could be accessed using the hardcoded credentials.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to ePO 5.10 Service Pack 1 Update 2 or later to remediate. Ensure strict file system access controls on the ePO server are maintained.

Recommended fix High confidence

5.10 Service Pack 1 Update 2

  1. 1. Identify current ePO version by checking the ePO console or server
  2. 2. Create a full backup of the ePO database and configuration
  3. 3. Download ePO version 5.10 Service Pack 1 Update 2 or later from the Trellix download portal
  4. 4. Apply the upgrade following Trellix standard ePO upgrade procedures
  5. 5. Verify the upgrade completed successfully and ePO services are running
  6. 6. Confirm the orion.keystore file now uses a non-hardcoded password
Caveat Review Trellix release notes for 5.10 SP1 Update 2 for any configuration or compatibility changes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

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

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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