Arcsight Enterprise Security ManagerApplication · Hp

CVE-2017-14357

MEDIUM · 6.1 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 →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 Reflected and Stored Cross-Site Scripting (XSS) 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 Reflected and Stored Cross-Site Scripting (XSS)

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 Reflected and Stored Cross-Site Scripting (XSS) vulnerability exists in HP ArcSight ESM and ArcSight ESM Express versions 6.x prior to 6.9.1c Patch 4 or 6.11.0 Patch 1. The vulnerability allows remote attackers to inject malicious scripts through unvalidated input that is reflected back to users or stored in the application.

MitigationUpgrade HP ArcSight ESM/ESM Express to version 6.9.1c Patch 4 or 6.11.0 Patch 1 or later to remediate this vulnerability.

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.0= 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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

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 the installed ArcSight product type
    Determine whether your system is running HP ArcSight Enterprise Security Manager (ESM) or ArcSight ESM Express. This can typically be confirmed through the product license, installation documentation, or the ArcSight console interface.
    Affected if The system is running either HP ArcSight ESM or ArcSight ESM Express
  2. Locate the installed version number
    Access the ArcSight console or administration interface to view the product version information. Check the 'About' or 'System Information' section within the ArcSight Manager or through the command-line interface if available.
    Affected if The displayed version matches any of the affected versions: 6.0, 6.0c, 6.5, 6.5c, 6.8, 6.8c, 6.9.0, 6.9.0c, 6.9.1c, or 6.11.0
  3. Confirm the patch level if version is 6.9.1c or 6.11.0
    If the version shows 6.9.1c or 6.11.0, verify whether the applicable patch (Patch 4 for 6.9.1c or Patch 1 for 6.11.0) has been applied. Check the patch history or system documentation for applied patches.
    Affected if Running 6.9.1c without Patch 4 or 6.11.0 without Patch 1, or any other version in the 6.x line prior to these patched versions
  4. Determine if the web interface is accessible
    Verify whether the ArcSight web interface or any web-based component is accessible to users. This includes the ArcSight Console web access or any REST/API endpoints.
    Affected if The web interface is accessible and accepts user input through forms, search fields, or URL parameters

You are affected if your installed version of HP ArcSight ESM or ESM Express is any 6.x version prior to 6.9.1c Patch 4 or 6.11.0 Patch 1, and the web interface is in use.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade HP ArcSight ESM/ESM Express to version 6.9.1c Patch 4 or 6.11.0 Patch 1 or later to remediate this vulnerability.

Fix this in Arcsight Enterprise Security Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-14357 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