CVE-2021-20318: The HornetQ component of Artemis in EAP 7 was not updated with the fix for CVE-2016-4978.
Noroxi assessment
Priority: Monitor (action score 29/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.7% (FIRST EPSS); higher than 78.1% of all records.
- Anyone who can reach it over the internet can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: eap7-hornetq (Red Hat:jboss_enterprise_application_platform:7.4::el7) 0:2.4.8-1.Final_redhat_00001.1.el7eap; eap7-hornetq-commons (Red Hat:jboss_enterprise_application_platform:7.4::el7) 0:2.4.8-1.Final_redhat_00001.1.el7eap; eap7-hornetq-core-client (Red Hat:jboss_enterprise_application_platform:7.4::el7) 0:2.4.8-1.Final_redhat_00001.1.el7eap.
Low priority for now. Upgrade to eap7-hornetq (Red Hat:jboss_enterprise_application_platform:7.4::el7) 0:2.4.8-1.Final_redhat_00001.1.el7eap; eap7-hornetq-commons (Red Hat:jboss_enterprise_application_platform:7.4::el7) 0:2.4.8-1.Final_redhat_00001.1.el7eap; eap7-hornetq-core-client (Red Hat:jboss_enterprise_application_platform:7.4::el7) 0:2.4.8-1.Final_redhat_00001.1.el7eap or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
The HornetQ component of Artemis in EAP 7 was not updated with the fix for CVE-2016-4978. A remote attacker could use this flaw to execute arbitrary code with the permissions of the application using a JMS ObjectMessage.
- Published
- Dec 23, 2021
- Updated
- Jun 16, 2026
- EPSS
- 1.7% · 78th percentile
- CWE
- CWE-502
Report tools
Action score
29
Monitor
Low priority for now.
- CVSS
- 28 / 40 · 7.2 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 1.7%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| redhat | jboss enterprise application platform | cpe:2.3:a:redhat:jboss_enterprise_application_platform |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- redhat jboss enterprise application platform7.3.9
- redhat jboss enterprise application platform7.4.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.
n/a Artemis in EAP 7
- 7.3.9.GA, 7.4.0.GAaffected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Red Hat:jboss_enterprise_application_platform:7.4::el7 | eap7-hornetq | before 0:2.4.8-1.Final_redhat_00001.1.el7eap | 0:2.4.8-1.Final_redhat_00001.1.el7eap |
| Red Hat:jboss_enterprise_application_platform:7.4::el7 | eap7-hornetq-commons | before 0:2.4.8-1.Final_redhat_00001.1.el7eap | 0:2.4.8-1.Final_redhat_00001.1.el7eap |
| Red Hat:jboss_enterprise_application_platform:7.4::el7 | eap7-hornetq-core-client | before 0:2.4.8-1.Final_redhat_00001.1.el7eap | 0:2.4.8-1.Final_redhat_00001.1.el7eap |
| Red Hat:jboss_enterprise_application_platform:7.4::el7 | eap7-hornetq-jms-client | before 0:2.4.8-1.Final_redhat_00001.1.el7eap | 0:2.4.8-1.Final_redhat_00001.1.el7eap |
| Red Hat:jboss_enterprise_application_platform:7.4::el7 | eap7-undertow | before 0:2.2.13-1.SP2_redhat_00001.1.el7eap | 0:2.2.13-1.SP2_redhat_00001.1.el7eap |
| Red Hat:jboss_enterprise_application_platform:7.4::el8 | eap7-hornetq | before 0:2.4.8-1.Final_redhat_00001.1.el8eap | 0:2.4.8-1.Final_redhat_00001.1.el8eap |
| Red Hat:jboss_enterprise_application_platform:7.4::el8 | eap7-hornetq-commons | before 0:2.4.8-1.Final_redhat_00001.1.el8eap | 0:2.4.8-1.Final_redhat_00001.1.el8eap |
| Red Hat:jboss_enterprise_application_platform:7.4::el8 | eap7-hornetq-core-client | before 0:2.4.8-1.Final_redhat_00001.1.el8eap | 0:2.4.8-1.Final_redhat_00001.1.el8eap |
| Red Hat:jboss_enterprise_application_platform:7.4::el8 | eap7-hornetq-jms-client | before 0:2.4.8-1.Final_redhat_00001.1.el8eap | 0:2.4.8-1.Final_redhat_00001.1.el8eap |
| Red Hat:jboss_enterprise_application_platform:7.4::el8 | eap7-undertow | before 0:2.2.13-1.SP2_redhat_00001.1.el8eap | 0:2.2.13-1.SP2_redhat_00001.1.el8eap |
Same product
redhat: all recordsOther highest-scoring records for the same primary product.
- CVE-2017-12149In Jboss Application Server as shipped with Red Hat Enterprise Application Platform 5.2, it was found that the doFilter method in the…KEV96Now
- CVE-2010-1871JBoss Seam 2 (jboss-seam2), as used in JBoss Enterprise Application Platform 4.3.0 for Red Hat Linux, does not properly sanitize inputs for…KEV90Now
- CVE-2010-1428The Web Console (aka web-console) in JBossAs in Red Hat JBoss Enterprise Application Platform (aka JBoss EAP or JBEAP) 4.2 before…KEV76This week
Published before and after this one in the same product
- ← EarlierCVE-2020-14299Oct 16, 2020 · A flaw was found in JBoss EAP, where the authentication configuration is set-up using a legacy SecurityRealm, to delegate to a legacy…26Monitor
- ← EarlierCVE-2020-14317Jun 2, 2021 · It was found that the issue for security flaw CVE-2019-3805 appeared again in a further version of JBoss Enterprise Application Platform…22Monitor
- Later →CVE-2022-0866May 10, 2022 · This is a concurrency issue that can result in the wrong caller principal being returned from the session context of an EJB that is…21Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| red hat:eap7-hornetq | 0:2.4.8-1.Final_redhat_00001.1.el7eap · Red Hat:jboss_enterprise_application_platform:7.4::el7 | Package registry (OSV) |
| red hat:eap7-hornetq-commons | 0:2.4.8-1.Final_redhat_00001.1.el7eap · Red Hat:jboss_enterprise_application_platform:7.4::el7 | Package registry (OSV) |
| red hat:eap7-hornetq-core-client | 0:2.4.8-1.Final_redhat_00001.1.el7eap · Red Hat:jboss_enterprise_application_platform:7.4::el7 | Package registry (OSV) |
| red hat:eap7-hornetq-jms-client | 0:2.4.8-1.Final_redhat_00001.1.el7eap · Red Hat:jboss_enterprise_application_platform:7.4::el7 | Package registry (OSV) |
| red hat:eap7-undertow | 0:2.2.13-1.SP2_redhat_00001.1.el7eap · Red Hat:jboss_enterprise_application_platform:7.4::el7 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- Administrator privileges are required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-502 · Deserialization of Untrusted DataCVSS vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
Data received over the network is deserialized into the language’s native object format without verifying its source. Code paths inside the object can be triggered during deserialization.
The bug in code
The whole CWE-502 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
payload = sock.recv(65536)
job = pickle.loads(payload)Fixed
payload = sock.recv(65536)
if not hmac.compare_digest(sign(payload), header_sig):
raise PermissionError("invalid signature")
job = JobSchema.validate(json.loads(payload))Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.