CVE-2019-11657
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 · uneditedCross-Site Request Forgery vulnerability in all Micro Focus ArcSight Logger affecting all product versions below version 7.0. The vulnerability could be exploited to perform CSRF attack.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in Micro Focus ArcSight Logger allows attackers to induce authenticated users to perform unintended actions. The vulnerability exists in all product versions below 7.0, potentially enabling malicious requests to be executed through the victim's authenticated session.
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.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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Verify ArcSight Logger installationIdentify if Micro Focus ArcSight Logger is installed on the system by checking for the installation directory (commonly under /opt/arcsight/logger or C:\arcsight\logger on Windows) or by querying running processes for 'arcsight' or 'logger' related services.Affected if ArcSight Logger is found to be installed on the system
-
Determine installed versionLocate the version information in the Logger installation, typically found in a version file within the installation directory, or by accessing the web interface login page which often displays the version, or by running: 'sudo /opt/arcsight/logger/current/bin/arcsight loggeradmin -a version' if available.Affected if The detected version is below 7.0 (e.g., 6.x, 5.x, etc.)
-
Confirm web interface is accessibleVerify the ArcSight Logger web interface is enabled and reachable by attempting to access the management URL (default ports 443 or 8443) or checking the configuration file for web interface enablement settings.Affected if The web interface is enabled and accessible to users or attackers on the network
-
Check for active authenticated sessionsReview session management configuration or active user sessions to determine if authenticated sessions are in use, as CSRF exploits require authenticated users to be logged in when the malicious request is triggered.Affected if Users can authenticate to the web interface and maintain active sessions
If ArcSight Logger is installed with a version below 7.0 AND the web interface is enabled allowing authenticated sessions, the environment is vulnerable to CVE-2019-11657 CSRF attacks.
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.0
Upgrade ArcSight Logger to version 7.0 or later to obtain the vendor patch; until then, consider disabling the web interface or implementing SameSite cookie attributes as compensating controls.
- 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-11657 — 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-11657 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