| パッケージ | 影響を受けるバージョン | 修正済みバージョン |
|---|---|---|
| api control plane | ≥ 4.5.0, < 4.5.0.56≥ 4.6.0, < 4.6.0.20 | 4.5.0.564.6.0.20 |
| api manager | ≥ 3.1.0, < 3.1.0.320≥ 3.2.0, < 3.2.0.413≥ 3.2.1, < 3.2.1.90≥ 4.0.0, < 4.0.0.334≥ 4.1.0, < 4.1.0.255≥ 4.2.0, < 4.2.0.195≥ 4.3.0, < 4.3.0.106≥ 4.4.0, < 4.4.0.70≥ 4.5.0, < 4.5.0.55≥ 4.6.0, < 4.6.0.19 | 3.1.0.3203.2.0.4133.2.1.904.0.0.3344.1.0.2554.2.0.1954.3.0.1064.4.0.704.5.0.554.6.0.19 |
| identity server | ≥ 5.10.0, < 5.10.0.338≥ 5.11.0, < 5.11.0.395≥ 6.0.0, < 6.0.0.229≥ 6.1.0, < 6.1.0.208 | 5.10.0.3385.11.0.3956.0.0.2296.1.0.208 |
| identity server as key manager | ≥ 5.10.0, < 5.10.0.338 | 5.10.0.338 |
| open banking am | ≥ 2.0.0, < 2.0.0.369 | 2.0.0.369 |
| open banking iam | ≥ 2.0.0, < 2.0.0.389 | 2.0.0.389 |
| traffic manager | ≥ 4.5.0, < 4.5.0.54≥ 4.6.0, < 4.6.0.19 | 4.5.0.544.6.0.19 |
| universal gateway | ≥ 4.5.0, < 4.5.0.55≥ 4.6.0, < 4.6.0.19 | 4.5.0.554.6.0.19 |
Unused authorization codes issued to deleted users are not being properly invalidated or removed from the system. This allows for the persistence of these codes, enabling them to be potentially reused. If an attacker possesses both the authorization code and the associated client credentials (client ID and client secret), they can leverage these unused codes to obtain access tokens on behalf of users who have already been deleted. This may lead to unauthorized access to sensitive resources and services, contingent on the scopes originally authorized for the compromised authorization code.
これらの製品をお使いですか？サイトをスキャンして、脆弱なバージョンが公開されていないか確認しましょう。
無料でサイトをスキャン