| Title | Cisco Sourcefire Snort におけるリソース管理に関する脆弱性 |
|---|---|
| Summary | Cisco Sourcefire Snort には、リソース管理に関する脆弱性が存在します。 |
| Possible impacts | サービス運用妨害 (DoS) 状態にされる可能性があります。 |
| Solution | ベンダ情報および参考情報を参照して適切な対策を実施してください。 |
| Publication Date | May 15, 2017, midnight |
| Registration Date | June 16, 2017, 4:57 p.m. |
| Last Update | June 16, 2017, 4:57 p.m. |
| CVSS3.0 : 重要 | |
| Score | 7.5 |
|---|---|
| Vector | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| CVSS2.0 : 警告 | |
| Score | 5 |
|---|---|
| Vector | AV:N/AC:L/Au:N/C:N/I:N/A:P |
| シスコシステムズ |
| Snort++ |
| No | Changed Details | Date of change |
|---|---|---|
| 0 | [2017年06月16日] 掲載 |
Feb. 17, 2018, 10:37 a.m. |
| Summary | Cisco Sourcefire Snort 3.0 before build 233 mishandles Ether Type Validation. Since valid ether type and IP protocol numbers do not overlap, Snort++ stores all protocol decoders in a single array. That makes it possible to craft packets that have IP protocol numbers in the ether type field which will confuse the Snort++ decoder. For example, an eth:llc:snap:icmp6 packet will cause a crash because there is no ip6 header with which to calculate the icmp6 checksum. Affected decoders include gre, llc, trans_bridge, ciscometadata, linux_sll, and token_ring. The fix adds a check in the packet manager to validate the ether type before indexing the decoder array. An out of range ether type will raise 116:473. |
|---|---|
| Publication Date | May 17, 2017, 2:29 a.m. |
| Registration Date | Jan. 26, 2021, 1:27 p.m. |
| Last Update | Nov. 21, 2024, 12:30 p.m. |
| Configuration1 | or higher | or less | more than | less than | |
| cpe:2.3:a:cisco:snort\+\+:-:*:*:*:*:*:*:* | |||||