| Title | FFmpeg におけるリソース管理に関する脆弱性 |
|---|---|
| Summary | FFmpeg には、リソース管理に関する脆弱性が存在します。 |
| Possible impacts | サービス運用妨害 (DoS) 状態にされる可能性があります。 |
| Solution | ベンダより正式な対策が公開されています。ベンダ情報を参照して適切な対策を実施してください。 |
| Publication Date | Aug. 30, 2017, midnight |
| Registration Date | Sept. 28, 2017, 12:22 p.m. |
| Last Update | Sept. 28, 2017, 12:22 p.m. |
| CVSS3.0 : 警告 | |
| Score | 6.5 |
|---|---|
| Vector | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H |
| CVSS2.0 : 危険 | |
| Score | 7.1 |
|---|---|
| Vector | AV:N/AC:M/Au:N/C:N/I:N/A:C |
| FFmpeg |
| FFmpeg 3.3.3 |
| No | Changed Details | Date of change |
|---|---|---|
| 0 | [2017年09月28日] 掲載 |
Feb. 17, 2018, 10:37 a.m. |
| Summary | In libavformat/mxfdec.c in FFmpeg 3.3.3 -> 2.4, a DoS in mxf_read_index_entry_array() due to lack of an EOF (End of File) check might cause huge CPU consumption. When a crafted MXF file, which claims a large "nb_index_entries" field in the header but does not contain sufficient backing data, is provided, the loop would consume huge CPU resources, since there is no EOF check inside the loop. Moreover, this big loop can be invoked multiple times if there is more than one applicable data segment in the crafted MXF file. |
|---|---|
| Publication Date | Sept. 7, 2017, 3:29 p.m. |
| Registration Date | Jan. 26, 2021, 1:15 p.m. |
| Last Update | Nov. 21, 2024, 12:12 p.m. |
| Configuration1 | or higher | or less | more than | less than | |
| cpe:2.3:a:ffmpeg:ffmpeg:3.3.3:*:*:*:*:*:*:* | |||||