Search for packages
| purl | pkg:maven/org.apache.cxf/cxf@2.4.9 |
| Vulnerability | Summary | Fixed by |
|---|---|---|
|
VCID-3tb8-jrjz-b7fw
Aliases: CVE-2022-46364 GHSA-x3x3-qwjq-8gj4 |
Apache CXF Server-Side Request Forgery vulnerability A SSRF vulnerability in parsing the href attribute of XOP:Include in MTOM requests in versions of Apache CXF before 3.5.5 and 3.4.10 allows an attacker to perform SSRF style attacks on webservices that take at least one parameter of any type. |
Affected by 0 other vulnerabilities. Affected by 0 other vulnerabilities. |
|
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 3 other vulnerabilities. Affected by 3 other vulnerabilities. |
|
VCID-7w7b-5v75-4qd9
Aliases: CVE-2019-12423 GHSA-42f2-f9vc-6365 |
Private key leak in Apache CXF Apache CXF ships with a OpenId Connect JWK Keys service, which allows a client to obtain the public keys in JWK format, which can then be used to verify the signature of tokens issued by the service. Typically, the service obtains the public key from a local keystore (JKS/PKCS12) by specifing the path of the keystore and the alias of the keystore entry. This case is not vulnerable. However it is also possible to obtain the keys from a JWK keystore file, by setting the configuration parameter `rs.security.keystore.type` to `jwk`. For this case all keys are returned in this file "as is", including all private key and secret key credentials. This is an obvious security risk if the user has configured the signature keystore file with private or secret key credentials. From CXF 3.3.5 and 3.2.12, it is mandatory to specify an alias corresponding to the id of the key in the JWK file, and only this key is returned. In addition, any private key information is omitted by default. `oct` keys, which contain secret keys, are not returned at all. |
Affected by 5 other vulnerabilities. Affected by 5 other vulnerabilities. |
|
VCID-h4gn-4zp9-jyh5
Aliases: CVE-2019-17573 GHSA-f93p-f762-vr53 |
Reflected 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, which allows a malicious actor to inject javascript into the web page. Please note that the attack exploits a feature which is not typically not present in modern browsers, who remove dot segments before sending the request. However, Mobile applications may be vulnerable. |
Affected by 5 other vulnerabilities. Affected by 5 other vulnerabilities. |
|
VCID-kxm6-jc3k-3bfp
Aliases: CVE-2020-1954 GHSA-ffm7-7r8g-77xm |
Apache CXF JMX Integration is vulnerable to a MITM attack Apache CXF has the ability to integrate with JMX by registering an `InstrumentationManager` extension with the CXF bus. If the `createMBServerConnectorFactory` property of the default `InstrumentationManagerImpl` is not disabled, then it is vulnerable to a man-in-the-middle (MITM) style attack. An attacker on the same host can connect to the registry and rebind the entry to another server, thus acting as a proxy to the original. They are then able to gain access to all of the information that is sent and received over JMX. |
Affected by 4 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 9 other vulnerabilities. Affected by 9 other vulnerabilities. |
|
VCID-qjqy-9ypz-8bgz
Aliases: CVE-2022-46363 GHSA-3w37-5p3p-jv92 |
Apache CXF vulnerable to Exposure of Sensitive Information A vulnerability in Apache CXF before versions 3.5.5 and 3.4.10 allows an attacker to perform a remote directory listing or code exfiltration. The vulnerability only applies when the CXFServlet is configured with both the static-resources-list and redirect-query-check attributes. These attributes are not supposed to be used together, and so the vulnerability can only arise if the CXF service is misconfigured. |
Affected by 0 other vulnerabilities. Affected by 0 other vulnerabilities. |
|
VCID-tt64-r2e3-sue6
Aliases: CVE-2019-12419 GHSA-cw6w-q88j-6mqf |
Potential session hijack in Apache CXF Apache CXF before 3.3.4 and 3.2.11 provides all of the components that are required to build a fully fledged OpenId Connect service. There is a vulnerability in the access token services, where it does not validate that the authenticated principal is equal to that of the supplied clientId parameter in the request. If a malicious client was able to somehow steal an authorization code issued to another client, then they could exploit this vulnerability to obtain an access token for the other client. |
Affected by 7 other vulnerabilities. Affected by 7 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 2 other vulnerabilities. Affected by 2 other vulnerabilities. |
|
VCID-vd5r-76hv-3bbv
Aliases: CVE-2019-12406 GHSA-58p8-9g59-q2hr |
Potential DOS attack due to unrestricted attachment count in messages Apache CXF before 3.3.4 and 3.2.11 does not restrict the number of message attachments present in a given message. This leaves open the possibility of a denial of service type attack, where a malicious user crafts a message containing a very large number of message attachments. From the 3.3.4 and 3.2.11 releases, a default limit of 50 message attachments is enforced. This is configurable via the message property "attachment-max-count". |
Affected by 7 other vulnerabilities. Affected by 7 other vulnerabilities. |
|
VCID-wrwu-yqgh-7qdk
Aliases: CVE-2012-5633 GHSA-xf9f-32gh-h2w4 |
Affected by 10 other vulnerabilities. Affected by 10 other vulnerabilities. Affected by 10 other vulnerabilities. |
| Vulnerability | Summary | Aliases |
|---|---|---|
| VCID-g8ms-27bp-4qa6 |
CVE-2012-3451
GHSA-55j7-f5wf-43m4 |