Threats / Primetek / CVE-2017-1000486
CVE-2017-1000486
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Primetek Primefaces Application vulnerability
Primetek Primefaces contains a weak encryption vulnerability (CWE-326) that enables remote code execution. The flaw has been actively exploited in the wild.
Verdict
Today item — known-exploited.
An attacker can exploit insufficient cryptographic strength in Primefaces to achieve remote code execution on affected systems. Active exploitation in the wild combined with high EPSS score indicates immediate risk to deployed instances.
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
718 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-01-10).
Probability (EPSS)
EPSS 0.94104 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Primetek, Primefaces Application. Confirm exact fixed builds in the vendor advisory.
Weakness (CWE)
Mapped to CWE-326 Inadequate Encryption Strength — weakness family: Cryptography.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I identify that Primefaces uses weak encryption mechanisms that do not meet current cryptographic standards.
Business
Encryption controls fail to protect sensitive data and application integrity, creating exposure to unauthorized access.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I craft malicious input that exploits the weak encryption to bypass authentication or tamper with protected values.
Business
Security boundaries collapse, allowing attackers to impersonate legitimate users or modify application state.
3
Lateral reach — past segmentation narrative 3
Attacker
I leverage the encryption weakness to inject and execute arbitrary code within the application context.
Business
Complete system compromise occurs, enabling data theft, service disruption, and lateral movement within the infrastructure.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05