| パッケージ | 影響を受けるバージョン | 修正済みバージョン |
|---|---|---|
| curl | ≥ 7.75.0, ≤ 7.76.1 | |
| communications cloud native core binding support function | = 1.11.0 | |
| communications cloud native core network function cloud native environment | = 1.10.0 | |
| communications cloud native core network repository function | = 1.15.0= 1.15.1 | |
| communications cloud native core network slice selection function | = 1.8.0 | |
| communications cloud native core service communication proxy | = 1.15.0 | |
| essbase | ≥ 21.0, < 21.3< 11.1.2.4.047 | 21.311.1.2.4.047 |
| mysql server | ≥ 8.0.0, ≤ 8.0.25≤ 5.7.34 | |
| sinec infrastructure network services | < 1.0.1.1 | 1.0.1.1 |
| universal forwarder | = 9.1.0≥ 8.2.0, < 8.2.12≥ 9.0.0, < 9.0.6 | 8.2.129.0.6 |
curl 7.75.0 through 7.76.1 suffers from a use-after-free vulnerability resulting in already freed memory being used when a TLS 1.3 session ticket arrives over a connection. A malicious server can use this in rare unfortunate circumstances to potentially reach remote code execution in the client. When libcurl at run-time sets up support for TLS 1.3 session tickets on a connection using OpenSSL, it stores pointers to the transfer in-memory object for later retrieval when a session ticket arrives. If the connection is used by multiple transfers (like with a reused HTTP/1.1 connection or multiplexed HTTP/2 connection) that first transfer object might be freed before the new session is established on that connection and then the function will access a memory buffer that might be freed. When using that memory, libcurl might even call a function pointer in the object, making it possible for a remote code execution if the server could somehow manage to get crafted memory content into the correct place in memory.
これらの製品をお使いですか?サイトをスキャンして、脆弱なバージョンが公開されていないか確認しましょう。
無料でサイトをスキャン