Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2022-4492: The undertow client is not checking the server identity presented by the server certificate in https connectio

48
This month
HIGH 7.5REMOTEWATCHLISTMITIGATEMITIGATEMITIGATE

CVE-2022-4492 is a high-severity flaw (CVSS 7.5) affecting build of quarkus, integration camel for spring boot, integration camel k. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The undertow client is not checking the server identity presented by the server certificate in https connections. This is a compulsory step (at least it should be performed by default) in https and in http/2. I would add it to any TLS client protocol.

Why this priority

  • High severity
  • Remotely exploitable, no login, no user action
  • On your watchlist

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score7.5 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance0.6% (top 52%)
CISA exploited listNo
WeaknessCWE-918
Published2023-02-23
Last modified2026-06-17
Publisher (CNA): Red Hat, Inc. · Vendor: redhat

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

redhat build of quarkus MITIGATE
Affected: all versions
Fixed in: no fixed release known
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy build-of-quarkus || rpm -q build-of-quarkus || build-of-quarkus --version
No fixed or unaffected release known
Apply the vendor mitigation from the advisory, disable the affected feature, or restrict network access.
redhat integration camel for spring boot MITIGATE
Affected: all versions
Fixed in: no fixed release known
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy integration-camel-for-spring-boot || rpm -q integration-camel-for-spring-boot || integration-camel-for-spring-boot --version
No fixed or unaffected release known
Apply the vendor mitigation from the advisory, disable the affected feature, or restrict network access.
redhat integration camel k MITIGATE
Affected: all versions
Fixed in: no fixed release known
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy integration-camel-k || rpm -q integration-camel-k || integration-camel-k --version
No fixed or unaffected release known
Apply the vendor mitigation from the advisory, disable the affected feature, or restrict network access.
redhat integration service registry MITIGATE
Affected: all versions
Fixed in: no fixed release known
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy integration-service-registry || rpm -q integration-service-registry || integration-service-registry --version
No fixed or unaffected release known
Apply the vendor mitigation from the advisory, disable the affected feature, or restrict network access.
redhat jboss enterprise application platform DOWNGRADE
Affected: 7.0.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 7.0.0
1. Check installed version
apt-cache policy jboss-enterprise-application-platform || rpm -q jboss-enterprise-application-platform || jboss-enterprise-application-platform --version
2. No fixed release: DOWNGRADE to a release before 7.0.0 (Debian / Ubuntu)
apt-cache madison jboss-enterprise-application-platform sudo apt install jboss-enterprise-application-platform=<VERSION_BEFORE_7.0.0> sudo apt-mark hold jboss-enterprise-application-platform
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list jboss-enterprise-application-platform sudo dnf downgrade jboss-enterprise-application-platform-<VERSION_BEFORE_7.0.0> sudo dnf versionlock add jboss-enterprise-application-platform
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
redhat jboss fuse DOWNGRADE
Affected: 7.0.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 7.0.0
1. Check installed version
apt-cache policy jboss-fuse || rpm -q jboss-fuse || jboss-fuse --version
2. No fixed release: DOWNGRADE to a release before 7.0.0 (Debian / Ubuntu)
apt-cache madison jboss-fuse sudo apt install jboss-fuse=<VERSION_BEFORE_7.0.0> sudo apt-mark hold jboss-fuse
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list jboss-fuse sudo dnf downgrade jboss-fuse-<VERSION_BEFORE_7.0.0> sudo dnf versionlock add jboss-fuse
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-4492?

build of quarkus: mitigate or apply the listed mitigation; integration camel for spring boot: mitigate or apply the listed mitigation; integration camel k: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2022-4492 being exploited?

CVE-2022-4492 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-4492 affect?

CVE-2022-4492 affects build of quarkus, integration camel for spring boot, integration camel k. Severity is high (CVSS 7.5). The undertow client is not checking the server identity presented by the server certificate in https connections. This is a compulsory step (at least it should be performed by default) in https and in http/2. I would add it to any TLS clien

How urgent is CVE-2022-4492?

Priority 48/100. High severity; Remotely exploitable, no login, no user action; On your watchlist

Software pages

Spring Framework vulnerabilities · JBoss and WildFly vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.