GHSA-c2p2-hgjg-9r3f: Crayfish Allows Remote Code Execution via hypercube X-Islandora-Args Header
Impact What kind of vulnerability is it? Who is impacted? Remote code execution is possible in web-accessible installations of hypercube. Patches Has the problem been patched? What versions should users upgrade to? Not yet, though no patch is neccessary if your installation of the microservices is behind a firewall. See below.
Published Feb 12, 2025
Affected packages
islandora/crayfish
- Ecosystem
- Composer (PHP)
- Affected
- <= 4.0.0
- Fixed in
- No patched version yet
- Check
composer show islandora/crayfish
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
_What kind of vulnerability is it? Who is impacted?_
Remote code execution is possible in web-accessible installations of hypercube.
Patches
_Has the problem been patched? What versions should users upgrade to?_
Not yet, though no patch is neccessary if your installation of the microservices is behind a firewall. See below.
Workarounds
_Is there a way for users to fix or remediate the vulnerability without upgrading?_
The exploit requires making a request against Hypercube's endpoints; therefore, the ability to make use of the exploit is much reduced if the microservice is not directly accessible from the Internet, so: Prevent general access from the Internet from hitting Hypercube. Furthermore, if you've used any of the official installation methods, your Crayfish will be behind a firewall and there is no work neccessary.
The webserver might be made to validate the structure of headers passed, but that would only be neccessary if you publicly exposed the endpoint. Standard security practices should be applied.
References
_Are there any links users can visit to find out more?_
- XBOW-024-074
Credited to xbow-security.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
