-
Public Security Vulnerability
-
Resolution: Fixed
-
High
-
5.0.0, 5.0.1, 5.1.0, 5.0.2, 5.0.3, 5.2.0, 5.0.4, 5.1.1, 5.1.2, 5.0.5, 5.0.6, 5.1.3, 5.1.4, 5.0.7, 5.1.5, 5.1.6, 5.0.8, 5.2.1, 5.2.2, 5.1.7, 5.0.9, 5.2.3, 5.1.8, 5.0.10
-
None
-
7.5
-
High
-
CVE-2017-7656
-
Atlassian (Internal)
-
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
-
Security Misconfiguration
-
Crowd Data Center, Crowd Server
This High severity org.eclipse.jetty:jetty-server Dependency vulnerability was introduced in versions 5.0.0, 5.1.0, and 5.2.0 of Crowd Data Center and Server.
This org.eclipse.jetty:jetty-server Dependency vulnerability, with a CVSS Score of 7.5 and a CVSS Vector of CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N allows an unauthenticated attacker to expose assets in your environment susceptible to exploitation which has no impact to confidentiality, high impact to integrity, no impact to availability, and requires no user interaction.
Atlassian recommends that Crowd Data Center and Server customers upgrade to latest version, if you are unable to do so, upgrade your instance to one of the specified supported fixed versions:
Affected versions | Fixed versions |
---|---|
5.2.0 to 5.2.3 | 5.2.4 |
5.1.0 to 5.1.8 | 5.1.9 or 5.2.4 recommended |
5.0 to 5.0.10 | 5.1.9 or 5.2.4 recommended |
Any earlier versions | 5.1.9 or 5.2.4 recommended |
See the release notes (https://confluence.atlassian.com/crowd/crowd-release-notes-199094.html). You can download the latest version of Crowd Data Center and Server from the download center (https://www.atlassian.com/software/crowd/download-archive).
The National Vulnerability Database provides the following description for this vulnerability: In Eclipse Jetty, versions 9.2.x and older, 9.3.x (all configurations), and 9.4.x (non-default configuration with RFC2616 compliance enabled), HTTP/0.9 is handled poorly. An HTTP/1 style request line (i.e. method space URI space version) that declares a version of HTTP/0.9 was accepted and treated as a 0.9 request. If deployed behind an intermediary that also accepted and passed through the 0.9 version (but did not act on it), then the response sent could be interpreted by the intermediary as HTTP/1 headers. This could be used to poison the cache if the server allowed the origin client to generate arbitrary content in the response.