CVE-2017-7822 json
The AES-GCM implementation in WebCrypto API accepts 0-length IV when it should require a length of 1 according to the NIST Special Publicat…
published 2018-06-11 8 y ago modified 2026-06-17 4 mo ago also EUVD-2017-16797
- cvss
- 5.3
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.3%
- EPSS 1.3% chance of exploitation in 30 days, percentile 71%
- public exploits
- 0
- none known
Summary
The AES-GCM implementation in WebCrypto API accepts 0-length IV when it should require a length of 1 according to the NIST Special Publication 800-38D specification. This might allow for the authentication key to be determined in some instances. This vulnerability affects Firefox < 56.
Patch / fix
- Mozilla Firefox 56
- firefox Ubuntu 14.04 LTS 56.0+build6-0ubuntu0.14.04.1
- firefox Ubuntu 16.04 LTS 56.0+build6-0ubuntu0.16.04.1
- firefox Ubuntu 18.04 LTS 56.0+build6-0ubuntu1
ubuntu advisories UBUNTU-CVE-2017-7822
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
Exploit prediction
1.33% chance of exploitation in the next 30 days, higher than 71% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 5.3 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Affected products
- Mozilla Firefox
References
-
mozilla.org
/security/advisories/mfsa2017-21/
vendor-advisory
-
securitytracker.com
/id/1039465
vdb-entry, third-party-advisory
-
bugzilla.mozilla.org
/show_bug.cgi?id=1368859
issue-tracking
-
securityfocus.com
/bid/101057
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2017-7822
- NVD CVE-2017-7822
Fencer Vulns 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.