CVE-2019-3631
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 code through specially crafted parameters. The vulnerability exists in versions prior to 11.2.0 and 10.4.0, allowing attackers to inject OS commands via user-controlled input that is not properly sanitized before being passed to system call execution.
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 McAfee ESM versionCheck the installed version through the ESM web interface (Help > About) or via the ESM smc -version command-line tool if availableAffected if Version is below 10.4.0, or between 11.0.0 and 11.2.0 (exclusive)
-
Confirm ESM web interface accessibilityDetermine if the ESM management console web interface is reachable on its configured port (typically 443 or 8443) from network locationsAffected if Web interface is exposed to untrusted networks or the internet
-
Review user authentication methodsCheck which user accounts have access to the ESM console and identify any accounts with administrative or operator privileges that can submit configuration parametersAffected if Multiple or weakly-controlled authenticated users have access to the console
-
Audit console access logsReview ESM console and system logs for suspicious command-like parameters or unexpected system calls originating from the web interfaceAffected if Logs show unusual parameter patterns or unauthorized command executions
-
Check network exposureDetermine if the ESM management interface is behind a firewall and accessible only from trusted management subnetsAffected if ESM management ports are open to broad network segments or DMZ
Your environment is affected if the installed ESM version is below 10.4.0 or falls between 11.0.0 and 11.2.0, and the management console is accessible to users who could inject malicious 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 the 10.x branch) to remediate this vulnerability. Restrict administrative access to trusted personnel and implement network segmentation to limit exposure.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-3631 — 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-3631 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