# CVE-2018-8088: Improper Access Control in SLF4J

> Remote attackers can bypass access restrictions in the SLF4J logging library via crafted data, requiring an upgrade to patched versions.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Mar 2018
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2018-8088, GHSA-w77p-8cfg-2x43, RHSA-2018:0582, RHSA-2018:0592, RHSA-2018:0627, RHSA-2018:0628, SUSE-SU-2018:1744-1, openSUSE-SU-2024:11386-1

## What is CVE-2018-8088?

CVE-2018-8088 is a critical unsafe deserialization vulnerability in Redhat Enterprise Linux Desktop, published on 20 Mar 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

org.slf4j.ext.EventData in the slf4j-ext module in QOS.CH SLF4J before 1.8.0-beta2 allows remote attackers to bypass intended access restrictions via crafted data. EventData in the slf4j-ext module in QOS.CH SLF4J, has been fixed in SLF4J versions 1.7.26 later and in the 2.0.x series.

## Which versions are affected by CVE-2018-8088?

4 open source packages ship an affected version, including org.slf4j:slf4j-ext. It affects 13 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.slf4j:slf4j-ext` | Maven | All versions | 1.7.26 |
| `org.slf4j:slf4j-ext` | Maven | All versions | 1.7.26 |
| `org.slf4j:slf4j-ext` | Maven | From 1.8.0-alpha0 | 1.8.0-beta4 |
| `org.slf4j:slf4j-ext` | Maven | From 1.8.0-alpha0 | 1.8.0-beta4 |
| `slf4j` | Red Hat:enterprise_linux:7::client | All versions | 0:1.7.4-4.el7_4 |
| `slf4j-javadoc` | Red Hat:enterprise_linux:7::client | All versions | 0:1.7.4-4.el7_4 |
| `slf4j-manual` | Red Hat:enterprise_linux:7::client | All versions | 0:1.7.4-4.el7_4 |
| `slf4j` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.7.4-4.el7_4 |
| `slf4j-javadoc` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.7.4-4.el7_4 |
| `slf4j-manual` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.7.4-4.el7_4 |
| `slf4j` | Red Hat:enterprise_linux:7::server | All versions | 0:1.7.4-4.el7_4 |
| `slf4j-javadoc` | Red Hat:enterprise_linux:7::server | All versions | 0:1.7.4-4.el7_4 |
| `slf4j-manual` | Red Hat:enterprise_linux:7::server | All versions | 0:1.7.4-4.el7_4 |
| `slf4j` | Red Hat:enterprise_linux:7::workstation | All versions | 0:1.7.4-4.el7_4 |
| `slf4j-javadoc` | Red Hat:enterprise_linux:7::workstation | All versions | 0:1.7.4-4.el7_4 |
| `slf4j-manual` | Red Hat:enterprise_linux:7::workstation | All versions | 0:1.7.4-4.el7_4 |
| `slf4j` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:1.7.2-14.redhat_4.1.ep6.el5 |
| `slf4j-eap6` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:1.7.2-14.redhat_4.1.ep6.el5 |
| `slf4j-eap6` | Red Hat:jboss_enterprise_application_platform:6::el6 | All versions | 0:1.7.2-14.redhat_4.1.ep6.el6 |
| `slf4j-eap6` | Red Hat:jboss_enterprise_application_platform:6::el7 | All versions | 0:1.7.2-14.redhat_4.1.ep6.el7 |
| `eap7-jcl-over-slf4j` | Red Hat:jboss_enterprise_application_platform:7.1::el7 | All versions | 0:1.7.22-3.redhat_2.1.ep7.el7 |
| `eap7-slf4j` | Red Hat:jboss_enterprise_application_platform:7.1::el7 | All versions | 0:1.7.22-3.redhat_2.1.ep7.el7 |
| `eap7-slf4j-api` | Red Hat:jboss_enterprise_application_platform:7.1::el7 | All versions | 0:1.7.22-3.redhat_2.1.ep7.el7 |
| `eap7-slf4j-ext` | Red Hat:jboss_enterprise_application_platform:7.1::el7 | All versions | 0:1.7.22-3.redhat_2.1.ep7.el7 |
| `eap7-jcl-over-slf4j` | Red Hat:jboss_enterprise_application_platform:7::el6 | All versions | 0:1.7.22-3.redhat_2.1.ep7.el6 |
| `eap7-slf4j` | Red Hat:jboss_enterprise_application_platform:7::el6 | All versions | 0:1.7.22-3.redhat_2.1.ep7.el6 |
| `eap7-slf4j-api` | Red Hat:jboss_enterprise_application_platform:7::el6 | All versions | 0:1.7.22-3.redhat_2.1.ep7.el6 |
| `eap7-slf4j-ext` | Red Hat:jboss_enterprise_application_platform:7::el6 | All versions | 0:1.7.22-3.redhat_2.1.ep7.el6 |
| `rh-maven35-jcl-over-slf4j` | Red Hat:rhel_software_collections:3::el7 | All versions | 0:1.7.25-1.3.el7 |
| `rh-maven35-jul-to-slf4j` | Red Hat:rhel_software_collections:3::el7 | All versions | 0:1.7.25-1.3.el7 |
| `rh-maven35-log4j-over-slf4j` | Red Hat:rhel_software_collections:3::el7 | All versions | 0:1.7.25-1.3.el7 |
| `rh-maven35-slf4j` | Red Hat:rhel_software_collections:3::el7 | All versions | 0:1.7.25-1.3.el7 |
| `rh-maven35-slf4j-ext` | Red Hat:rhel_software_collections:3::el7 | All versions | 0:1.7.25-1.3.el7 |
| `rh-maven35-slf4j-javadoc` | Red Hat:rhel_software_collections:3::el7 | All versions | 0:1.7.25-1.3.el7 |
| `rh-maven35-slf4j-jcl` | Red Hat:rhel_software_collections:3::el7 | All versions | 0:1.7.25-1.3.el7 |
| `rh-maven35-slf4j-jdk14` | Red Hat:rhel_software_collections:3::el7 | All versions | 0:1.7.25-1.3.el7 |
| `rh-maven35-slf4j-log4j12` | Red Hat:rhel_software_collections:3::el7 | All versions | 0:1.7.25-1.3.el7 |
| `rh-maven35-slf4j-manual` | Red Hat:rhel_software_collections:3::el7 | All versions | 0:1.7.25-1.3.el7 |
| `rh-maven35-slf4j-sources` | Red Hat:rhel_software_collections:3::el7 | All versions | 0:1.7.25-1.3.el7 |
| `slf4j` | SUSE:HPE Helion OpenStack 8 | All versions | 1.7.12-3.3.1 |

Products: Oracle Goldengate Application Adapters, Oracle Goldengate Stream Analytics, Oracle Utilities Framework, Qos Slf4j, Redhat Enterprise Linux Desktop, Redhat Enterprise Linux Eus, Redhat Enterprise Linux Server, Redhat Enterprise Linux Server Aus, Redhat Enterprise Linux Server Tus, Redhat Enterprise Linux Workstation, Redhat Jboss Enterprise Application Platform, Redhat Virtualization, Redhat Virtualization Host.

## How do I fix CVE-2018-8088?

Upgrade org.slf4j:slf4j-ext to a fixed version for your release line: 1.7.26 or 1.8.0-beta4.

## Is CVE-2018-8088 being exploited?

There is no known exploitation of CVE-2018-8088 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-8088 and fix it if it is affected.

What it is: CVE-2018-8088 is a critical unsafe deserialization vulnerability in Redhat Enterprise Linux Desktop, published on 20 Mar 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-8088 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.slf4j:slf4j-ext (Maven): affected all versions; fixed in 1.7.26
- org.slf4j:slf4j-ext (Maven): affected all versions; fixed in 1.7.26
- org.slf4j:slf4j-ext (Maven): affected from 1.8.0-alpha0; fixed in 1.8.0-beta4
- org.slf4j:slf4j-ext (Maven): affected from 1.8.0-alpha0; fixed in 1.8.0-beta4

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-8088/ (Markdown: https://insights.sbomify.com/CVE-2018-8088/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-8088
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-8088
- OSV: https://osv.dev/vulnerability/CVE-2018-8088

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-8088/
Summaries are generated and may contain mistakes; the official description above is the record.
