Arbitrary Code Injection Affecting whitedune package, versions *
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-DEBIAN11-WHITEDUNE-517968
- published14 Dec 2017
- disclosed14 Dec 2017
Introduced: 14 Dec 2017
CVE-2017-17518 (opens in a new tab)How to fix?
There is no fixed version for Debian:11 whitedune.
NVD Description
Note: Versions mentioned in the description apply only to the upstream whitedune package and not the whitedune package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
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".