JervenBolleman sparql-identifiers RegistryDao.java sql injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.9 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in JervenBolleman sparql-identifiers. This affects an unknown part of the file src/main/java/org/identifiers/db/RegistryDao.java. The manipulation leads to sql injection. This vulnerability is documented as CVE-2014-125052. There is not any exploit available. To fix this issue, it is recommended to deploy a patch.
Details
A vulnerability was found in JervenBolleman sparql-identifiers (the affected version is unknown) and classified as critical. This issue affects an unknown code of the file src/main/java/org/identifiers/db/RegistryDao.java. 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 01/06/2023 as 44bb0db91c064e305b192fc73521d1dfd25bde52. It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2014-125052. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1505 according to MITRE ATT&CK.
Applying the patch 44bb0db91c064e305b192fc73521d1dfd25bde52 is able to eliminate this problem. The bugfix is ready for download at github.com. The advisory contains the following remark:
Clean up DB code, remove some SQL injection holes.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
License
Website
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: 🔍
Physical: No
Local: No
Remote: Yes
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: PatchStatus: 🔍
0-Day Time: 🔍
Patch: 44bb0db91c064e305b192fc73521d1dfd25bde52
Timeline
01/06/2023 🔍01/06/2023 🔍
01/06/2023 🔍
01/29/2023 🔍
Sources
Product: github.comAdvisory: 44bb0db91c064e305b192fc73521d1dfd25bde52
Status: Confirmed
CVE: CVE-2014-125052 (🔍)
GCVE (CVE): GCVE-0-2014-125052
GCVE (VulDB): GCVE-100-217571
Entry
Created: 01/06/2023 21:45Updated: 01/29/2023 14:05
Changes: 01/06/2023 21:45 (41), 01/29/2023 13:58 (2), 01/29/2023 14:05 (28)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.