Search for packages
| purl | pkg:maven/org.apache.cxf/cxf-rt-transports-http@3.0.0-milestone2 |
| Vulnerability | Summary | Fixed by |
|---|---|---|
|
VCID-64k6-5enf-abgu
Aliases: CVE-2020-13954 GHSA-64x2-gq24-75pv |
Cross-site scripting in Apache CXF By default, Apache CXF creates a /services page containing a listing of the available endpoint names and addresses. This webpage is vulnerable to a reflected Cross-Site Scripting (XSS) attack via the styleSheetPath, which allows a malicious actor to inject javascript into the web page. This vulnerability affects all versions of Apache CXF prior to 3.4.1 and 3.3.8. Please note that this is a separate issue to CVE-2019-17573. |
Affected by 1 other vulnerability. Affected by 1 other vulnerability. |
|
VCID-edyf-jp8v-gfgg
Aliases: CVE-2016-6812 GHSA-vw2c-5wph-v92r |
Affected by 3 other vulnerabilities. Affected by 3 other vulnerabilities. |
|
|
VCID-m1md-etzs-t3gw
Aliases: CVE-2018-8039 GHSA-jc7r-v6fg-2gpf |
It is possible to configure Apache CXF to use the com.sun.net.ssl implementation via 'System.setProperty("java.protocol.handler.pkgs", "com.sun.net.ssl.internal.www.protocol");'. When this system property is set, CXF uses some reflection to try to make the HostnameVerifier work with the old com.sun.net.ssl.HostnameVerifier interface. However, the default HostnameVerifier implementation in CXF does not implement the method in this interface, and an exception is thrown. However, in Apache CXF prior to 3.2.5 and 3.1.16 the exception is caught in the reflection code and not properly propagated. What this means is that if you are using the com.sun.net.ssl stack with CXF, an error with TLS hostname verification will not be thrown, leaving a CXF client subject to man-in-the-middle attacks. |
Affected by 2 other vulnerabilities. Affected by 2 other vulnerabilities. |
|
VCID-tujp-5vda-b3c5
Aliases: CVE-2021-22696 GHSA-7q4h-pj78-j7vg |
Authorization service vulnerable to DDos attacks in Apache CFX CXF supports (via JwtRequestCodeFilter) passing OAuth 2 parameters via a JWT token as opposed to query parameters (see: The OAuth 2.0 Authorization Framework: JWT Secured Authorization Request (JAR)). Instead of sending a JWT token as a "request" parameter, the spec also supports specifying a URI from which to retrieve a JWT token from via the "request_uri" parameter. CXF was not validating the "request_uri" parameter (apart from ensuring it uses "https) and was making a REST request to the parameter in the request to retrieve a token. This means that CXF was vulnerable to DDos attacks on the authorization server, as specified in section 10.4.1 of the spec. This issue affects Apache CXF versions prior to 3.4.3; Apache CXF versions prior to 3.3.10. |
Affected by 0 other vulnerabilities. Affected by 0 other vulnerabilities. |
| Vulnerability | Summary | Aliases |
|---|---|---|
| This package is not known to fix vulnerabilities. | ||
| Date | Actor | Action | Vulnerability | Source | VulnerableCode Version |
|---|---|---|---|---|---|
| 2025-08-01T09:51:18.861887+00:00 | GitLab Importer | Affected by | VCID-tujp-5vda-b3c5 | https://gitlab.com/gitlab-org/advisories-community/-/blob/main/maven/org.apache.cxf/cxf-rt-transports-http/CVE-2021-22696.yml | 37.0.0 |
| 2025-08-01T09:44:51.810457+00:00 | GitLab Importer | Affected by | VCID-64k6-5enf-abgu | https://gitlab.com/gitlab-org/advisories-community/-/blob/main/maven/org.apache.cxf/cxf-rt-transports-http/CVE-2020-13954.yml | 37.0.0 |
| 2025-08-01T09:01:27.723908+00:00 | GitLab Importer | Affected by | VCID-edyf-jp8v-gfgg | https://gitlab.com/gitlab-org/advisories-community/-/blob/main/maven/org.apache.cxf/cxf-rt-transports-http/CVE-2016-6812.yml | 37.0.0 |
| 2025-08-01T08:07:54.323782+00:00 | GHSA Importer | Affected by | VCID-m1md-etzs-t3gw | https://github.com/advisories/GHSA-jc7r-v6fg-2gpf | 37.0.0 |