Folio Spring Module Core up to 1.1.5 Schema Name HibernateSchemaService.java dropSchema sql injection
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
6.9 | $0-$5k | 0.05 |
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 with an unknown input leads to a sql injection vulnerability. Using CWE to declare the problem leads to CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Impacted is confidentiality, integrity, and availability.
The weakness was released 11/21/2022 as FOLIO-3645. The advisory is shared for download at github.com. This vulnerability is handled as CVE-2022-4963. The exploitation is known to be easy. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1505.
Upgrading to version 2.0.0 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch d374a5f77e6b58e36f0e0e4419be18b95edcd7ff is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version. A possible mitigation has been published immediately after the disclosure of the vulnerability. The advisory contains the following remark:
SELECT EXISTS now uses a prepared statement.
PostgreSQL doesn't support a prepared statement for CREATE SCHEMA and DROP SCHEMA. Instead we validate the schema name before use to mitigate any SQL injection attack.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.9VulDB Meta Temp Score: 6.9
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CNA Base Score: 5.5
CNA Vector (VulDB): 🔍
CVSSv2
AV | AC | Au | C | I | A |
---|---|---|---|---|---|
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
---|---|---|---|---|---|
unlock | unlock | unlock | unlock | unlock | unlock |
unlock | unlock | unlock | unlock | unlock | unlock |
unlock | unlock | unlock | unlock | unlock | unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Sql injectionCWE: CWE-89 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Local: No
Remote: Partially
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
0-Day | unlock | unlock | unlock | unlock |
---|---|---|---|---|
Today | unlock | unlock | unlock | unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Upgrade: Spring Module Core 2.0.0
Patch: d374a5f77e6b58e36f0e0e4419be18b95edcd7ff
Timeline
11/21/2022 🔍11/21/2022 🔍
01/11/2024 🔍
03/20/2024 🔍
03/05/2025 🔍
Sources
Advisory: FOLIO-3645Status: Confirmed
CVE: CVE-2022-4963 (🔍)
GCVE (CVE): GCVE-0-2022-4963
GCVE (VulDB): GCVE-100-257516
Entry
Created: 03/20/2024 07:13 PMUpdated: 03/05/2025 08:41 PM
Changes: 03/20/2024 07:13 PM (61), 05/03/2024 06:28 AM (2), 05/03/2024 06:40 AM (18), 03/05/2025 08:41 PM (20)
Complete: 🔍
Cache ID: 18:540:40
No comments yet. Languages: en.
Please log in to comment.