LiveActive security incident?Get immediate response
CVE Record

CVE-2018-25075: karsany OBridge ProcedureDao.java getAllStandaloneProcedureAndFunction sql injection

A vulnerability classified as critical has been found in karsany OBridge up to 1.3. Affected is the function getAllStandaloneProcedureAndFunction of the file obridge-main/src/main/java/org/obridge/dao/ProcedureDao.java. The manipulation leads to sql injection. The complexity of an attack is rather high. The exploitability is told to be difficult. Upgrading to version 1.4 is able to address this issue. The name of the patch is 52eca4ad05f3c292aed3178b2f58977686ffa376. It is recommended to upgrade the affected component. The identifier of this vulnerability is VDB-218376.

MediumCVSS 4.6Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2018-25075 is a SQL injection issue in karsany OBridge versions 1.0 through 1.3. The published scoring rates it medium because exploitation is difficult, requires low privileges, and appears limited to adjacent-network access. Organizations using OBridge should treat it as a targeted data-integrity and confidentiality risk and upgrade to version 1.4.

Executive priority

Prioritize remediation during the next normal security maintenance window unless OBridge is internet-exposed, handles sensitive data, or is reachable by many low-privileged users. In those cases, accelerate upgrade planning because SQL injection can affect data confidentiality, integrity, and availability.

Technical view

The flaw is in getAllStandaloneProcedureAndFunction in obridge-main/src/main/java/org/obridge/dao/ProcedureDao.java. Source data maps it to CWE-89 SQL injection with CVSS 3.1 score 4.6: AV:A/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L. The named fix is commit 52eca4ad05f3c292aed3178b2f58977686ffa376 and release v1.4.

Likely exposure

Exposure is likely limited to environments running karsany OBridge 1.0, 1.1, 1.2, or 1.3. The source bundle provides no CPEs or deployment details, so teams must confirm whether OBridge is present in applications, build files, vendor packages, or internal tooling.

Exploitation context

The CVE is not listed as KEV in the provided bundle, and no cited source claims active exploitation. VulDB characterizes attack complexity as high and exploitability as difficult, with low privileges required. Treat this as plausible but not broadly opportunistic without additional environment-specific evidence.

Researcher notes

Evidence is specific but narrow: CVE and VulDB identify the vulnerable function, affected versions, CVSS vector, and patch. The bundle does not include exploit proof, affected endpoints, CPEs, or active exploitation claims. Validation should focus on version presence and whether the fixed commit is included.

Mitigation direction

  • Upgrade karsany OBridge to version 1.4.
  • Apply the referenced patch commit if full upgrade is not immediately possible.
  • Limit OBridge access to trusted users and networks until remediated.
  • Monitor database and application logs for unusual query errors or access patterns.
  • Check upstream project guidance before deploying compensating controls.

Validation and detection

  • Inventory applications and dependencies for karsany OBridge versions 1.0 through 1.3.
  • Confirm whether ProcedureDao.java includes the referenced patch commit.
  • Verify production artifacts use OBridge 1.4 or patched code.
  • Review reachable OBridge functions against expected trust boundaries.
  • Run existing regression tests after upgrading or patching.
Prepared
Confidence
medium
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · medium confidence lookup

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 lookup
description · low confidence lookup

Database 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 lookup
cve · low confidence lookup

CVE-2018-25075 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.6 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
4.6CVSS 3.1MediumCVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L1.23.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.6Medium
CVSS 3.1 vector shape for CVE-2018-25075Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
karsanyOBridge1.0, 1.1, 1.2, 1.3Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-89 · source CWE mapping

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.