Repository navigation
com-morpheus-plugin 0.3.1 (security release)
Unofficial community plugin: not an HPE or Morpheus Data product, and not supported by HPE. See NOTICE.md.
Security release: upgrade if you use the action buttons
Affected: 0.2.0 and 0.3.0 with Enable actions turned on. The read-only tab wasn't affected. Every issue required a signed-in Morpheus user with the "Run HPE COM actions" permission; none was reachable anonymously.
Upgrade: upload com-morpheus-plugin-0.3.1.jar over the installed plugin, then reload pages that have the HPE COM tab open. Your settings are kept.
Independent security review
Before this release, the action routes, the permission model and the browser script were reviewed independently. The reviewer was a separate AI reviewer (Anthropic's Claude Fable model), working read-only from this project's source and HPE's published morpheus-plugin-core source. It wasn't shown the author's conclusions. Every finding below is fixed with tests. The same reviewer then re-reviewed the fixes, confirmed each one, and gave a go for release.
| Severity | Finding | Fix in 0.3.1 |
|---|---|---|
| High | A com-id / com-serial tag on a user's own host could aim an action at any COM server the shared GreenLake client can reach, beyond the user's tenant. |
Tags only change which server is shown. For actions, the tagged server must share at least one of the host's MAC addresses, and no other server may have any of them. |
| Medium | Cross-site request protection relied entirely on Morpheus, and an unknown request method was let through. | Action routes require POST, X-Requested-With: XMLHttpRequest and a same-origin request, on top of Morpheus's CSRF filter. |
| Medium | Markup injected anywhere in the UI could trigger an action through the page-wide script. | The script only acts inside the plugin's tab, with fixed actions and confirmations. Each tab carries a signed per-host action token that the routes require. |
| Low | Job status could report jobs without a target, and its errors revealed whether a job existed. | The job must name this host's server; one generic answer otherwise. |
| Low | Errors could show internal detail. | Errors return a reference number; details go to the Morpheus log. |
| Low | Actions had no rate limit, and job polls grew the cache. | One action per server every 30 seconds; job polls aren't cached. |
| Info | Missing host-type re-check; /caps gated on the view permission. |
Both fixed. |
Behavior changes to know
- A host matched only by a tag must agree with its hardware before actions run. Otherwise the tab explains why the buttons are off.
- One action per server every 30 seconds.
- Behind a reverse proxy that rewrites
Hostwithout sendingX-Forwarded-Host, actions are refused as "cross-origin". See Troubleshooting.
Verification
-
117 automated tests (22 new, for these fixes), run against Plugin API 1.4.1 (Morpheus 9.0) and 1.5.0 (Morpheus 9.1).
-
The jar loads, with its routes, through the plugin manager of both API versions.
-
Browser test in headless Chromium against a stand-in server:
- planted buttons outside the tab do nothing;
- a planted button with a forged token is refused;
- iLO reset always asks for confirmation;
- the real buttons work.
-
The release-time compatibility check against HPE's published plugin-core and docs is clean.
-
Verified on a real Morpheus 9.0.1 appliance (2026-10-26), through its production web front end:
Test Result The UID light button 200, job completed The same request without X-Requested-With403, "missing X-Requested-With header" The same request with the header 200, so the plugin's own check did the refusing A plain GET link to the action route 403, "POST only." The front end passed the request headers through, with no false "cross-origin" refusal. If actions are refused behind a different proxy, see the troubleshooting table and please open an issue.
Pull requests and security reports are welcome. Report security issues privately via Security → Report a vulnerability.