GHSA-C827-PW3M-67W7

Vulnerability from github – Published: 2026-07-08 20:25 – Updated: 2026-07-08 20:25
VLAI
Summary
DSpace: ORE resource URI does not validate scheme for non-web resources
Details

Overview

When ingesting an aggregated ORE resource by URI (using the OAI-ORE Harvester), the ORE Ingestion Crosswalk does not validate the URI scheme. This may allow for local file inclusion via malicious paths like file:///etc/passwd. This vulnerability impacts DSpace versions <= 7.6.6, 8.0 <= 8.3, 9.0 <= 9.2. The attacker MUST already have DSpace collection administrator privileges in order to perform the attack.

Expected behaviour : Only external web resources should be ingested as ORE resources, preferably from the trusted endpoint.

Impact

A remote OAI endpoint configured as a harvest source for a DSpace collection can supply malicious ORE XML that results in a local file from the DSpace server being ingested as a bitstream.

Only Collection, Community and Site Administrators can configure a collection for OAI harvest, however an attacker may use stolen credentials to escalate into local file/data disclosure, or a compromised OAI endpoint could also supply malicious XML.

Patches

The fix is included in DSpace 7.6.7, 8.4, 9.3 and 10.0. Please upgrade to one of these versions or disable the ORE Crosswalk (see below).

If users cannot upgrade immediately, it is possible to manually patch their DSpace backend. (No changes are necessary to the frontend.) A pull request exists which can be used to patch systems running DSpace 7.6.x, 8.x or 9.x. * Pull request for 9.x: https://github.com/DSpace/DSpace/pull/12541 (Downloadable patch file) * Pull request for 8.x: https://github.com/DSpace/DSpace/pull/12543 (Downloadable patch file) * Pull request for 7.x: https://github.com/DSpace/DSpace/pull/12542 (Downloadable patch file)

Apply the patch to a user's DSpace

If at all possible, we recommend disabling the ORE Crosswalk (see below) or upgrading a user's DSpace site based on the upgrade instructions. However, if they are unable to do so, they can manually apply the above patches to their DSpace backend as follows: 1. Download the appropriate patch file to the machine where DSpace backend is running 2. From the [dspace-src] folder, apply the patch, e.g. git apply [name-of-file].patch 3. Now, update the DSpace site (based loosely on the Upgrade instructions). This generally involves three steps: 1. Rebuild DSpace, e.g. mvn -U clean package (This will recompile all DSpace backend code) 2. Redeploy DSpace, e.g. ant update (This will copy all newly built code to their installation directory). Depending on their setup they also may need to copy the updated "server" webapp over to their Tomcat webapps folder. 3. Restart Tomcat (or runnable JAR)

Workarounds

  • Disable the ORE ingestion crosswalk in dspace.cfg by commenting out or removing it from the list of plugin.named.org.dspace.content.crosswalk.IngestionCrosswalk plugins:
  # Remove or comment out this line
  org.dspace.content.crosswalk.OREIngestionCrosswalk = ore, \
  • Once they have patched their site or upgraded, they may safely enable the OREIngestionCrosswalk again.

Credits

Discovered & reported by Pablo Picurelli Ortiz (@superpegaso2703), cybersecurity student at Universidad Rey Juan Carlos. Code fix developed by Kim Shepherd (@kshepherd) of The Library Code

Show details on source website

