CVE-2024-4978 — Justice AV Solutions (JAVS) Viewer Installer Embedded Malicious Code Vulnerability
Justice AV Solutions Viewer Setup 8.3.7.250-1 contains a malicious binary when executed and is signed with an unexpected authenticode signature. A remote, privileged threat actor may exploit this vulnerability to execute of unauthorized PowerShell commands.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- Confirmed exploitation (CISA KEV)+35
- EPSS 26.9% (30-day exploitation probability)+15
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
CISA required action CISA
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
US federal deadline: Jun 19, 2024 — passed 848 day(s) ago
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Javs Javs Viewer, Justice AV Solutions Viewer).
- Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Exploitation requires user interaction: tighten email/web filtering and warn affected users.
- EPSS ahead of 98% of scored CVEs: prioritize it in the patch queue.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Javs | Javs Viewer | version 8.3.7.250 | Vulnerable | NIST National Vulnerability Database |
| Justice AV Solutions | Viewer | version 8.3.7.250 | Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 8.7 | CVSS 4.0 | High | — | — | 9119a7d8-5eab-497f-8521-727c672e3725 via NIST National Vulnerability Database |
| 8.7 | CVSS 4.0 | High | — | — | cisa-cg via CVE Program (cve.org) e CISA ADP |
| 8.4 | CVSS 3.1 | High | 1.7 | 6.0 | 9119a7d8-5eab-497f-8521-727c672e3725 via NIST National Vulnerability Database |
| 8.4 | CVSS 3.1 | High | 1.7 | 6.0 | nvd@nist.gov via NIST National Vulnerability Database |
| 8.4 | CVSS 3.1 | High | — | — | GitHub, Inc. via GitHub Security Advisories |
| 8.4 | CVSS 3.1 | High | — | — | cisa-cg via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
CISA KEV details CISA
CISA lists a CVE once it has evidence of exploitation against real targets.
CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a reference date.
EPSS over time FIRST
Oct 12, 2026 → Oct 14, 2026 · 3 reading(s) · max 26.94%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Hunt retroactively in logs from before May 29, 2024 (KEV listing): exploitation may have started earlier.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · javs/javs viewer
- Source status changed · Published → Analyzed
- Record published
- Affected products added · justice av solutions/viewer
- CVSS changed · 8.4
- Source status changed · → Published
- SSVC assessment updated
- Added to CISA KEV (detected)
- Record created in this database
- 2024
- Added to CISA KEV catalog
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 3× References added · Oct 13, 2026 – Oct 13, 2026
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
8 on the record
- www.cisa.gov/known-exploited-vulnerabilities-catalog
- www.javs.com/downloads
- www.rapid7.com/blog/post/2024/05/23/cve-2024-4978-backdoored-justice-av-solutions-vi
- www.rapid7.com/blog/post/2024/05/23/cve-2024-4978-backdoored-justice-av-solutions-vi
- www.javs.com/downloads/
- github.com/advisories/GHSA-wf54-f8v9-v72v
- twitter.com/2RunJack2/status/1775052981966377148
- nvd.nist.gov/vuln/detail/CVE-2024-4978
Elsewhere on this site
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2024-4978 is "Justice AV Solutions (JAVS) Viewer Installer Embedded Malicious Code Vulnerability", rated High. It affects Javs Viewer (Javs); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 8.4 describes technical severity. EPSS 26.94% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.