CVE-2017-13988
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 · uneditedAn improper access control 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 unauthorized users to alter the maximum size of storage groups and enable/disable the setting for the 'follow schedule' function.
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 confidenceThis is an improper access control vulnerability in ArcSight ESM and ArcSight ESM Express (versions 6.x before 6.9.1c Patch 4 or 6.11.0 Patch 1) that allows unauthorized users to modify storage group settings—specifically the maximum size and the 'follow schedule' function—without proper authorization.
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= 6.0= 6.0c= 6.5= 6.5c= 6.8= 6.8c= 6.9.0c= 6.9.1c= 6.11.0= 6.0= 6.0c= 6.5= 6.5c= 6.8= 6.8c= 6.9.0= 6.9.1c= 6.11.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed ArcSight ESM versionLocate the version information in the ArcSight ESM console under Administration > System > General or check the installation directory for a version file. Alternatively, use the 'arcsight version' command if available.Affected if The installed version 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 before 6.9.1c Patch 4 or 6.11.0 Patch 1).
-
Confirm the product type is affectedVerify that the installation is either HP ArcSight Enterprise Security Manager or HP ArcSight Enterprise Security Manager Express, version 6.x.Affected if The product is ArcSight ESM or ArcSight ESM Express version 6.x and the version is earlier than the patched releases.
-
Locate storage group configurationAccess the ArcSight ESM console and navigate to Configuration > Storage > Storage Groups, or check the configuration database for storage group definitions.Affected if Storage groups exist in the environment and the system is running an affected version.
-
Verify unauthorized access to storage group settingsLog in with a user account that should NOT have administrative privileges for storage settings. Attempt to modify the 'Maximum Size' or 'Follow Schedule' settings for any storage group.Affected if A non-privileged user can successfully modify storage group settings without receiving an authorization error.
-
Check patch level statusReview the installed patches or hotfixes on the system. In the ArcSight console, examine the patch history under Administration > System > Patches, or check the patches directory in the installation folder.Affected if The system shows no patches applied, or shows patches earlier than Patch 4 for version 6.9.1c, or earlier than Patch 1 for version 6.11.0.
The environment is affected if ArcSight ESM or ESM Express version 6.x is installed without the 6.9.1c Patch 4 or 6.11.0 Patch 1 applied, and storage groups are configured with potential for unauthorized modification.
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 dataApply the vendor-supplied patches (6.9.1c Patch 4 or 6.11.0 Patch 1) to all affected ArcSight ESM installations. Verify that unauthorized users can no longer modify storage group settings after patching.
- Consultation3.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,416.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-13988 — 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-2017-13988 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