GHSA-c2p2-hgjg-9r3f json
Crayfish Allows Remote Code Execution via hypercube X-Islandora-Args Header
published last yr. modified last yr.
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
### 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
Is GHSA-c2p2-hgjg-9r3f in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | islandora/crayfish | <=4.0.0 |
no fix listed |
Classification
References
Sources
- GitHub Advisory GHSA-c2p2-hgjg-9r3f
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.