CVE-2016-6298 json
jwcrypto lacks the Random Filling protection mechanism
published 2016-09-01 10 y ago modified 2026-06-17 4 mo ago also GHSA-wg33-x934-3ghh , PYSEC-2016-4 , EUVD-2016-0011
- cvss
- 5.3
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.2%
- EPSS 2.2% chance of exploitation in 30 days, percentile 82%
- public exploits
- 0
- none known
Summary
The _Rsa15 class in the RSA 1.5 algorithm implementation in jwa.py in jwcrypto before 0.3.2 lacks the Random Filling protection mechanism, which makes it easier for remote attackers to obtain cleartext data via a Million Message Attack (MMA).
Patch / fix
- pypi jwcrypto 0.3.2, 0.4.0
- latchset jwcrypto 0.3.2
- python-jwcrypto Debian 14, Debian 13, Debian 12 0.3.2-1
debian advisories DEBIAN-CVE-2016-6298
- github.com/latchset/jwcrypto@eb5be5b commit
- github.com/latchset/jwcrypto#66 pull request
- github.com/latchset/jwcrypto/releases/tag/v0.3.2 release
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2016-6298 updated cvss 3.7
jwcrypto: million messages attack vulnerability
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
2.23% chance of exploitation in the next 30 days, higher than 82% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:P/I:N/A:N |
| GitHub | 3.0 | 5.3 | CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | jwcrypto | <0.3.2 <0.4.0 |
0.3.2 0.4.0 |
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
-
github.com
/latchset/jwcrypto/pull/66
web, issue-tracking, patch
-
github.com
/latchset/jwcrypto/commit/eb5be5bd94c8cae1d7f3ba9801377084d8e5a7ba
web, issue-tracking, patch, vendor-advisory
-
github.com
/latchset/jwcrypto/releases/tag/v0.3.2
web, patch, vendor-advisory
-
github.com
/latchset/jwcrypto/issues/65
web, issue-tracking, vendor-advisory, report
-
securityfocus.com
/bid/92729
vdb-entry, broken-link, third-party-advisory, web
-
nvd.nist.gov
/vuln/detail/CVE-2016-6298
advisory
-
github.com
/latchset/jwcrypto
package
-
github.com
/pypa/advisory-database/tree/main/vulns/jwcrypto/PYSEC-2016-4.yaml
web
-
web.archive.org
/web/20200227230613/http://www.securityfocus.com/bid/92729
web
-
github.com
/advisories/GHSA-wg33-x934-3ghh
advisory
Sources
- CVE List CVE-2016-6298
- GitHub Advisory GHSA-wg33-x934-3ghh
- NVD CVE-2016-6298
- OSV PYSEC-2016-4
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.