dbcve.org
Arcsight Enterprise Security ManagerApplication · Hp

CVE-2017-13990

MEDIUM · 5.3 CVSS v3.0 Published 2017-09-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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 information leakage vulnerability in ArcSight ESM and ArcSight ESM Express, any 6.x version prior to 6.9.1c Patch 4 or 6.11.0 Patch 1, allows disclosure of Apache Tomcat application server version.

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

This is an information disclosure vulnerability in ArcSight ESM and ArcSight ESM Express where the application reveals the version of the underlying Apache Tomcat application server through some exposed endpoint or error message. An attacker can use this Tomcat version information for fingerprinting and identifying known vulnerabilities in that specific Tomcat version.

MitigationApply the vendor-supplied patches (6.9.1c Patch 4 or 6.11.0 Patch 1) to update the ArcSight ESM installation to a fixed version.

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.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
Low
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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. Verify ArcSight ESM installation
    Locate the ArcSight ESM installation directory (commonly under /opt/arcsight or C:\ArcSight) or check for running arcsight services using system commands like 'ps aux | grep arcsight' or 'Get-Service | Where-Object {$_.DisplayName -like "*arcsight*"}'
    Affected if ArcSight ESM or ESM Express is not installed on the system
  2. Determine installed ArcSight version
    Check for version information in the ArcSight installation. Common locations: look for a 'version.properties' or 'version.txt' file in the installation root, or check the 'arcsight_version' file under the installation directory. On Windows, also check the Windows Registry under HKLM\SOFTWARE\ArcSight or examine the installer logs.
    Affected if The installed version cannot be determined or is not one of: 6.0, 6.0c, 6.5, 6.5c, 6.8, 6.8c, 6.9.0c, 6.9.1c, 6.11.0 (for ESM) or 6.0, 6.0c, 6.5, 6.5c, 6.8, 6.8c, 6.9.0, 6.9.1c, 6.11.0 (for ESM Express)
  3. Compare version to affected range
    If you obtained a version number in step 2, compare it exactly to the affected versions list. The vulnerability affects exact version matches (denoted by '=' in the advisory).
    Affected if The installed version matches exactly one of the affected versions listed in the CVE (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)
  4. Inspect HTTP responses for Tomcat version disclosure
    If ArcSight ESM is accessible via web interface, send HTTP requests to common endpoints (such as the login page, /admin, or any error-triggering endpoint) and inspect the Server header or error message bodies for Apache Tomcat version strings (e.g., 'Apache Tomcat/7.x' or 'Apache Tomcat/8.x')
    Affected if The HTTP response headers or error pages reveal a specific Apache Tomcat version number

The environment is affected if ArcSight ESM or ESM Express version matches exactly one of the listed 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) and HTTP responses expose Tomcat version information.

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

Apply the vendor-supplied patches (6.9.1c Patch 4 or 6.11.0 Patch 1) to update the ArcSight ESM installation to a fixed version.

Fix this in Arcsight Enterprise Security Manager Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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