dbcve.org
Symantec Endpoint ProtectionApplication · Broadcom

CVE-2022-37017

HIGH · 7.5 CVSS v3.1 Published 2022-12-01
Fix available
A fix is available. Upgrade to 14.3.5.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
Symantec Endpoint Protection (Windows) agent, prior to 14.3 RU6/14.3 RU5 Patch 1, may be susceptible to a Security Control Bypass vulnerability, which is a type of issue that can potentially allow a threat actor to circumvent existing security controls. This CVE applies narrowly to the Client User Interface Password protection and Policy Import/Export Password protection, if it has been enabled.

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

This is a Security Control Bypass vulnerability in Symantec Endpoint Protection (Windows) agent versions prior to 14.3 RU6 or 14.3 RU5 Patch 1. The vulnerability allows circumvention of Client User Interface Password protection and Policy Import/Export Password protection when these features are enabled, potentially allowing threat actors to bypass security controls.

MitigationUpgrade Symantec Endpoint Protection Windows agent to version 14.3 RU6 or 14.3 RU5 Patch 1 or later to resolve the vulnerability.

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
Symantec Endpoint ProtectionApplication
Affected:< 14.3.5.1

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 SEP client version
    Open the Symantec Endpoint Protection client, click Help, then About, or check the version from the main UI. Compare the version number to the affected range (versions prior to 14.3.5.1).
    Affected if Installed version is less than 14.3.5.1 (14.3 RU6 or 14.3 RU5 Patch 1)
  2. Verify Client UI Password protection status
    In the SEP client, go to Configure > Password Protection > Client User Interface Password. Check whether the password protection for accessing the client interface is enabled.
    Affected if Client User Interface Password protection is enabled on a version below 14.3.5.1
  3. Verify Policy Import/Export Password protection status
    In the SEP management console or client settings, navigate to Password Protection for Policy Import/Export. Check whether a password is required when importing or exporting policies.
    Affected if Policy Import/Export Password protection is enabled on a version below 14.3.5.1

You are affected if your installed Symantec Endpoint Protection Windows agent version is below 14.3.5.1 AND either Client UI Password protection or Policy Import/Export Password protection is enabled.

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 14.3.5.1 or later
Fixed in 14.3.5.1
Interim mitigation

Upgrade Symantec Endpoint Protection Windows agent to version 14.3 RU6 or 14.3 RU5 Patch 1 or later to resolve the vulnerability.

Recommended fix High confidence

14.3 RU6 (14.3.6) or later, or 14.3 RU5 Patch 1 (14.3.5.1)

  1. 1. Obtain the fixed version (14.3 RU6 or 14.3 RU5 Patch 1) from the Broadcom Support portal at support.broadcom.com
  2. 2. Download the Symantec Endpoint Protection installer for the fixed version
  3. 3. Verify the integrity of the downloaded installer using checksums if provided by Broadcom
  4. 4. Test the upgrade in a non-production environment first to ensure compatibility
  5. 5. Deploy the upgrade to production endpoints using your preferred deployment method (SCCM, GPO, or Symantec's built-in deployment)
  6. 6. Verify the upgrade was successful by checking the client version in the SEP management console
  7. 7. Confirm that Client User Interface Password protection and Policy Import/Export Password protection are functioning correctly after upgrade
  8. 8. Document the remediation for compliance purposes
Caveat Standard SEP upgrade precautions apply - ensure compatibility with existing infrastructure and backup policies before deployment

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

Fix this in Symantec Endpoint Protection 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 the upgrade done

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-2022-37017 — 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-2022-37017 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