Build Of QuarkusApplication · Redhat
CVE-2019-14900
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceSQL injection vulnerability in Hibernate ORM's JPA Criteria API implementation. When literals are used in SELECT or GROUP BY parts of queries without proper sanitization, an attacker can inject malicious SQL to access unauthorized data or conduct further attacks. Affects versions before 5.3.18, 5.4.18, and 5.5.0.Beta1.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Build Of QuarkusApplication
all versions
Decision ManagerApplication
= 7.0
FuseApplication
< 7.8.0
Jboss Data GridApplication
= 7.0.0
Jboss Enterprise Application PlatformApplication
all versions= 7.3= 7.4= 7.2
Jboss Middleware Text Only AdvisoriesApplication
all versions
OpenstackApplication
= 10= 13= 14
Single Sign OnApplication
all versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Hibernate ORM library presenceSearch for hibernate-core JAR files or Maven/Gradle dependencies containing 'hibernate' in your application dependenciesAffected if Hibernate ORM is present in the application
-
Determine Hibernate ORM versionCheck the hibernate-core version in your dependency management (pom.xml, build.gradle, or the JAR manifest)Affected if Version is before 5.3.18, before 5.4.18, or before 5.5.0.Beta1 (any version < 5.5.0.Beta1 that is not 5.3.18 or 5.4.18)
-
Identify JPA Criteria API usage in SELECT clausesSearch codebase for code using CriteriaQuery.select(), CriteriaBuilder.construct(), or explicit SELECT statements in Criteria queriesAffected if Code uses Criteria API to select fields with literal values
-
Identify JPA Criteria API usage in GROUP BY clausesSearch codebase for code using CriteriaQuery.groupBy() with literal values in the grouping expressionAffected if Code uses Criteria API with GROUP BY containing literal values
-
Check for unsanitized input in Criteria queriesReview all CriteriaQuery implementations that include literals or string concatenation in SELECT or GROUP BY, verify if user-controlled parameters are directly interpolated without parameterizationAffected if Literals in SELECT or GROUP BY are constructed from untrusted input without sanitization
Your environment is affected if you run any Hibernate ORM version below 5.3.18, 5.4.18, or 5.5.0.Beta1 AND your application uses JPA Criteria API with literal values in SELECT or GROUP BY clauses derived from user input.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data7.8.0
Upgrade Hibernate ORM to version 5.3.18, 5.4.18, or later. Additionally, review all JPA Criteria API queries that use literals in SELECT or GROUP BY clauses to ensure no unsanitized input is passed.
Fix this in Build Of Quarkus
Scoped from the published advisory
- Consultation6.0 h
- Implementation12.0 h
- Testing16.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,944.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-14900 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-14900 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data