What is the severity of CVE-2016-8737?

CVE-2016-8737 is classified as a moderate severity cross-site request forgery (CSRF) vulnerability.

How do I fix CVE-2016-8737?

To fix CVE-2016-8737, upgrade Apache Brooklyn to version 0.10.0 or later.

Who is affected by CVE-2016-8737?

CVE-2016-8737 affects users of Apache Brooklyn versions prior to 0.10.0.

What could an attacker achieve with CVE-2016-8737?

An attacker could potentially execute unauthorized commands on the server as an authenticated user if the victim clicks a malicious link.

Is there a workaround for CVE-2016-8737?

Currently, the recommended solution is to upgrade to a secure version, as there are no known effective workarounds for CVE-2016-8737.

Vulnerability/
CVE-2016-8737

high

8.8

CWE

352

13/9/2017

17/9/2024

CVE-2016-8737: CSRF

First published: Wed Sep 13 2017(Updated: )

In Apache Brooklyn before 0.10.0, the REST server is vulnerable to cross-site request forgery (CSRF), which could permit a malicious web site to produce a link which, if clicked whilst a user is logged in to Brooklyn, would cause the server to execute the attacker's commands as the user. There is known to be a proof-of-concept exploit using this vulnerability.

Credit: security@apache.org

Affected Software	Affected Version	How to fix
Apache Brooklyn	<=0.9.0

Remedy

https://brooklyn.apache.org/community/security/CVE-2016-8737.html

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2016-8737?
CVE-2016-8737 is classified as a moderate severity cross-site request forgery (CSRF) vulnerability.
How do I fix CVE-2016-8737?
To fix CVE-2016-8737, upgrade Apache Brooklyn to version 0.10.0 or later.
Who is affected by CVE-2016-8737?
CVE-2016-8737 affects users of Apache Brooklyn versions prior to 0.10.0.
What could an attacker achieve with CVE-2016-8737?
An attacker could potentially execute unauthorized commands on the server as an authenticated user if the victim clicks a malicious link.
Is there a workaround for CVE-2016-8737?
Currently, the recommended solution is to upgrade to a secure version, as there are no known effective workarounds for CVE-2016-8737.

collector/nvd-index
agent/type
agent/softwarecombine
agent/author
agent/remedy
agent/references
agent/weakness
agent/severity
agent/description
agent/tags
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/event
agent/first-publish-date
agent/source
vendor/apache
canonical/apache brooklyn
version/apache brooklyn/0.9.0

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.