LiveActive security incident?Get immediate response
CVE Record

CVE-2021-31837: Out of bounds write vulnerability in McAfee GetSusp

Memory corruption vulnerability in the driver file component in McAfee GetSusp prior to 4.0.0 could allow a program being investigated on the local machine to trigger a buffer overflow in GetSusp, leading to the execution of arbitrary code, potentially triggering a BSOD.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

McAfee GetSusp before 4.0.0 contains a memory corruption flaw in a driver component. A local program being examined by GetSusp could cause a buffer overflow, potentially running arbitrary code or crashing the system. Treat this as high priority where GetSusp is installed, especially on investigation workstations or response environments.

Executive priority

High priority for organizations that use McAfee GetSusp. The business risk is concentrated on local systems running the tool, but impact can include code execution and system crash during investigation workflows.

Technical view

CVE-2021-31837 is a CWE-787 out-of-bounds write in McAfee GetSusp's driver file component. CVSS 3.1 is 8.8: local attack vector, low complexity, low privileges, no user interaction, changed scope, and high confidentiality, integrity, and availability impact. The vulnerable range is described as GetSusp prior to 4.0.0.

Likely exposure

Exposure appears limited to systems running McAfee GetSusp before 4.0.0. The source bundle does not identify affected operating systems, default deployment patterns, or specific vulnerable driver names beyond the driver file component.

Exploitation context

The bundle does not report active exploitation, and CISA KEV is false. Exploitation requires local execution by a program being investigated on the machine, so this is not described as a remote internet-facing issue.

Researcher notes

Evidence is concise: CVE data, CVSS vector, CWE-787 classification, and a McAfee confirmation reference. The bundle does not provide exploit details, indicators, affected platforms, or named mitigations beyond the version boundary.

Mitigation direction

  • Identify systems with McAfee GetSusp installed.
  • Prioritize endpoints used for malware investigation or incident response.
  • Update GetSusp to version 4.0.0 or later where applicable.
  • Review McAfee advisory SB10363 for vendor-specific remediation details.
  • Remove vulnerable GetSusp installations where the tool is no longer required.

Validation and detection

  • Confirm GetSusp version on managed endpoints and investigation workstations.
  • Check asset inventory for GetSusp installations older than 4.0.0.
  • Verify remediation against McAfee advisory SB10363.
  • Review crash or endpoint telemetry for unexpected GetSusp driver failures.
  • Document exceptions where vulnerable versions cannot be updated immediately.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-787: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-31837 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H26Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2021-31837Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
McAfee,LLCMcAfee GetSuspunspecifiedListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-787 · source CWE mapping

Out-of-bounds Write

Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.