CVE-2019-3630
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 · uneditedCommand Injection vulnerability in McAfee Enterprise Security Manager (ESM) prior to 11.2.0 and prior to 10.4.0 allows authenticated user to execute arbitrary code via specially crafted parameters.
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 confidenceCommand injection vulnerability in McAfee Enterprise Security Manager (ESM) allows authenticated users to execute arbitrary OS commands by submitting specially crafted parameters. The vulnerability stems from improper input sanitization where user-supplied data is passed to system shell commands without validation.
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< 10.4.0>= 11.0.0, < 11.2.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if McAfee ESM is installedCheck for ESM installation directories (commonly at C:\Program Files\McAfee\ESM or /opt/McAfee/ESM) or look for ESM-related services using 'sc query' on Windows or 'ps aux | grep -i esm' on Linux.Affected if McAfee Enterprise Security Manager is present on the system
-
Determine the installed ESM versionLocate the ESM version information - typically found in the About section of the ESM web console, or check version files in the installation directory such as version.txt or esmversion in the ESM root folder.Affected if The installed version is < 10.4.0 OR (>= 11.0.0 AND < 11.2.0)
-
Verify ESM web interface accessibilityCheck if the ESM web administration interface is accessible by attempting to reach the default ports (typically 8443 or 443) on the ESM server - use 'netstat -an | findstr :8443' or similar to confirm the listener is active.Affected if The ESM web interface is exposed and reachable from a network where untrusted users could authenticate
-
Confirm authentication is enabledVerify that ESM user authentication is configured and active - check user accounts in the ESM console or review authentication configuration files in the ESM config directory.Affected if User authentication is enabled (which is required for the command injection to be exploitable)
A user is affected if McAfee ESM is installed with a version less than 10.4.0, or version 11.0.0 through 11.1.x, and the ESM web interface is accessible to authenticated users who could submit crafted parameters.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor data10.4.011.2.0
Upgrade McAfee ESM to version 11.2.0 or later (or 10.4.0 or later for older branches). Additionally, limit ESM administrative access to trusted personnel only and implement network segmentation to reduce attack surface.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-3630 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-3630 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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