dbcve.org
Code InjectionWeakness · CWE-94

CVE-2025-0618

MEDIUM · 6.5 CVSS v3.1 Published 2025-04-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
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
A malicious third party could invoke a persistent denial of service vulnerability in FireEye EDR agent by sending a specially-crafted tamper protection event to the HX service to trigger an exception. This exception will prevent any further tamper protection events from being processed, even after a reboot of HX.

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

A persistent denial of service vulnerability exists in FireEye EDR (HX) agent where a malicious third party can send specially-crafted tamper protection events to the HX service, triggering an exception that prevents any further tamper protection events from being processed. This condition persists even after system reboot.

MitigationApply vendor-provided security update/patch for FireEye EDR (now Trellix HX) to address this vulnerability. Verify tamper protection functionality after patching.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 FireEye EDR or Trellix HX agent is installed
    Check for the HX agent service or process. On Windows, look for 'HXAGENT' service or 'HxAgent.exe' process. On Linux, check for 'hesagd' or 'hx-agent' processes. Use commands: sc query hxagent (Windows) or ps aux | grep -i hx (Linux).
    Affected if The agent is not installed or not running.
  2. Identify the installed agent version
    Query the agent for its version information. On Windows: use 'sc query hxagent' or check the file version of the HXAGENT executable in the installation directory. On Linux: run 'hesagd --version' or check the RPM/DEB package version.
    Affected if The installed version matches or falls within the vulnerable version range (compare your version to vendor release notes for CVE-2025-0618).
  3. Confirm tamper protection is enabled
    Check the HX agent configuration for tamper protection status. This may be visible in the HX console under agent policies, or via registry key (Windows) or config file (Linux) if local access is permitted. Look for tamper protection policy settings.
    Affected if Tamper protection is disabled - the vulnerability only affects environments where tamper protection is enabled.
  4. Test if tamper protection events are being processed
    Trigger a test tamper protection event or review the agent event log to confirm new tamper events are being logged and transmitted to the management console. Check the HX console for recent tamper protection events.
    Affected if No new tamper protection events appear in logs or console after normal system activity that would generate them (the vulnerability causes all tamper events to stop processing).
  5. Review system or agent logs for exceptions
    Examine the HX agent logs (typically in the agent's log directory) for exception errors related to tamper protection event processing. Look for crash or exception messages that coincide with the last recorded tamper event.
    Affected if Logs show exceptions or errors related to tamper protection processing that prevent new events from being handled.

You are affected if the FireEye EDR/Trellix HX agent is installed with a vulnerable version, tamper protection is enabled, and tamper protection events are no longer being processed or logged after a specific point in time.

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

Apply vendor-provided security update/patch for FireEye EDR (now Trellix HX) to address this vulnerability. Verify tamper protection functionality after patching.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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