dbcve.org
Epolicy OrchestratorApplication · Mcafee

CVE-2023-5445

MEDIUM · 5.4 CVSS v3.1 Published 2023-11-17
Fix available
A fix is available. Upgrade to 5.10.0 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
An open redirect vulnerability in ePolicy Orchestrator prior to 5.10.0 CP1 Update 2, allows a remote low privileged user to modify the URL parameter for the purpose of redirecting URL request(s) to a malicious site. This impacts the dashboard area of the user interface. A user would need to be logged into ePO to trigger this vulnerability. To exploit this the attacker must change the HTTP payload post submission, prior to it reaching the ePO server.

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

Open redirect vulnerability in ePolicy Orchestrator dashboard UI allows a logged-in low-privileged attacker to modify URL parameters in HTTP requests post-submission to redirect users to external malicious sites. The vulnerability exists in version prior to 5.10.0 CP1 Update 2 and requires server-side validation of redirect URLs.

MitigationApply ePO 5.10.0 CP1 Update 2 or later which contains the fix. Additionally, implement server-side validation of redirect parameters to ensure they point only to trusted internal domains.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Epolicy OrchestratorApplication
Affected:< 5.10.0= 5.10.0

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

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 ePolicy Orchestrator installed version
    Access the ePO server console or registry and locate the ePO version information. This is typically found in the 'About' section of the ePO console or via the ePO version file on the server.
    Affected if The installed version is 5.10.0 or any version prior to 5.10.0 (e.g., 5.9.x, 5.8.x, etc.)
  2. Confirm the installed update level
    Check whether the installation includes CP1 Update 2. This information is visible in the ePO console under the version details or in the installed patches/hotfixes list on the server.
    Affected if The installation does not have CP1 Update 2 applied, meaning it remains on base 5.10.0 or earlier.
  3. Inspect server-side redirect validation configuration
    Examine the ePO server configuration or web.xml/settings files for server-side validation of redirect URL parameters. Look for settings that validate whether redirect targets point to trusted internal domains only.
    Affected if Server-side validation of redirect URLs is not implemented, missing, or improperly configured, allowing arbitrary external URL redirection.
  4. Verify low-privileged user access to dashboard
    Log in to the ePO console with a low-privileged (non-administrator) user account and attempt to access dashboard functions that involve URL redirect parameters.
    Affected if Low-privileged users can access dashboard features where URL parameters can be modified to trigger redirects after form submission.

You are affected if your ePolicy Orchestrator version is 5.10.0 or earlier without CP1 Update 2 applied AND server-side redirect URL validation is not properly configured, allowing external URL redirects from the dashboard UI.

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
Upgrade available Upgrade to 5.10.0 or later
Fixed in 5.10.0
Interim mitigation

Apply ePO 5.10.0 CP1 Update 2 or later which contains the fix. Additionally, implement server-side validation of redirect parameters to ensure they point only to trusted internal domains.

Recommended fix Moderate confidence

5.10.0 CP1 Update 2 (or subsequent releases)

  1. Obtain ePolicy Orchestrator 5.10.0 CP1 Update 2 or later from the official Trellix/Trellix downloads portal (refer to kcm.trellix.com or your authorized distribution channel)
  2. Review the ePO upgrade documentation and release notes for 5.10.0 CP1 Update 2
  3. Create a complete backup of the ePO database and configuration files
  4. Stop all ePO services before beginning the upgrade
  5. Install ePolicy Orchestrator 5.10.0 CP1 Update 2 using the standard upgrade procedure
  6. Restart ePO services after the upgrade completes
  7. Verify the ePO console is accessible and the dashboard functions correctly
  8. Confirm the version number reflects 5.10.0 CP1 Update 2 or higher

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

Fix this in Epolicy Orchestrator Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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