# CVE-2020-10693: Improper Input Validation in Hibernate Validator

> Attackers can execute arbitrary code by bypassing input sanitation in Hibernate Validator error messages via invalid EL expressions.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 May 2020
- **Updated:** 4 Aug 2024
- **Also known as:** CLSA-2026-1770682156, CLSA-2026-1791220396, DEBIAN-CVE-2020-10693, GHSA-rmrm-75hp-phr2, OESA-2021-1138, UBUNTU-CVE-2020-10693

## What is CVE-2020-10693?

CVE-2020-10693 is a medium-severity code injection vulnerability in Ibm Websphere Application Server, published on 6 May 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A flaw was found in Hibernate Validator version 6.1.2.Final. A bug in the message interpolation processor enables invalid EL expressions to be evaluated as if they were valid. This flaw allows attackers to bypass input sanitation (escaping, stripping) controls that developers may have put in place when handling user-controlled data in error messages.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2020-10693?

8 open source packages ship an affected version, including org.hibernate.validator:hibernate-validator and org.hibernate:hibernate-validator. It affects 7 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.hibernate.validator:hibernate-validator` | Maven | All versions | 6.0.20.Final |
| `org.hibernate.validator:hibernate-validator` | Maven | All versions | 6.0.20.Final |
| `org.hibernate.validator:hibernate-validator` | Maven | From 6.1.0.Final | 6.1.5.Final |
| `org.hibernate.validator:hibernate-validator` | Maven | From 6.1.0.Final | 6.1.5.Final |
| `org.hibernate:hibernate-validator` | Maven | All versions | 6.0.20.Final |
| `org.hibernate:hibernate-validator` | Maven | All versions | 6.0.20.Final |
| `org.hibernate:hibernate-validator` | Maven | From 6.1.0.Final | 6.1.5.Final |
| `org.hibernate:hibernate-validator` | Maven | From 6.1.0.Final | 6.1.5.Final |

Products: Ibm Websphere Application Server, Oracle Weblogic Server, Quarkus Quarkus, Redhat Hibernate Validator, Redhat Jboss Enterprise Application Platform, Redhat Satellite, Redhat Satellite Capsule.

## How do I fix CVE-2020-10693?

Upgrade org.hibernate.validator:hibernate-validator to a fixed version for your release line: 6.0.20.Final or 6.1.5.Final.

## Is CVE-2020-10693 being exploited?

There is no known exploitation of CVE-2020-10693 in the wild and no public exploit code.

## Other vulnerabilities in Ibm Websphere Application Server

- [CVE-2015-1920](https://insights.sbomify.com/CVE-2015-1920/): Code injection in n/a (critical 10.0)
- [CVE-2013-0462](https://insights.sbomify.com/CVE-2013-0462/): Other in n/a (critical 10.0)
- [CVE-2011-1377](https://insights.sbomify.com/CVE-2011-1377/): Security feature bypass in n/a (critical 10.0)
- [CVE-2010-3186](https://insights.sbomify.com/CVE-2010-3186/): Other in n/a (critical 10.0)
- [CVE-2009-1899](https://insights.sbomify.com/CVE-2009-1899/): Information disclosure in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-10693 and fix it if it is affected.

What it is: CVE-2020-10693 is a medium-severity code injection vulnerability in Ibm Websphere Application Server, published on 6 May 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-10693 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.hibernate.validator:hibernate-validator (Maven): affected all versions; fixed in 6.0.20.Final
- org.hibernate.validator:hibernate-validator (Maven): affected all versions; fixed in 6.0.20.Final
- org.hibernate.validator:hibernate-validator (Maven): affected from 6.1.0.Final; fixed in 6.1.5.Final
- org.hibernate.validator:hibernate-validator (Maven): affected from 6.1.0.Final; fixed in 6.1.5.Final
- org.hibernate:hibernate-validator (Maven): affected all versions; fixed in 6.0.20.Final
- org.hibernate:hibernate-validator (Maven): affected all versions; fixed in 6.0.20.Final
- org.hibernate:hibernate-validator (Maven): affected from 6.1.0.Final; fixed in 6.1.5.Final
- org.hibernate:hibernate-validator (Maven): affected from 6.1.0.Final; fixed in 6.1.5.Final

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-2020-10693/ (Markdown: https://insights.sbomify.com/CVE-2020-10693/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-10693
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-10693
- OSV: https://osv.dev/vulnerability/CVE-2020-10693

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-10693/
Summaries are generated and may contain mistakes; the official description above is the record.