Security readout for executives and security teams
Plain-English summary
This is a SQL injection issue in JervenBolleman sparql-identifiers. The public sources say the affected code is RegistryDao.java and name a fixing commit, but they do not identify affected versions. The business risk is moderate because exploitation requires adjacent access and privileges, with low confidentiality, integrity, and availability impact.
Executive priority
Treat as a targeted internal-application remediation item, not an internet-wide emergency based on available evidence. Prioritize confirmation of use and patch status because affected versions are not published.
Technical view
CVE-2014-125052 is a CWE-89 SQL injection in src/main/java/org/identifiers/db/RegistryDao.java. CVSS 3.1 is 5.5: AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L. Sources identify patch commit 44bb0db91c064e305b192fc73521d1dfd25bde52, but version scope is not provided.
Likely exposure
Exposure appears limited to environments running JervenBolleman sparql-identifiers, especially where the relevant application function is reachable from adjacent or internal networks. Public sources do not provide affected version ranges, package identifiers, or deployment prevalence.
Exploitation context
The source bundle does not show CISA KEV listing or any cited evidence of active exploitation. The CVSS vector indicates an attacker needs adjacent access and low privileges, with no user interaction required. Public detail is sparse beyond the affected file and patch reference.
Researcher notes
Evidence is thin: VulDB and CVE metadata identify SQL injection in RegistryDao.java and a patch commit, but not affected versions or exploit activity. Avoid assuming broader products or fixed release numbers without vendor confirmation.
Mitigation direction
- Inventory applications using JervenBolleman sparql-identifiers.
- Apply commit 44bb0db91c064e305b192fc73521d1dfd25bde52 or a vendor release containing it.
- Restrict reachable application paths to trusted internal networks until patched.
- Review database account privileges used by the application.
- Monitor CVE and vendor sources for affected-version clarification.
Validation and detection
- Confirm deployed source includes the named patch commit.
- Check whether RegistryDao.java exists in deployed or vendored code.
- Map services exposing sparql-identifiers functionality to adjacent networks.
- Review dependency manifests for JervenBolleman sparql-identifiers usage.
- Confirm tests cover database query handling around RegistryDao.java.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2014-125052 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L2.13.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.5MediumVector: CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
Source materials
- CVE List V5 sourceCVE List V5
- https://vuldb.com/?id.217571CVE reference · vdb-entry, technical-description
- https://vuldb.com/?ctiid.217571CVE reference · signature, permissions-required
- https://github.com/JervenBolleman/sparql-identifiers/commit/44bb0db91c064e305b192fc73521d1dfd25bde52CVE reference · patch
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.