CVE-2025-23368: Org.wildfly.core:wildfly-elytron-integration: wildfly elytron brute force attack via cli

Published Jan 14, 2025
·
Updated

Impact

A flaw was found in Wildfly Elytron integration. The component does not implement sufficient measures to prevent multiple failed authentication attempts within a short time frame, making it more susceptible to brute force attacks via CLI.

Patches

The default behaviour has been changed in WildFly Core 31.0.3.Final, and 32.0.0.Beta3 - the first version is used by WildFly 39.0.1.Final and the second will be included in WildFly 40.

Workarounds

No direct workaround. Monitoring network traffic / blocking suspicious traffic may help.

References

https://www.cve.org/CVERecord?id=CVE-2025-23368 https://issues.redhat.com/browse/WFCORE-7192

Acknowledgements

We would like to thank Claudia Bartolini (TIM S.p.A), Marco Ventura (TIM S.p.A), and Massimiliano Brolli (TIM S.p.A) for reporting this issue.

Other sources

The product does not implement sufficient measures to prevent multiple failed authentication attempts within a short time frame, making it more susceptible to brute force attacks via CLI.

Network access to any of WildFly or JBoss EAP’s exposed ports which require either HTTP or SASL authentication.

Red Hat

Affected Software

8 affected componentsFixes available
WildFly Elytron Integration
maven/org.wildfly.core:wildfly-elytron-integration<=27.0.0.Final
redhat WildFly Core<31.0.3
redhat Data Grid=8.0
redhat JBoss Enterprise Application Platform=7.0.0
redhat JBoss Enterprise Application Platform=8.0.0
maven/org.wildfly.core:wildfly-elytron-integration<31.0.3.Final
31.0.3.Final
maven/org.wildfly.core:wildfly-elytron-integration>=32.0.0.Beta1<32.0.0.Beta3
32.0.0.Beta3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade maven/org.wildfly.core:wildfly-elytron-integration to a version that resolves this vulnerability.

    Fixed in 31.0.3.Final
  2. Upgrade

    Upgrade maven/org.wildfly.core:wildfly-elytron-integration to a version that resolves this vulnerability.

    Fixed in 32.0.0.Beta3
  3. Upgrade

    Upgrade Org.wildfly.core:wildfly-elytron-integration to a version that resolves this vulnerability.

    Fixed in 31.0.3.Final
  4. Upgrade

    Upgrade Org.wildfly.core:wildfly-elytron-integration to a version that resolves this vulnerability.

    Fixed in 32.0.0.Beta3
  5. Compensating control

    Monitor network traffic and block suspicious traffic targeting WildFly or JBoss EAP exposed ports that require HTTP or SASL authentication.

Event History

Jan 14, 2025
Data Sourced
via Red Hat·03:39 PM
DescriptionSeverityAffected Software
Mar 4, 2025
CVE Published
via MITRE·03:14 PM
Data Sourced
via MITRE·03:14 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·04:15 PM
DescriptionSeverityWeaknessAffected Software
Advisory Published
via GitHub·06:33 PM
Feb 13, 2026
Advisory Published
via GitHub·08:52 PM
Data Sourced
via GitHub·08:52 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-23368?

CVE-2025-23368 is considered a medium severity vulnerability due to its potential for exploitation through brute force attacks.

2

How do I fix CVE-2025-23368?

To fix CVE-2025-23368, implement rate limiting for authentication attempts in WildFly Elytron integration to prevent brute force attacks.

3

What versions of WildFly Elytron integration are affected by CVE-2025-23368?

CVE-2025-23368 affects versions of WildFly Elytron integration up to and including 27.0.0.Final.

4

Can CVE-2025-23368 lead to unauthorized access?

Yes, CVE-2025-23368 can lead to unauthorized access if an attacker successfully exploits the vulnerability through brute force methods.

5

Is there a workaround for CVE-2025-23368?

A possible workaround for CVE-2025-23368 is to manually configure security settings to limit authentication attempts until an official patch is applied.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203