LiveActive security incident?Get immediate response
CVE Record

CVE-2019-14900: A flaw was found in Hibernate ORM in versions before 5.3.18, 5.4.18 and 5.5.0.Beta1.

A flaw was found in Hibernate ORM in versions before 5.3.18, 5.4.18 and 5.5.0.Beta1. A SQL injection in the implementation of the JPA Criteria API can permit unsanitized literals when a literal is used in the SELECT or GROUP BY parts of the query. This flaw could allow an attacker to access unauthorized information or possibly conduct further attacks.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2019-14900 is a SQL injection flaw in Hibernate ORM. Affected applications may let unsafe values reach generated database queries through specific JPA Criteria API usage, potentially exposing unauthorized data or enabling follow-on attacks.

Executive priority

Treat this as dependency remediation with conditional urgency. Prioritize systems handling sensitive data, internet-facing Java services, and products confirmed to include vulnerable Hibernate ORM versions.

Technical view

Hibernate ORM before 5.3.18, 5.4.18, and 5.5.0.Beta1 can permit unsanitized literals in JPA Criteria API SELECT or GROUP BY query parts. Impact depends on application query construction and whether attacker-controlled input reaches those literals.

Likely exposure

Exposure is most likely in Java applications bundling affected Hibernate ORM versions and using JPA Criteria API paths involving literals in SELECT or GROUP BY. Indirect exposure may exist through products or frameworks that package vulnerable Hibernate versions.

Exploitation context

The provided sources do not report active exploitation, and KEV status is false. Practical exploitability depends on a reachable application path that passes unsafe external input into the vulnerable Criteria API query pattern.

Researcher notes

The record lacks CVSS, CWE, and detailed exploitation evidence. Analysis should focus on version confirmation, vulnerable Criteria API usage, and reachability from untrusted input rather than assuming all Hibernate deployments are exploitable.

Mitigation direction

  • Upgrade Hibernate ORM to 5.3.18, 5.4.18, 5.5.0.Beta1, or later supported releases.
  • Check vendor advisories for products that bundle Hibernate ORM.
  • Review dependency trees for transitive Hibernate ORM versions.
  • Avoid passing untrusted input into Criteria API literals.
  • Prioritize internet-facing and data-sensitive applications first.

Validation and detection

  • Inventory deployed Hibernate ORM versions across applications and packaged products.
  • Search code for JPA Criteria API SELECT or GROUP BY literal usage.
  • Confirm whether external input can influence those query literals.
  • Verify upgraded artifacts are actually deployed in runtime environments.
  • Review database logs for unusual query patterns if exposure is suspected.
Prepared
Confidence
medium
Sources
5

Public sources used

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.

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-2019-14900 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aHibernateVersions before Hibernate ORM 5.3.18, Versions before Hibernate ORM 5.4.18, Versions before Hibernate ORM 5.5.0.Beta1Listed
Weakness

CWE details

No CWE listed

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