Skip to content
Fencer Intel
high 7.8

CVE-2019-11696 json

Files with the .JNLP extension used for "Java web start" applications are not treated as executable content for download prompts even thoug…

published 7y ago modified 4mo ago also EUVD-2019-3366

cvss
7.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 58%
public exploits
0
none known

Summary

Files with the .JNLP extension used for "Java web start" applications are not treated as executable content for download prompts even though they can be executed if Java is installed on the local system. This could allow users to mistakenly launch an executable binary locally. This vulnerability affects Firefox < 67.

Patch / fix

  • Mozilla Firefox 67
  • firefox Ubuntu 16.04 LTS 67.0+build2-0ubuntu0.16.04.1
  • firefox Ubuntu 18.04 LTS 67.0+build2-0ubuntu0.18.04.1

ubuntu advisories UBUNTU-CVE-2019-11696

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • firefox-esr openSUSE Tumbleweed 128.5.1-1.1
  • MozillaFirefox openSUSE Tumbleweed 92.0-1.2

opensuse advisories openSUSE-SU-2024:14572-1openSUSE-SU-2024:10600-1

  • firefox Arch Linux 67.0-1

arch linux advisories AVG-966

Is CVE-2019-11696 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.84% chance of exploitation in the next 30 days, higher than 58% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • bugzilla.mozilla.org https://bugzilla.mozilla.org/show_bug.cgi?id=1392955 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.0 7.8 CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P

Affected products

  • Mozilla Firefox

Classification

Weakness
  • CWE-20 Improper Input Validation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.