| Title | NTP および NTPsec の ntpd における時間を制御される脆弱性 |
|---|---|
| Summary | NTP および NTPsec の ntpd には、時間を制御される脆弱性が存在します。 |
| Possible impacts | 攻撃者により、receive() 関数に到達するリファレンスクロック (例えば 127.127.1.1) のソース IP アドレスを持つパケットを介して、時間を制御される可能性があります。 |
| Solution | ベンダ情報および参考情報を参照して適切な対策を実施してください。 |
| Publication Date | April 27, 2016, midnight |
| Registration Date | March 13, 2017, 6:20 p.m. |
| Last Update | March 13, 2017, 6:20 p.m. |
| CVSS3.0 : 低 | |
| Score | 3.7 |
|---|---|
| Vector | CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N |
| CVSS2.0 : 注意 | |
| Score | 2.6 |
|---|---|
| Vector | AV:N/AC:H/Au:N/C:N/I:P/A:N |
| NTP Project |
| NTP 4.2.8p3 |
| NTPsec project |
| NTPsec a5fb34b9cc89b92a8fef2f459004865c93bb7f92 |
| No | Changed Details | Date of change |
|---|---|---|
| 0 | [2017年03月13日] 掲載 |
Feb. 17, 2018, 10:37 a.m. |
| Summary | ntpd in NTP 4.2.8p3 and NTPsec a5fb34b9cc89b92a8fef2f459004865c93bb7f92 relies on the underlying operating system to protect it from requests that impersonate reference clocks. Because reference clocks are treated like other peers and stored in the same structure, any packet with a source ip address of a reference clock (127.127.1.1 for example) that reaches the receive() function will match that reference clock's peer record and will be treated as a trusted peer. Any system that lacks the typical martian packet filtering which would block these packets is in danger of having its time controlled by an attacker. |
|---|---|
| Publication Date | Jan. 28, 2017, 2:59 a.m. |
| Registration Date | Jan. 26, 2021, 2:07 p.m. |
| Last Update | Nov. 21, 2024, 11:46 a.m. |
| Configuration1 | or higher | or less | more than | less than | |
| cpe:2.3:a:ntp:ntp:4.2.8:p3:*:*:*:*:*:* | |||||
| Configuration2 | or higher | or less | more than | less than | |
| cpe:2.3:a:ntpsec:ntpsec:a5fb34b9cc89b92a8fef2f459004865c93bb7f92:*:*:*:*:*:*:* | |||||