Описание
The mx4200_send function in the legacy MX4200 refclock in NTP before 4.2.8p10 and 4.3.x before 4.3.94 does not properly handle the return value of the snprintf function, which allows local users to execute arbitrary code via unspecified vectors, which trigger an out-of-bounds memory write.
| Релиз | Статус | Примечание |
|---|---|---|
| devel | not-affected | code not compiled |
| esm-infra-legacy/trusty | not-affected | code not compiled |
| esm-infra/xenial | not-affected | code not compiled |
| precise | not-affected | code not compiled |
| trusty | not-affected | code not compiled |
| trusty/esm | not-affected | code not compiled |
| upstream | needs-triage | |
| vivid/stable-phone-overlay | not-affected | code not compiled |
| vivid/ubuntu-core | DNE | |
| xenial | not-affected | code not compiled |
Показывать по
Ссылки на источники
4.6 Medium
CVSS2
7.8 High
CVSS3
Связанные уязвимости
The mx4200_send function in the legacy MX4200 refclock in NTP before 4.2.8p10 and 4.3.x before 4.3.94 does not properly handle the return value of the snprintf function, which allows local users to execute arbitrary code via unspecified vectors, which trigger an out-of-bounds memory write.
The mx4200_send function in the legacy MX4200 refclock in NTP before 4.2.8p10 and 4.3.x before 4.3.94 does not properly handle the return value of the snprintf function, which allows local users to execute arbitrary code via unspecified vectors, which trigger an out-of-bounds memory write.
The mx4200_send function in the legacy MX4200 refclock in NTP before 4 ...
The mx4200_send function in the legacy MX4200 refclock in NTP before 4.2.8p10 and 4.3.x before 4.3.94 does not properly handle the return value of the snprintf function, which allows local users to execute arbitrary code via unspecified vectors, which trigger an out-of-bounds memory write.
4.6 Medium
CVSS2
7.8 High
CVSS3