dbcve.org
Arcsight Enterprise Security ManagerApplication · Hp

CVE-2017-14356

CRITICAL · 9.8 CVSS v3.0 Published 2017-10-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
An SQL Injection vulnerability in HP ArcSight ESM and HP ArcSight ESM Express, in any 6.x version prior to 6.9.1c Patch 4 or 6.11.0 Patch 1. This vulnerability could be exploited remotely to allow SQL injection.

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 SQL injection vulnerability exists in HP ArcSight ESM and HP ArcSight ESM Express versions 6.x prior to 6.9.1c Patch 4 or 6.11.0 Patch 1. The flaw allows remote attackers to inject malicious SQL queries through unsanitized input, potentially enabling unauthorized database access, data exfiltration, or privilege escalation.

MitigationApply vendor-supplied patches 6.9.1c Patch 4 or 6.11.0 Patch 1 to the affected ArcSight ESM installations. If patching is delayed, restrict network access to the ESM management interfaces and implement WAF rules to detect SQL injection 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
Arcsight Enterprise Security ManagerApplication
Affected:= 6.0= 6.0c= 6.5= 6.5c= 6.8= 6.8c= 6.9.0c= 6.9.1c= 6.11.0
Arcsight Enterprise Security Manager ExpressApplication
Affected:= 6.0= 6.0c= 6.5= 6.5c= 6.8= 6.8c= 6.9.0c= 6.9.1c= 6.11.0

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

CVSS:3.0/AV:N/AC:L/PR:N/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 ArcSight ESM installation
    Locate the HP ArcSight ESM or ArcSight ESM Express installation directory, typically under /opt/arcsight or C:\arcsight on Windows servers
    Affected if The product is not found in expected locations, indicating it may not be installed
  2. Determine installed ArcSight ESM version
    Access the ESM console or use the arcsight command line tool with version flags (e.g., ./arcsight version or check the installer logs in the installation directory)
    Affected if The version displayed is 6.0, 6.0c, 6.5, 6.5c, 6.8, 6.8c, 6.9.0c, 6.9.1c, or 6.11.0 (any version from 6.x through 6.11.0)
  3. Verify patch level applied
    Check the patch history or installed patches through the ESM administrator console, or look for patch metadata files in the installation directory under /patch or similar
    Affected if No patches are installed, or patches prior to 6.9.1c Patch 4 or 6.11.0 Patch 1 are applied (these specific patches are required to remediate)
  4. Confirm ESM Express variant
    Determine if the installation is ArcSight ESM or ArcSight ESM Express by checking product naming in the console or installer details
    Affected if The Express variant is in use with version 6.0 through 6.11.0 without the required patches

Affected if HP ArcSight ESM or ArcSight ESM Express version 6.x (including 6.0 through 6.11.0) is installed without patches 6.9.1c Patch 4 or 6.11.0 Patch 1 applied.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied patches 6.9.1c Patch 4 or 6.11.0 Patch 1 to the affected ArcSight ESM installations. If patching is delayed, restrict network access to the ESM management interfaces and implement WAF rules to detect SQL injection patterns.

Recommended fix High confidence

6.9.1c Patch 4 or 6.11.0 Patch 1 (whichever path is supported by your licensing)

  1. 1. Identify the current installed version of Arcsight ESM or ESM Express (6.0, 6.0c, 6.5, or 6.5c)
  2. 2. Obtain the appropriate upgrade package: either upgrade to 6.9.1c with Patch 4 applied, or upgrade to 6.11.0 with Patch 1 applied
  3. 3. Download the upgrade/patch from the official Micro Focus (now owner of ArcSight) support portal or HPE software support site
  4. 4. Review the upgrade documentation and release notes for any prerequisites
  5. 5. Create a full backup of the current ESM installation and database before proceeding
  6. 6. Apply the upgrade following the documented installation procedure
  7. 7. Verify the version number post-upgrade to confirm 6.9.1c Patch 4 or 6.11.0 Patch 1 is installed
  8. 8. Test critical ESM functions to ensure normal operations
Caveat Verify licensing compatibility with Micro Focus for the target version; ESM upgrades may require corresponding connector updates and should be tested in non-production first

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

Fix this in Arcsight Enterprise Security Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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