LiveActive security incident?Get immediate response
CVE Record

CVE-2016-15018: krail-jpa sql injection

A vulnerability was found in krail-jpa up to 0.9.1. It has been classified as critical. This affects an unknown part. The manipulation leads to sql injection. Upgrading to version 0.9.2 is able to address this issue. The identifier of the patch is c1e848665492e21ef6cc9be443205e36b9a1f6be. It is recommended to upgrade the affected component. The identifier VDB-218373 was assigned to this vulnerability.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2016-15018 is a SQL injection issue in krail-jpa 0.9.0 and 0.9.1. A successful attack could allow limited reading, changing, or disruption of database-backed data. The public record names version 0.9.2 as the fix, but provides little detail about the affected code path.

Executive priority

Schedule remediation in the normal vulnerability cycle, faster for systems handling sensitive data or reachable by many internal users. The business risk is real but not currently evidenced as internet-wide or actively exploited in the provided sources.

Technical view

The sources classify the weakness as CWE-89 SQL injection in an unspecified part of krail-jpa through 0.9.1. CVSS 3.1 is 5.5 with adjacent-network access, low complexity, low privileges, no user interaction, unchanged scope, and low confidentiality, integrity, and availability impact.

Likely exposure

Exposure is likely limited to applications that directly include krail-jpa 0.9.0 or 0.9.1 and expose affected database operations to low-privileged users on an adjacent network. The source bundle does not identify specific endpoints, APIs, or deployment patterns.

Exploitation context

The CVE is not listed as KEV in the provided bundle. The cited sources do not state active exploitation, publish exploit details, or identify weaponized use. Treat exploitation status as unconfirmed.

Researcher notes

Technical detail is sparse: the vulnerable part is not named in the CVE description, and the bundle does not provide exploit mechanics. The most useful artifacts are the GitHub issue, patch commit c1e848665492e21ef6cc9be443205e36b9a1f6be, and release 0.9.2.

Mitigation direction

  • Upgrade krail-jpa to version 0.9.2 or later.
  • Prioritize systems where low-privileged users can reach database-backed features.
  • Check the GitHub issue, patch, and release notes before choosing compensating controls.
  • If upgrade is delayed, limit database privileges for affected application accounts.

Validation and detection

  • Search dependency manifests and lockfiles for krail-jpa versions 0.9.0 and 0.9.1.
  • Confirm deployed artifacts no longer package vulnerable krail-jpa versions.
  • Map reachable application features that invoke krail-jpa database operations.
  • Review database logs for unusual low-privileged activity, without assuming compromise.
Prepared
Confidence
medium
Sources
7

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-2016-15018 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
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

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
6Source 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
5.5CVSS 3.1MediumCVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L2.13.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2016-15018Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:A/AC:L/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
n/akrail-jpa0.9.0, 0.9.1Listed
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.