Skip to content

Crayfish allows Remote Code Execution via Homarus Authorization header

Critical severity GitHub Reviewed Published Jan 15, 2025 in Islandora/Crayfish • Updated Jan 15, 2025

Package

composer islandora/crayfish (Composer)

Affected versions

< 4.1.0

Patched versions

4.1.0

Description

Impact

What kind of vulnerability is it? Who is impacted?

Remote code execution may be possible in web-accessible installations of Homarus in certain configurations.

Patches

Has the problem been patched? What versions should users upgrade to?

The issue has been patched in islandora/crayfish:4.1.0

Workarounds

Is there a way for users to fix or remediate the vulnerability without upgrading?

The exploit requires making a request against the Homarus's /convert endpoint; therefore, the ability to exploit is much reduced if the microservice is not directly accessible from the Internet, so: Prevent general access from the Internet from hitting Homarus.

Configure auth in Crayfish to be more strongly required, such that requests with Authorization headers that do not validate are rejected before the problematic CLI interpolation occurs.

References

Are there any links users can visit to find out more?

  • XBOW-024-071

References

@adam-vessey adam-vessey published to Islandora/Crayfish Jan 15, 2025
Published to the GitHub Advisory Database Jan 15, 2025
Reviewed Jan 15, 2025
Last updated Jan 15, 2025

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Weaknesses

CVE ID

No known CVE

GHSA ID

GHSA-mm6v-68qp-f9fw

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.