Codeready StudioApplication · Redhat
CVE-2023-1932
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-validator's 'isValid' method in the org.hibernate.validator.internal.constraintvalidators.hv.SafeHtmlValidator class, which can be bypassed by omitting the tag ending in a less-than character. Browsers may render an invalid html, allowing HTML injection or Cross-Site-Scripting (XSS) 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 confidenceThe SafeHtmlValidator in hibernate-validator fails to properly validate HTML when the tag ending is omitted (e.g., '<script' instead of '</script>'). This bypass allows malicious HTML to pass validation, enabling XSS attacks through improper HTML injection.
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
Codeready StudioApplication
= 12.0
Jboss Enterprise Application PlatformApplication
all versions= 7.0.0
Openstack PlatformApplication
= 13.0
Single Sign OnApplication
= 7.0< 6.2CVSS 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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-validator versionCheck your project dependency management (Maven pom.xml, Gradle build.gradle) for hibernate-validator version, or inspect the hibernate-validator JAR manifest if deployed as a standalone libraryAffected if Version is below 6.2.0 (e.g., 6.1.x, 6.0.x)
-
Check for JBoss EAP usage and versionIf using Redhat JBoss Enterprise Application Platform, check the installed server version via $JBOSS_HOME/bin/standalone.sh --version or the manifest in jboss-modules.jarAffected if Any version of JBoss EAP is in use with hibernate-validator
-
Determine if SafeHtmlValidator is actively usedSearch codebase for imports of org.hibernate.validator.constraints.SafeHtml, @SafeHtml annotations on fields/methods, or programmatic use of SafeHtmlValidator.classAffected if SafeHtmlValidator or @SafeHtml annotation is present in the codebase
-
Identify HTML input validation flowTrace the data flow: locate where user-supplied HTML enters the application and passes through hibernate-validator validation (e.g., form inputs, API payloads, stored content)Affected if HTML input is accepted and validated by hibernate-validator's SafeHtml constraint
-
Test for tag omission bypassSubmit test payloads with unclosed tags such as '<script', '<img', '<svg' (without closing '/script', '/img', '/svg') through the validated input field and observe if the payload passes validationAffected if The validator accepts HTML with missing closing tags (e.g., '<script' passes but '</script>' is required for valid HTML)
You are affected if hibernate-validator version is below 6.2 AND your application uses SafeHtmlValidator/@SafeHtml to validate HTML input that originates from untrusted sources.
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.
dbcve · scoped6.2
Update hibernate-validator to the latest version containing the fix, and implement additional output encoding/sanitization on the consumer side as defense-in-depth.
Hibernate Validator 6.2.0.Final or later (or corresponding Red Hat Security Update for affected JBoss products)
- Identify all applications and dependencies that include hibernate-validator (check pom.xml, build.gradle, or packaged EAR/WAR files)
- Locate the hibernate-validator library in your project dependencies (typically under ~/.m2/repository/org/hibernate/validator/ or in the application server's module directory)
- Upgrade hibernate-validator to version 6.2.0.Final or later from the Maven Central repository or Red Hat subscriber portal
- Rebuild and recompile all applications that depend on hibernate-validator to include the new version
- Redeploy affected applications to Jboss EAP, Codeready Studio, OpenStack Platform, or Single Sign On environments
- Verify the fix by testing input validation with XSS payloads that omit closing tags (e.g., '<script src=javascript:alert(1)>' without the closing '></script>')
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Codeready Studio
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-1932 — 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-2023-1932 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