[Snyk] Fix for 2 vulnerabilities

[Atmire-github]

Snyk has created this PR to fix 2 vulnerabilities in the maven dependencies of this project.

Snyk changed the following file(s):

• pom.xml

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score	Upgrade
	Allocation of Resources Without Limits or Throttling SNYK-JAVA-ORGECLIPSEJETTYHTTP2-12047629	721	org.apache.solr:solr-solrj: 8.11.1 -> 9.0.0 Major version upgrade No Known Exploit
	Relative Path Traversal SNYK-JAVA-ORGSPRINGFRAMEWORK-12008931	696	org.springframework.boot:spring-boot-starter-aop: 2.6.8 -> 3.4.9 org.springframework.boot:spring-boot-starter-cache: 2.6.8 -> 3.4.9 org.springframework.boot:spring-boot-starter-data-rest: 2.6.8 -> 3.4.9 org.springframework.boot:spring-boot-starter-security: 2.6.8 -> 3.4.9 org.springframework.boot:spring-boot-starter-web: 2.6.8 -> 3.4.9 Major version upgrade No Known Exploit

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Allocation of Resources Without Limits or Throttling
🦉 Relative Path Traversal

[github-actions]

This pull request has been automatically marked as stale because it has not had
activity in one year. It will be closed in 14 days if no further activity occurs.

Allowing pull requests to close as stale helps us filter out old work that is no longer
relevant and helps developers focus on reviewing current work.

All pull requests closed by this bot act like normal pull requests;
they can be searched for, commented on or reopened at any point.

If these changes are still relevant then please comment and/or rebase your PR based on the
latest DSpace code. This will remove the stale status and notify us to assign a reviewer
for your PR.