CVE-2017-3165 — brooklyn
MEDIUMCVE-2017-3165 is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in org.apache.brooklyn:brooklyn. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for org.apache.brooklyn:brooklyn — see the affected versions and patch details below.
Cross-site Scripting In Apache Brooklyn
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.apache.brooklyn:brooklynReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
In Apache Brooklyn before 0.10.0, the REST server is vulnerable to cross-site scripting where one authenticated user can cause scripts to run in the browser of another user authorized to access the first user's resources. This is due to improper escaping of server-side content. There is known to be a proof-of-concept exploit using this vulnerability.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.brooklyn:brooklyn | all versions | 0.10.0org.apache.brooklyn:brooklyn:0.10.0 |
Affected Products
brooklynapacheResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.brooklyn:brooklyn, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.brooklyn:brooklyn to 0.10.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-3165 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is CVE-2017-3165 in your dependencies?
Find it across Maven, including transitive dependencies.