Skip to content
Fencer Intel
critical 9.8

CVE-2017-1000486 kev in the critical feed json

Inadequate Encryption Strength

published 8y ago modified 4mo ago also GHSA-j239-4gqg-5j54 , EUVD-2021-1339

cvss
9.8
version 3.1, CNA
cisa kev
Exploited
added 2022-01-10
epss
94.1%
EPSS 94.1% chance of exploitation in 30 days, percentile 99.8%
public exploits
2
Metasploit and Exploit-DB, plus a Nuclei check

Summary

Primetek Primefaces 5.x is vulnerable to a weak encryption flaw resulting in remote code execution

Patch / fix

cisa required action Apply updates per vendor instructions.

  • maven org.primefaces:primefaces 6.0
  • primetek primefaces 5.2.21, 5.3.8

Is CVE-2017-1000486 in your dependencies? 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

Timeline

  1. First public exploit (Metasploit exploit/multi/http/primefaces_weak_encryption_rce)
  2. Published
  3. Added to CISA KEV
  4. CISA patch deadline
  5. CISA SSVC: exploitation active

Known exploited

Added
4y ago
Patch by
2022-07-10 (4y ago)
Ransomware
Not known
Required action
Apply updates per vendor instructions.
Vendor, product
Primetek, Primefaces Application
CISA name
Primetek Primefaces Remote Code Execution Vulnerability

CISA SSVC

Exploitation
Active, exploited in the wild
Automatable
yes
Technical impact
total
Assessed
last yr.

Exploit prediction

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

Exploits and checks

CVSS scores

assigned by version score vector
CISA ADP 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P
GitHub 3.0 9.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
maven org.primefaces:primefaces
>=5.0, <6.0
6.0

Classification

Weakness
  • CWE-326 Inadequate Encryption Strength

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.