# CVE-2022-4963: Folio Spring Module Core Schema Name HibernateSchemaService.java dropSchema sql injection


- **Severity:** Medium 5.5 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 20 Mar 2024
- **Updated:** 20 Aug 2024
- **Also known as:** GHSA-4h5h-p23f-hjqf

## What is CVE-2022-4963?

CVE-2022-4963 is a medium-severity vulnerability in Folio Spring Module Core, published on 20 Mar 2024. 

### Official description

A vulnerability was found in Folio Spring Module Core up to 1.1.5. It has been rated as critical. Affected by this issue is the function dropSchema of the file tenant/src/main/java/org/folio/spring/tenant/hibernate/HibernateSchemaService.java of the component Schema Name Handler. The manipulation leads to sql injection. Upgrading to version 2.0.0 is able to address this issue. The name of the patch is d374a5f77e6b58e36f0e0e4419be18b95edcd7ff. It is recommended to upgrade the affected component. The identifier of this vulnerability is VDB-257516.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2022-4963?

2 open source packages ship an affected version, including org.folio:spring-module-core. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.folio:spring-module-core` | Maven | All versions | 2.0.0 |
| `org.folio:spring-module-core` | Maven | All versions | 2.0.0 |

Products: Folio Spring Module Core.

## How do I fix CVE-2022-4963?

Upgrade org.folio:spring-module-core to 2.0.0 or later.

## Is CVE-2022-4963 being exploited?

There is no known exploitation of CVE-2022-4963 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-4963 and fix it if it is affected.

What it is: CVE-2022-4963 is a medium-severity vulnerability in Folio Spring Module Core, published on 20 Mar 2024. 
Exploitation: There is no known exploitation of CVE-2022-4963 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.folio:spring-module-core (Maven): affected all versions; fixed in 2.0.0
- org.folio:spring-module-core (Maven): affected all versions; fixed in 2.0.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-4963/ (Markdown: https://insights.sbomify.com/CVE-2022-4963/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-4963
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-4963
- OSV: https://osv.dev/vulnerability/CVE-2022-4963

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-4963/
Summaries are generated and may contain mistakes; the official description above is the record.