CVE-2016-7034: CSRF
First published: Tue Sep 06 2016(Updated: )
The dashbuilder in Red Hat JBoss BPM Suite 6.3.2 does not properly handle CSRF tokens generated during an active session and includes them in query strings, which makes easier for remote attackers to (1) bypass CSRF protection mechanisms or (2) conduct cross-site request forgery (CSRF) attacks by obtaining an old token.
Credit: secalert@redhat.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| redhat JBoss BPM suite | =6.3.2 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2016-7034?
CVE-2016-7034 is rated as a medium severity vulnerability.
How do I fix CVE-2016-7034?
To fix CVE-2016-7034, you should upgrade to Red Hat JBoss BPM Suite 6.3.3 or later releases.
What is the impact of CVE-2016-7034?
CVE-2016-7034 can allow attackers to bypass CSRF protections and conduct unauthorized actions on behalf of users.
Who is affected by CVE-2016-7034?
CVE-2016-7034 affects users of Red Hat JBoss BPM Suite version 6.3.2.
Is CVE-2016-7034 a cross-site request forgery vulnerability?
Yes, CVE-2016-7034 specifically facilitates cross-site request forgery attacks due to improper CSRF token handling.
- agent/type
- collector/redhat-bugzilla
- source/Red Hat
- alias/CVE-2016-7034
- agent/first-publish-date
- agent/severity
- agent/references
- agent/author
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/event
- agent/softwarecombine
- agent/weakness
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/redhat
- canonical/redhat jboss bpm suite
- version/redhat jboss bpm suite/6.3.2