{
  "affected": [
    {
      "database_specific": {
        "last_known_affected_version_range": "\u003c= 7.6.6"
      },
      "package": {
        "ecosystem": "Maven",
        "name": "org.dspace:dspace-api"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "7.6.7"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "database_specific": {
        "last_known_affected_version_range": "\u003c= 8.3"
      },
      "package": {
        "ecosystem": "Maven",
        "name": "org.dspace:dspace-api"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "8.0-rc1"
            },
            {
              "fixed": "8.4"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "database_specific": {
        "last_known_affected_version_range": "\u003c= 9.2"
      },
      "package": {
        "ecosystem": "Maven",
        "name": "org.dspace:dspace-api"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "9.0-rc1"
            },
            {
              "fixed": "9.3"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Maven",
        "name": "org.dspace:dspace-api"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "10-rc1"
            },
            {
              "fixed": "10.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "10-rc1"
      ]
    }
  ],
  "aliases": [
    "CVE-2026-49830"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-20"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-07-08T20:25:54Z",
    "nvd_published_at": null,
    "severity": "MODERATE"
  },
  "details": "## Overview\n\nWhen ingesting an aggregated ORE resource by URI (using the [OAI-ORE Harvester](https://wiki.lyrasis.org/spaces/DSDOC9x/pages/379125906/OAI#OAI-OAI-PMH/OAI-OREHarvester(Client))), the ORE Ingestion Crosswalk does not validate the URI scheme. This may allow for local file inclusion via malicious paths like `file:///etc/passwd`. _This vulnerability impacts DSpace versions \u003c= 7.6.6, 8.0 \u003c= 8.3, 9.0 \u003c= 9.2._ The attacker MUST already have DSpace collection administrator privileges in order to perform the attack.\n\nExpected behaviour : Only external web resources should be ingested as ORE resources, preferably from the trusted endpoint.\n\n## Impact\n\nA remote OAI endpoint configured as a harvest source for a DSpace collection can supply malicious ORE XML that results in a local file from the DSpace server being ingested as a bitstream.\n\nOnly Collection, Community and Site Administrators can configure a collection for OAI harvest, however an attacker may use stolen credentials to escalate into local file/data disclosure, or a compromised OAI endpoint could also supply malicious XML.\n\n## Patches\n\nThe fix is included in DSpace 7.6.7, 8.4, 9.3 and 10.0.  Please upgrade to one of these versions or disable the ORE Crosswalk (see below).\n\nIf users cannot upgrade immediately, it is possible to manually patch their DSpace backend. (No changes are necessary to the frontend.) A pull request exists which can be used to patch systems running DSpace 7.6.x, 8.x or 9.x.\n* Pull request for 9.x: https://github.com/DSpace/DSpace/pull/12541  ([Downloadable patch file](https://github.com/DSpace/DSpace/pull/12541.patch))\n* Pull request for 8.x: https://github.com/DSpace/DSpace/pull/12543  ([Downloadable patch file](https://github.com/DSpace/DSpace/pull/12543.patch))\n* Pull request for 7.x: https://github.com/DSpace/DSpace/pull/12542  ([Downloadable patch file](https://github.com/DSpace/DSpace/pull/12542.patch))\n\n\n### Apply the patch to a user\u0027s DSpace\nIf at all possible, we recommend disabling the ORE Crosswalk (see below) or upgrading a user\u0027s DSpace site based on the upgrade instructions. However, if they are unable to do so, they can manually apply the above patches to their DSpace backend as follows:\n1. Download the appropriate patch file to the machine where DSpace backend is running\n2. From the `[dspace-src]` folder, apply the patch, e.g. `git apply [name-of-file].patch`\n3. Now, update the DSpace site (based loosely on the Upgrade instructions). This generally involves three steps:\n    1. Rebuild DSpace, e.g. `mvn -U clean package`  (This will recompile all DSpace backend code)\n    2. Redeploy DSpace, e.g. `ant update`  (This will copy all newly built code to their installation directory). Depending on their setup they also may need to copy the updated \"server\" webapp over to their Tomcat webapps folder.\n    3. Restart Tomcat (or runnable JAR)\n\n## Workarounds\n* Disable the ORE ingestion crosswalk in `dspace.cfg` by commenting out or removing it from the list of `plugin.named.org.dspace.content.crosswalk.IngestionCrosswalk` plugins:\n```\n  # Remove or comment out this line\n  org.dspace.content.crosswalk.OREIngestionCrosswalk = ore, \\\n```\n* Once they have patched their site or upgraded, they may safely enable the OREIngestionCrosswalk again.\n\n## Credits\nDiscovered \u0026 reported by Pablo Picurelli Ortiz (@superpegaso2703), cybersecurity student at Universidad Rey Juan Carlos.\nCode fix developed by Kim Shepherd (@kshepherd) of The Library Code",
  "id": "GHSA-c827-pw3m-67w7",
  "modified": "2026-07-08T20:25:54Z",
  "published": "2026-07-08T20:25:54Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/DSpace/DSpace/security/advisories/GHSA-c827-pw3m-67w7"
    },
    {
      "type": "WEB",
      "url": "https://github.com/DSpace/DSpace/pull/12541"
    },
    {
      "type": "WEB",
      "url": "https://github.com/DSpace/DSpace/pull/12542"
    },
    {
      "type": "WEB",
      "url": "https://github.com/DSpace/DSpace/pull/12543"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/DSpace/DSpace"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "DSpace: ORE resource URI does not validate scheme for non-web resources"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.