Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐘
🐘 Packagist
Not in CISA KEV
CRITICAL severity

GHSA-m58q-qq5h-mgqq islandora/islandora

CRITICALFix: Islandora/islandora@573d687

GHSA-m58q-qq5h-mgqq is a critical-severity (CVSS 10) vulnerability in islandora/islandora. A fix is available for islandora/islandora — see the affected versions and patch details below.

Islandora 2.0 before 2.4.1 could allow any user to upload content into a repository

Published
Jul 21, 2022
Updated
Nov 28, 2024
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 28, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
🐘islandora/islandora

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

This vulnerability would allow any user, regardless of permissions, to upload content into a repository. This affects installations of Islandora core 2.0 or greater.

Patches

Upgrade immediately to the latest release of Islandora.

Workarounds

In lieu of an upgrade the following module can be leveraged that will resolve the issue until such a time an upgrade can take place.

For more information

If you have any questions or comments about this advisory:

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistislandora/islandora2.0&&< 2.4.12.4.1composer require islandora/islandora:^2.4.1

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for islandora/islandora, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update islandora/islandora to 2.4.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m58q-qq5h-mgqq is resolved across your whole dependency graph.

  3. Workarounds

    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.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-m58q-qq5h-mgqq can be triaged on real exposure rather than presence alone.

Tailored to GHSA-m58q-qq5h-mgqq. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact This vulnerability would allow any user, regardless of permissions, to upload content into a repository. This affects installations of Islandora core 2.0 or greater. ### Patches Upgrade immediately to the [latest release](https://github.com/Islandora/islandora/releases/tag/2.4.1) of Islandora. ### Workarounds In lieu of an upgrade the [following module](https://github.com/Islandora/islandora_ghsa_route_fix) can be leveraged that will resolve the issue until such a time an upgrade can take place. ### For more information If you have any questions or comments about this advisory: *
O3 Security · Impact-Aware SCA

Is GHSA-m58q-qq5h-mgqq in your dependencies?

O3 Security finds GHSA-m58q-qq5h-mgqq across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-m58q-qq5h-mgqq: islandora/islandora | O3 Security