CVE-2017-1000486
Crypto Weakness in Primetek Primefaces 4.0 – 4.0.24
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2017-1000486 is a critical-severity Inadequate Encryption Strength (CWE-326) vulnerability in Primetek Primefaces. Its CVSS base score is 9.8 (Critical).
Operationally, ranked in the top 0.2% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog; a public proof-of-concept is referenced.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
Primetek Primefaces 5.x is affected by a weak encryption flaw that results in remote code execution. The issue is identified as CVE-2017-1000486, carries a CVSS v3.1 score of 9.8, and is categorized under CWE-326 for inadequate encryption strength.
The flaw can be exploited by unauthenticated remote attackers over the network with low complexity and no user interaction required. Successful exploitation allows arbitrary code execution that impacts confidentiality, integrity, and availability on the target system.
Public references document the weakness through technical write-ups and include a functional exploit on Exploit-DB along with discussion in the PrimeFaces GitHub issue tracker.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2021-1339
Vulnerability Data
Primetek Primefaces 5.x is vulnerable to a weak encryption flaw resulting in remote code execution
- CWE(s)
- KEV Date Added
- 10 January 2022
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Maintaining currency with technologies and practices reduces selection of encryption mechanisms that provide inadequate strength.
Updated assessments identify when previously adequate encryption strength no longer meets current attack capabilities or compliance drivers.
Establishment procedures require selection and generation of keys with adequate length and strength for the chosen algorithm.
Specifies required cryptography types and parameters, preventing selection of inadequate encryption strength.
Prompt patching corrects inadequate encryption strength when vendors release updates that increase key sizes or algorithm security.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Requiring the organization to define and enforce minimum cryptographic strength prevents deployment of insufficient key lengths or weak ciphers that can be brute-forced.
Hardening callouts derived
DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.
- No fine-grained STIG row for CWE-326, a class-level weakness. Rules are authored against its narrower children: CWE-328.