CVE-2018-8088: Improper Access Control in SLF4J

org.slf4j:slf4j-ext Updated 02 Oct 2025

Summary

13/05/2022
Yes i
Critical
9.8

CVE-2018-8088: Improper Access Control in SLF4J. Affects org.slf4j:slf4j-ext across 2 version ranges.

< 1.7.26 >= 1.8.0-alpha0, < 1.8.0-beta4

Fixed in 1.7.26 or 1.8.0-beta4, depending on the release line you run. How to fix ↓

Also tracked for

The same CVE-2018-8088 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

SLF4J is a logging facade for Java applications, providing a simple and efficient way to log messages. The slf4j-ext module in QOS.CH SLF4J is an extension that allows for additional functionality. However, versions of SLF4J prior to 1.7.26 and 2.0.x series are vulnerable to an improper access control issue in the org.slf4j.ext.EventData class. This vulnerability can be exploited by remote attackers to bypass intended access restrictions by sending crafted data.

Vulnerability Detail

The vulnerability in SLF4J allows remote attackers to bypass access restrictions by exploiting the improper access control issue in the org.slf4j.ext.EventData class. This can lead to unauthorized access to sensitive information or the execution of arbitrary code. The vulnerability has a CVSS score of 9.8, indicating its critical severity.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • < 1.7.26 1.7.26
  • >= 1.8.0-alpha0, < 1.8.0-beta4 1.8.0-beta4

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Workaround

There is no known workaround for this vulnerability. It is necessary to upgrade to the fixed version of SLF4J to mitigate the risk.

Conclusion

The vulnerability in SLF4J can be mitigated by upgrading to the fixed version of the library. It is recommended to update the SLF4J dependency in the project's pom.xml file to version 1.7.26 or later, or the 2.0.x series. For further assistance or support in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for org.slf4j:slf4j-ext →

Share this vulnerability

FAQ

SLF4J is a logging facade for Java applications that provides a simple and efficient way to log messages.

The slf4j-ext module in QOS.CH SLF4J is an extension that allows for additional functionality beyond the core SLF4J library.

The vulnerability can be exploited by remote attackers who send crafted data to the org.slf4j.ext.EventData class, bypassing intended access restrictions.

Exploiting this vulnerability can lead to unauthorized access to sensitive information or the execution of arbitrary code.

The CVSS score of this vulnerability is 9.8, indicating its critical severity.

References

View More

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • < 1.7.26 1.7.26
  • >= 1.8.0-alpha0, < 1.8.0-beta4 1.8.0-beta4

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback