CVE-2015-1997
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 (CSRF) vulnerability in IBM Security QRadar Vulnerability Manager 7.2.x before 7.2.5 Patch 5 allows remote attackers to hijack the authentication of arbitrary users for requests that insert XSS sequences.
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 · moderate confidenceCSRF vulnerability in IBM Security QRadar Vulnerability Manager allows remote attackers to forge requests that can inject XSS sequences by hijacking user authentication. The flaw exists in versions 7.2.x before 7.2.5 Patch 5, enabling attackers to perform actions on behalf of authenticated users.
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.2.0= 7.2.1= 7.2.2= 7.2.3= 7.2.4= 7.2.5CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
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 if IBM QRadar Vulnerability Manager is installedCheck for the presence of QVM or Qradar Incident Forensics components in your environment. Look for service processes named 'qvm' or 'forensics' or check the installation directory /opt/qradar/ for QVM-related folders.Affected if The product is IBM Security QRadar Vulnerability Manager or Qradar Incident Forensics
-
Determine the installed version of QVMRun the command 'rpm -q qvm' or check the version file in /opt/qradar/webui/etc/ if available. Alternatively, access the web UI and check Help > About for the version number.Affected if The installed version is 7.2.0, 7.2.1, 7.2.2, 7.2.3, 7.2.4, or 7.2.5 (any version in the 7.2.x line up to and including 7.2.5)
-
Check if the web interface is accessibleVerify if the QVM web console is exposed to network access. Check firewall rules and theListenAddress in /opt/qradar/webui/conf/httpd.conf to determine if the administrative interface is reachable.Affected if The QVM web interface is accessible from network segments where untrusted users could initiate CSRF attacks
-
Confirm the patch levelExamine the installed patches by running 'rpm -qa | grep qvm-patch' or checking the patch history in the QVM console under Maintenance > Patch Management.Affected if Patch 5 for version 7.2.5 has not been applied, leaving the system at a version before 7.2.5 Patch 5
You are affected if IBM Security QRadar Vulnerability Manager or Qradar Incident Forensics version 7.2.0 through 7.2.5 is installed and the web interface is accessible without the 7.2.5 Patch 5 applied.
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 IBM QVM 7.2.5 Patch 5 or later. Additionally, implement anti-CSRF tokens and SameSite cookie attributes as defense-in-depth measures.
- Consultation4.0 h
- Implementation6.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,080.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-1997 — 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-2015-1997 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