swt/motif/browser.c in White_dune (aka whitedune) 0.30.10 does not validate strings before launching the program specified by the BROWSER environment variable, which might allow remote attackers to conduct argument-injection attacks via a crafted URL. NOTE: This issue is being disputed as not being a vulnerability because “the current version of white_dune (1.369 at https://wdune.ourproject.org/) do not use a BROWSER environment variable. Instead, the browser variable is read from the $HOME/.dunerc file (or from the M$Windows registry). It is configurable in the options menu. The default is chosen in the ./configure script, which tests various programs, first tested is xdg-open.
The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| White_dune | White_dune_project | 0.30.10 (including) | 0.30.10 (including) |
| Whitedune | Ubuntu | artful | * |
| Whitedune | Ubuntu | bionic | * |
| Whitedune | Ubuntu | cosmic | * |
| Whitedune | Ubuntu | disco | * |
| Whitedune | Ubuntu | eoan | * |
| Whitedune | Ubuntu | groovy | * |
| Whitedune | Ubuntu | hirsute | * |
| Whitedune | Ubuntu | impish | * |
| Whitedune | Ubuntu | kinetic | * |
| Whitedune | Ubuntu | lunar | * |
| Whitedune | Ubuntu | mantic | * |
| Whitedune | Ubuntu | trusty | * |
| Whitedune | Ubuntu | upstream | * |
| Whitedune | Ubuntu | xenial | * |
| Whitedune | Ubuntu | zesty | * |