Red Hat JBoss Enterprise Application Platform 8.1 · Red Hat JBoss Enterprise Application Platform 7 · Red Hat JBoss Enterprise Application Platform Expansion Pack · Red Hat Single Sign-On 7
| Product | Affected | Fixed in |
|---|---|---|
| Red Hat Red Hat JBoss Enterprise Application Platform 8.1 | — | No fix yet |
| Red Hat Red Hat JBoss Enterprise Application Platform 7 | — | No fix yet |
| Red Hat Red Hat JBoss Enterprise Application Platform 7 | — | No fix yet |
| Red Hat Red Hat JBoss Enterprise Application Platform 7 | — | No fix yet |
| Red Hat Red Hat JBoss Enterprise Application Platform 7 | — | No fix yet |
| Red Hat Red Hat JBoss Enterprise Application Platform 7 | — | No fix yet |
| Red Hat Red Hat JBoss Enterprise Application Platform 7 | — | No fix yet |
| Red Hat Red Hat JBoss Enterprise Application Platform Expansion Pack | — | No fix yet |
| Red Hat Red Hat Single Sign-On 7 | — | No fix yet |
A path traversal flaw was found in WildFly's domain mode implementation. The LocalFileRepository.getFile() and getConfigurationFile() methods in wildfly-core/deployment-repository do not validate that the resolved file path remains within the configured repository or configuration root directories. A remote attacker who has obtained the slave host controller secret or compromised a slave host controller can supply a crafted relative path containing directory traversal sequences (e.g., ../../etc/passwd) via the slave-DC wire protocol, causing the Domain Controller to resolve and serve arbitrary files readable by the DC process. This leads to unauthorized disclosure of sensitive information such as configuration files, keystores, and system credentials.
From the CVE record · redhat
WildFly’s domain mode deployment repository does not ensure requested files stay within its configured directories. A remote attacker with the slave host controller secret, or control of a slave host controller, can send a crafted path over the slave-DC wire protocol and obtain files readable by the Domain Controller process.
Teams running Red Hat JBoss Enterprise Application Platform 8.1 or 7, Red Hat JBoss Enterprise Application Platform Expansion Pack, or Red Hat Single Sign-On 7 should check their deployments.