| パッケージ | 影響を受けるバージョン | 修正済みバージョン |
|---|---|---|
| org.apache.cxf:apache-cxf | ≥ 3.4.0, < 3.4.3< 3.3.10 | 3.4.33.3.10 |
| org.apache.cxf:cxf | ≥ 3.4.0, < 3.4.3< 3.3.10 | 3.4.33.3.10 |
| cxf | ≥ 3.4.0, < 3.4.3< 3.3.10 | 3.4.33.3.10 |
| business intelligence | = 12.2.1.3.0= 12.2.1.4.0= 5.5.0.0.0= 5.9.0.0.0 | |
| communications diameter intelligence hub | ≥ 8.0.0, ≤ 8.1.0≥ 8.2.0, ≤ 8.2.3 | |
| communications element manager | = 8.2.2 | |
| communications session report manager | ≥ 8.0.0, ≤ 8.2.4.0 | |
| communications session route manager | ≥ 8.0.0, ≤ 8.2.4 |
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.
これらの製品をお使いですか？サイトをスキャンして、脆弱なバージョンが公開されていないか確認しましょう。
無料でサイトをスキャン