← Search results
CVE-LINKED INVENTORY14 SECURITY RECORDS
Publisher not identified
undertow
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
Official registry publication history is available at undertow, but registry activity is not a publisher support boundary.
A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.
CVE-observed version history
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2022-4492 | 23 Feb 2023 | 2.7 | Before applying this update, ensure all previously released errata relevant to your system have been applied. Also, back up your existing installation, including all applications, configuration files, databases and database settings. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2022-2764 | 1 Sep 2022 | undertow 2.x | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-1319 | 31 Aug 2022 | Fixed in 2.3.0.Final, 2.2.18.Final, 2.2.17.SP3, 2.2.17.SP4, 2.3.0.Alpha2 | Before applying this update, ensure all previously released errata relevant to your system have been applied. Also, back up your existing installation, including all applications, configuration files, databases and database settings. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2022-1259 | 31 Aug 2022 | Fixed in 2.3.0.Final, 2.2.17.SP1, 2.2.20.Final, 2.2.19.SP1. | Before applying this update, ensure all previously released errata relevant to your system have been applied. Also, back up your existing installation, including all applications, configuration files, databases and database settings. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2021-3859 | 26 Aug 2022 | Fixed in 2.2.15.Final | Before applying this update, back up your existing Red Hat JBoss Enterprise Application Platform installation and deployed applications. For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2021-3690 | 23 Aug 2022 | Fixed in 2.2.10.Final, 2.0.40.Final | Before applying this update, back up your existing Red Hat JBoss Enterprise Application Platform installation and deployed applications. For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2022-2053 | 5 Aug 2022 | Fixed in Undertow 2.2.19.Final, Undertow 2.3.0.Alpha2 | Before applying this update, ensure all previously released errata relevant to your system have been applied. Also, back up your existing installation, including all applications, configuration files, databases and database settings. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2021-3597 | 24 May 2022 | undertow 2.0.35.SP1, undertow 2.2.6.SP1, undertow 2.2.7.SP1, undertow 2.0.36.SP1, undertow 2.2.9.Final, undertow 2.0.39.Final | Before applying this update, back up your existing Red Hat JBoss Enterprise Application Platform installation and deployed applications. For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2021-3629 | 24 May 2022 | undertow 2.0.40.Final, undertow 2.2.11.Final | Before applying this update, back up your existing Red Hat JBoss Enterprise Application Platform installation and deployed applications. For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2019-19343 | 23 Mar 2021 | undertow 2.0.25.SP1, jboss-remoting 5.0.14.SP1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-27782 | 23 Feb 2021 | 2.1.5.SP1; 2.0.33.SP2; 2.2.3.SP1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2021-20220 | 23 Feb 2021 | Undertow 2.2.0.Final, Undertow 2.1.6.Final, Undertow 2.0.34.Final | Before applying this update, ensure all previously released errata relevant to your system have been applied. For details about how to apply this update, see: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2020-10687 | 23 Sep 2020 | Undertow 2.2.0.Final | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-10705 | 10 Jun 2020 | Versions before Undertow 2.1.1.Final. | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
How this record is maintained
The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.