# CVE-2014-3558: Improper Authentication in Hibernate Validator > Attackers can bypass Java Security Manager restrictions to execute restricted reflection calls in Hibernate Validator, potentially leading to code execution. - **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Not stated - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 30 Sep 2014 - **Updated:** 6 Aug 2024 - **Also known as:** DEBIAN-CVE-2014-3558, GHSA-845h-985r-jrqh, RHSA-2014:1285, RHSA-2014:1286, RHSA-2014:1287 ## What is CVE-2014-3558? CVE-2014-3558 is a medium-severity vulnerability in n/a, published on 30 Sep 2014. ### Official description ReflectionHelper (org.hibernate.validator.util.ReflectionHelper) in Hibernate Validator 4.1.0 before 4.2.1, 4.3.x before 4.3.2, and 5.x before 5.1.2 allows attackers to bypass Java Security Manager (JSM) restrictions and execute restricted reflection calls via a crafted application. Weakness: CWE-264 ## Which versions are affected by CVE-2014-3558? 6 open source packages ship an affected version, including org.hibernate:hibernate-validator. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.hibernate:hibernate-validator` | Maven | From 4.1.0 | 4.2.1 | | `org.hibernate:hibernate-validator` | Maven | From 4.1.0 | 4.2.1 | | `org.hibernate:hibernate-validator` | Maven | From 4.3.0 | 4.3.2 | | `org.hibernate:hibernate-validator` | Maven | From 4.3.0 | 4.3.2 | | `org.hibernate:hibernate-validator` | Maven | From 5.0.0 | 5.1.2 | | `org.hibernate:hibernate-validator` | Maven | From 5.0.0 | 5.1.2 | | `glassfish-jaxb-eap6` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:2.2.5-22.redhat_9.1.ep6.el5 | | `glassfish-jsf-eap6` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:2.1.28-5.redhat_6.1.ep6.el5 | | `hibernate4-core-eap6` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:4.2.14-8.SP3_redhat_1.1.ep6.el5 | | `hibernate4-eap6` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:4.2.14-8.SP3_redhat_1.1.ep6.el5 | | `hibernate4-entitymanager-eap6` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:4.2.14-8.SP3_redhat_1.1.ep6.el5 | | `hibernate4-envers-eap6` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:4.2.14-8.SP3_redhat_1.1.ep6.el5 | | `hibernate4-infinispan-eap6` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:4.2.14-8.SP3_redhat_1.1.ep6.el5 | | `hibernate4-validator` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:4.3.2-1.Final_redhat_1.2.ep6.el5 | | `hornetq` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:2.3.21-1.Final_redhat_1.1.ep6.el5 | | `httpclient-eap6` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:4.2.6-4.redhat_3.1.ep6.el5 | | `httpcomponents-client-eap6` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:4.2.6-4.redhat_3.1.ep6.el5 | | `httpcomponents-core-eap6` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:4.2.5-4.redhat_3.1.ep6.el5 | | `httpcomponents-eap6` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7-4.redhat_3.1.ep6.el5 | | `httpcomponents-project-eap6` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7-4.redhat_3.1.ep6.el5 | | `httpcore-eap6` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:4.2.5-4.redhat_3.1.ep6.el5 | | `httpmime-eap6` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:4.2.6-4.redhat_3.1.ep6.el5 | | `ironjacamar-common-api-eap6` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:1.0.27-1.Final_redhat_1.1.ep6.el5 | | `ironjacamar-common-impl-eap6` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:1.0.27-1.Final_redhat_1.1.ep6.el5 | | `ironjacamar-common-spi-eap6` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:1.0.27-1.Final_redhat_1.1.ep6.el5 | | `ironjacamar-core-api-eap6` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:1.0.27-1.Final_redhat_1.1.ep6.el5 | | `ironjacamar-core-impl-eap6` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:1.0.27-1.Final_redhat_1.1.ep6.el5 | | `ironjacamar-deployers-common-eap6` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:1.0.27-1.Final_redhat_1.1.ep6.el5 | | `ironjacamar-eap6` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:1.0.27-1.Final_redhat_1.1.ep6.el5 | | `ironjacamar-jdbc-eap6` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:1.0.27-1.Final_redhat_1.1.ep6.el5 | | `ironjacamar-spec-api-eap6` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:1.0.27-1.Final_redhat_1.1.ep6.el5 | | `ironjacamar-validator-eap6` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:1.0.27-1.Final_redhat_1.1.ep6.el5 | | `jboss-annotations-api_1.1_spec` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:1.0.1-4.Final_redhat_2.2.ep6.el5 | | `jboss-as-appclient` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.4.1-2.Final_redhat_3.1.ep6.el5 | | `jboss-as-cli` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.4.1-2.Final_redhat_3.1.ep6.el5 | | `jboss-as-client-all` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.4.1-2.Final_redhat_3.1.ep6.el5 | | `jboss-as-clustering` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.4.1-2.Final_redhat_3.1.ep6.el5 | | `jboss-as-cmp` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.4.1-2.Final_redhat_3.1.ep6.el5 | | `jboss-as-configadmin` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.4.1-2.Final_redhat_3.1.ep6.el5 | | `jboss-as-connector` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.4.1-2.Final_redhat_3.1.ep6.el5 | Products: Redhat Hibernate Validator. ## How do I fix CVE-2014-3558? Upgrade org.hibernate:hibernate-validator to a fixed version for your release line: 4.2.1, 4.3.2 or 5.1.2. ## Is CVE-2014-3558 being exploited? There is no known exploitation of CVE-2014-3558 in the wild and no public exploit code. ## Other vulnerabilities in n/a - [CVE-2017-7536](https://insights.sbomify.com/CVE-2017-7536/): Privilege Escalation in Hibernate Validator (high 7.0) - [CVE-2025-35036](https://insights.sbomify.com/CVE-2025-35036/): hibernate-validator insecure default Expression Language interpolation (medium 6.9) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2014-3558 and fix it if it is affected. What it is: CVE-2014-3558 is a medium-severity vulnerability in n/a, published on 30 Sep 2014. Exploitation: There is no known exploitation of CVE-2014-3558 in the wild and no public exploit code. Affected packages and fixed versions: - org.hibernate:hibernate-validator (Maven): affected from 4.1.0; fixed in 4.2.1 - org.hibernate:hibernate-validator (Maven): affected from 4.1.0; fixed in 4.2.1 - org.hibernate:hibernate-validator (Maven): affected from 4.3.0; fixed in 4.3.2 - org.hibernate:hibernate-validator (Maven): affected from 4.3.0; fixed in 4.3.2 - org.hibernate:hibernate-validator (Maven): affected from 5.0.0; fixed in 5.1.2 - org.hibernate:hibernate-validator (Maven): affected from 5.0.0; fixed in 5.1.2 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2014-3558/ (Markdown: https://insights.sbomify.com/CVE-2014-3558/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2014-3558 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2014-3558 - OSV: https://osv.dev/vulnerability/CVE-2014-3558 --- From sbomify Insights: https://insights.sbomify.com/CVE-2014-3558/ Summaries are generated and may contain mistakes; the official description above is the record.