dbcve.org
AgentApplication · Mcafee

CVE-2022-1258

HIGH · 7.2 CVSS v3.1 Published 2022-04-14
Fix available
A fix is available. Upgrade to 5.7.6 or later.
See remediation →
78/100
Remediation priority · High
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 blind SQL injection vulnerability in the ePolicy Orchestrator (ePO) extension of MA prior to 5.7.6 can be exploited by an authenticated administrator on ePO to perform arbitrary SQL queries in the back-end database, potentially leading to command execution on the 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

A blind SQL injection vulnerability exists in the ePolicy Orchestrator (ePO) extension of McAfee Agent (MA) versions prior to 5.7.6. An authenticated administrator on ePO can craft malicious SQL queries through the extension interface, potentially escalating to operating system command execution on the underlying server.

MitigationUpgrade the McAfee Agent ePO extension to version 5.7.6 or later to remediate this vulnerability. Additionally, restrict ePO administrative access to trusted personnel and monitor for unusual SQL query patterns.

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
AgentApplication
Affected:< 5.7.6

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

CVSS:3.1/AV:N/AC:L/PR:H/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. Identify McAfee Agent installation
    Locate McAfee Agent on the system - typically found in Program Files/McAfee or via system inventory tools. On Windows, check 'Programs and Features' or use 'wmic product get name,version'. On Linux, check /opt/McAfee/ or use rpm/dpkg queries.
    Affected if McAfee Agent is installed on the system
  2. Determine the installed McAfee Agent version
    Use the appropriate command for your platform: Windows - 'wmic product where "name like 'McAfee Agent%'" get version' or check the agent UI. Linux - 'rpm -q ma' or '/opt/McAfee/agent/bin/cmdagent -p'. MacOS - 'ls /Library/McAfee/agent/' and check version info.
    Affected if The version returned is lower than 5.7.6 (e.g., 5.7.5, 5.6.x, etc.)
  3. Confirm ePO extension is in use
    Check if the system is managed through ePolicy Orchestrator by looking for ePO server communication, checking ePO console for managed agents, or verifying ePO-related configuration files/services exist on the agent.
    Affected if The agent is registered with or managed by an ePO server
  4. Verify administrative ePO access
    Review ePO console access logs and user accounts to determine if untrusted or unauthorized administrator accounts exist, since exploitation requires an authenticated ePO administrator.
    Affected if Untrusted or compromised accounts have ePO administrator privileges

A system is affected if McAfee Agent version is below 5.7.6 AND the agent is managed through ePO with an authenticated administrator account present.

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.7.6 or later
Fixed in 5.7.6
Interim mitigation

Upgrade the McAfee Agent ePO extension to version 5.7.6 or later to remediate this vulnerability. Additionally, restrict ePO administrative access to trusted personnel and monitor for unusual SQL query patterns.

Recommended fix High confidence

5.7.6

  1. 1. Download the McAfee Agent (MA) version 5.7.6 or later from the McAfee KnowledgeBase (kc.mcafee.com) or your McAfee product download portal.
  2. 2. Log in to the ePolicy Orchestrator (ePO) console as an administrator.
  3. 3. Navigate to the Software Manager or Repository management section.
  4. 4. Upload or import the MA 5.7.6 agent package to the ePO repository.
  5. 5. Create a new task or modify an existing deployment task to push the updated agent to managed systems.
  6. 6. Deploy the updated agent to all affected systems using the ePO deployment functionality.
  7. 7. Verify the agent version has been successfully updated to 5.7.6 or later on all managed systems.
  8. 8. Confirm the ePO console shows the agents reporting the correct version.
Caveat Standard minor version upgrade; test in non-production environment first to ensure compatibility with existing policies and infrastructure.

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

Fix this in Agent Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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