Artemis-server: artemis-jms-client: artemis-core-client: undertow-core: wildfly-messaging-activemq-subsystem: artemis messaging handlers in red hat eap permit deserialization by default
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. No fixed version is recorded.
EAP's Artemis deserialization configuration permits deserialization by default. ObjectMessage.getObject() uses ObjectInputStreamWithClassLoader, which implements allow-list/block-list filtering via its checkSecurity()/isTrustedType() method. However, by default both allow-list and block-list are empty. When the allow-list is empty (size == 0), isTrustedType() returns true for ALL classes. This means all classes are deserializable by default.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Red Hat | AMQ Broker | ||
| Red Hat | JBoss | ||
| Red Hat | build of Apache Camel 4 for Quarkus | ||
| Red Hat | build of Apache Camel for Spring Boot |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in JBoss, strongest first
Embed
A live severity badge for an advisory, README or ticket