MITM (Man-in-the-Middle) io.netty:netty-handler Dependency in Crowd Data Center

XMLWordPrintable

    • 7.5
    • High
    • CVE-2026-50010
    • Atlassian (Internal)
    • CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
    • MITM (Man-in-the-Middle)
    • Crowd Data Center

      This High severity MITM (Man-in-the-Middle) vulnerability was introduced in versions 6.2.0, 6.3.6, 7.0.0, 7.1.0, and
      7.2.0 of Crowd Data Center.

      This MITM (Man-in-the-Middle) vulnerability, with a CVSS Score of 7.5 and a CVSS Vector of
      CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N allows an unauthenticated attacker to expose assets in your environment
      susceptible to exploitation which has high impact to confidentiality, no impact to integrity, no impact to availability,
      and requires no user interaction.

      Atlassian recommends that Crowd Data Center customers upgrade to latest version, if you are unable to do so, upgrade
      your instance to one of the specified supported fixed versions:

      • Crowd Data Center 7.2: Upgrade to a release greater than or equal to 7.2.2

      See the release notes (https://confluence.atlassian.com/crowd/crowd-release-notes-199094.html). You can download the
      latest version of Crowd Data Center from the download center
      (https://www.atlassian.com/software/crowd/download-archive).

      The National Vulnerability Database provides the following description for this vulnerability:

      Netty is a network application framework for development of protocol servers and clients. Prior to versions
      4.1.135.Final and 4.2.15.Final, SimpleTrustManagerFactory.engineGetTrustManagers() and related paths wrap any
      user-supplied plain X509TrustManager in X509TrustManagerWrapper, which extends X509ExtendedTrustManager but implements
      the 3-arg checkServerTrusted(chain, authType, SSLEngine) by discarding the SSLEngine and calling the 2-arg delegate.
      Because the object now IS an X509ExtendedTrustManager, neither SunJSSE's internal AbstractTrustManagerWrapper nor
      Netty's own OpenSslX509TrustManagerWrapper will re-wrap it to add endpoint-identification. Consequently, even though
      Netty 4.2 sets endpointIdentificationAlgorithm="HTTPS" by default, a client built with
      `SslContextBuilder.forClient().trustManager(somePlainX509TrustManager)` performs no hostname verification at all.
      Versions 4.1.135.Final and 4.2.15.Final patch the issue.

              Assignee:
              Unassigned
              Reporter:
              Security Metrics Bot
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: