dbcve.org
Endpoint Detection And ResponseApplication · Symantec

CVE-2022-37015

CRITICAL · 9.8 CVSS v3.1 Published 2022-11-08
Fix available
A fix is available. Upgrade to 4.7.0 or later.
See remediation →
100/100
Remediation priority · Urgent
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 Detection and Response (SEDR) Appliance, prior to 4.7.0, may be susceptible to a privilege escalation vulnerability, which is a type of issue whereby an attacker may attempt to compromise the software application to gain elevated access to resources that are normally protected from an application or user.

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 · moderate confidence

A privilege escalation vulnerability exists in Symantec Endpoint Detection and Response (SEDR) Appliance versions prior to 4.7.0. The vulnerability allows an attacker to gain elevated access to resources that should normally be protected. With a CVSS score of 9.8, this represents a critical security risk requiring immediate attention.

MitigationUpgrade the SEDR Appliance to version 4.7.0 or later to remediate this vulnerability. As this is a critical-severity privilege escalation in an endpoint security product, prioritize this update in the deployment schedule.

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
Endpoint Detection And ResponseApplication
Affected:< 4.7.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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Check SEDR Appliance version through web interface
    Log into the SEDR Appliance management console and navigate to the About or System Information section, typically found under Settings, Administration, or Help menus. Locate the version number displayed there.
    Affected if The displayed version is less than 4.7.0 (for example, 4.6.x, 4.5.x, or earlier)
  2. Check SEDR Appliance version via command line
    Access the appliance through SSH or a local terminal. Use commands such as 'version', 'cat /opt/sedr/version', or 'rpm -q sedr' to retrieve the installed version number.
    Affected if The command output shows a version number lower than 4.7.0
  3. Check version from installation media or documentation
    Review any installation records, build documents, or the original deployment documentation that notes the version that was installed.
    Affected if The documented version is below 4.7.0
  4. Check version via API or administrative tool
    If your environment uses centralized management tools or APIs for SEDR, query the appliance status endpoint or use the management tool to retrieve the installed version information.
    Affected if The returned version is prior to 4.7.0

The environment is affected if the installed SEDR Appliance version is any release prior to 4.7.0, as the privilege escalation vulnerability exists in all earlier versions.

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

Upgrade the SEDR Appliance to version 4.7.0 or later to remediate this vulnerability. As this is a critical-severity privilege escalation in an endpoint security product, prioritize this update in the deployment schedule.

Recommended fix High confidence

4.7.0

  1. 1. Log in to the Broadcom Support portal at support.broadcom.com
  2. 2. Navigate to the Symantec Endpoint Detection and Response (SEDR) product area
  3. 3. Download the version 4.7.0 update package for your appliance
  4. 4. Review the upgrade documentation provided by Broadcom
  5. 5. Create a backup of the current appliance configuration
  6. 6. Apply the version 4.7.0 update following the documented upgrade procedure
  7. 7. Verify the appliance has upgraded successfully and is running version 4.7.0 or later
  8. 8. Confirm the privilege escalation vulnerability is resolved by verifying the fix is applied

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

Fix this in Endpoint Detection And Response Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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