Wildfly-core: wildfly core: denial of service via malformed payload injection by an authenticated administrative user.

Overview

A flaw was found in wildfly-core. A remote user authenticated as an administrative user can inject a malformed payload into the Inet Address field through the Management Model. This injection causes the server to crash and become unrecoverable, as the payload is written into the standalone.xml configuration file. Manual intervention is required to restore server operation, leading to a denial of service.

Affected

• wildfly-core-security (all versions)
• wildfly-core-security (all versions)
• wildfly-core-security (all versions)
• wildfly-core-security (all versions)
• wildfly-core-security (all versions)
• wildfly-core-security (all versions)

Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.

Workarounds

Restrict network access to the WildFly management interface to trusted hosts only. Configure firewall rules to limit inbound connections to the management port (e.g., 9990) from only authorized IP addresses or subnets. Additionally, ensure that only necessary and trusted administrative users have credentials for the WildFly management console.

Example firewall rule using firewalld on Red Hat Enterprise Linux: firewall-cmd --permanent --add-rich-rule='rule family="ipv4" source address="<TRUSTED_IP_ADDRESS>" port port="9990" protocol="tcp" accept' firewall-cmd --reload

This mitigation limits the attack surface by restricting who can access the administrative interface, thereby reducing the risk of an authenticated administrative user exploiting this vulnerability. Note that applying firewall rules may impact legitimate remote management operations if not configured correctly.