How severe is GHSA-c2p2-hgjg-9r3f?

No CVSS score has been assigned to GHSA-c2p2-hgjg-9r3f yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-c2p2-hgjg-9r3f?

GHSA-c2p2-hgjg-9r3f affects the following packages: islandora/crayfish (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-c2p2-hgjg-9r3f?

No patched version of islandora/crayfish has shipped for GHSA-c2p2-hgjg-9r3f yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-c2p2-hgjg-9r3f in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for islandora/crayfish. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-c2p2-hgjg-9r3f if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-c2p2-hgjg-9r3f?

O3 pinpoints whether GHSA-c2p2-hgjg-9r3f is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-c2p2-hgjg-9r3f actively exploited in the wild?

No public exploit code has been indexed for GHSA-c2p2-hgjg-9r3f yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-c2p2-hgjg-9r3f published, and has it been updated?

GHSA-c2p2-hgjg-9r3f was published on February 12, 2025 and was last updated on February 12, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

GHSA-c2p2-hgjg-9r3f

Crayfish Allows Remote Code Execution via hypercube X-Islandora-Args Header

Published

Feb 12, 2025

Updated

Feb 12, 2025

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Blast Radius

1 pkg affected

🐘islandora/crayfish

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

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

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`islandora/crayfish`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for islandora/crayfish. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Remediation status
No patched version of islandora/crayfish has shipped for GHSA-c2p2-hgjg-9r3f yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-c2p2-hgjg-9r3f is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-c2p2-hgjg-9r3f. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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 microservi

O3 Security · Impact-Aware SCA

Is GHSA-c2p2-hgjg-9r3f in your dependencies?

O3 detects GHSA-c2p2-hgjg-9r3f across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works