CVE-2019-11974
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 · uneditedA SQL injection code execution vulnerability was identified in HPE Intelligent Management Center (IMC) PLAT earlier than version 7.3 E0506P09.
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 confidenceSQL injection vulnerability in HPE Intelligent Management Center (IMC) PLAT allows remote attackers to execute arbitrary code via specially crafted SQL queries. The flaw exists in versions earlier than 7.3 E0506P09, where user-supplied input is not properly validated before being used in SQL statements.
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< 7.3= 7.3CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/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 HPE IMC installation locationLocate the HPE IMC installation directory. On Windows, check Program Files\Hewlett Packard Enterprise\IMC or C:\hp\imc. On Linux, check /opt/hp/imc or /usr/local/hp/imc. Look for version info in the installation root or a 'version' file.Affected if Installation directory cannot be found or IMC is not installed (not affected).
-
Retrieve installed IMC PLAT versionExamine the version file, About page in the IMC web console, or check the imcver.txt / version.ini file in the installation directory. Record the full version string including any build or patch numbers (e.g., 7.3 E0504).Affected if Unable to retrieve version information from standard locations.
-
Compare version against vulnerable rangeCompare the installed version to the affected range: versions < 7.3 or exactly version 7.3 (any build before E0506P09). Note that versions 7.3 E0506P09 and later are NOT vulnerable. The format typically appears as '7.3' or '7.3 Exxx' where xxx indicates the specific build.Affected if Installed version is 7.3 (any build) or any version below 7.3 (e.g., 7.2, 7.1, 7.0).
-
Verify PLAT component is accessibleConfirm the IMC PLAT web interface is accessible and exposed. Check if the IMC platform web portal (default ports 8080 or 8443) is running and reachable. The SQL injection affects the PLAT component regardless of other modules.Affected if PLAT web interface is exposed and version check in step 3 shows vulnerable version.
A system is affected if HPE IMC PLAT is installed and the installed version is any 7.3 version or any version earlier than 7.3, since the vulnerability exists in those versions before the E0506P09 patch.
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 data7.3
Upgrade HPE IMC PLAT to version 7.3 E0506P09 or later to remediate this vulnerability. Apply the patch following HPE's upgrade procedures.
- 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-11974 — 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-11974 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