ifup & ifdown crash if multiple interfaces are listed in no-scripts
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ifupdown (Debian) |
Fix Released
|
Unknown
|
|||
ifupdown (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Xenial |
Fix Released
|
High
|
Unassigned |
Bug Description
[Impact]
ifup and ifupdown segfault if multiple interfaces are listed in no-scripts
This is a trivially reproducible crash in ifup/ifdown, with a patch attached.
[Test Case]
Steps to reproduce:
1) echo no-scripts foo bar >> /etc/network/
2) ifup baz
Expected results:
Unknown interface baz
Actual results:
Segmentation fault (core dumped)
It's irrelevant whether the second interface is on the same no-scripts line or separate one. This will crash just the same:
echo no-scripts foo >> /etc/network/
echo no-scripts bar >> /etc/network/
[Regression potential]
Seems slight. The patch fixes a clear bug in code that is only used to process the no-scripts (and apparently no-auto-down) stanzas.
tags: | added: patch |
Changed in ifupdown (Ubuntu): | |
importance: | Undecided → High |
tags: | added: xenial yakkety |
Changed in ifupdown (Ubuntu): | |
status: | New → Fix Committed |
Changed in ifupdown (Ubuntu Xenial): | |
status: | New → In Progress |
Changed in ifupdown (Ubuntu Xenial): | |
importance: | Undecided → High |
Changed in ifupdown (Debian): | |
status: | Unknown → New |
Changed in ifupdown (Debian): | |
status: | New → Fix Released |
Fun. This bug affects Debian too it seems, I'll forward it along there unless you have already?