# CVE-2017-5929: QOS.ch Logback vulnerable to Deserialization of Untrusted Data

> Attackers can execute arbitrary code via unsafe deserialization in Logback's SocketServer and ServerSocketReceiver components.

- **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:** 13 Mar 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-5929, DLA-888-1, GHSA-vmfg-rjjm-rjrj, MGASA-2019-0079, ROOT-APP-MAVEN-CVE-2017-5929, UBUNTU-CVE-2017-5929

## What is CVE-2017-5929?

CVE-2017-5929 is a critical unsafe deserialization vulnerability in Redhat Satellite, published on 13 Mar 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

QOS.ch Logback before 1.2.0 has a serialization vulnerability affecting the SocketServer and ServerSocketReceiver components.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2017-5929?

4 open source packages ship an affected version, including ch.qos.logback:logback-classic and ch.qos.logback:logback-core. It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ch.qos.logback:logback-classic` | Maven | All versions | 1.2.0 |
| `ch.qos.logback:logback-classic` | Maven | All versions | 1.2.0 |
| `ch.qos.logback:logback-core` | Maven | All versions | 1.2.0 |
| `ch.qos.logback:logback-core` | Maven | All versions | 1.2.0 |

Products: Qos Logback, Redhat Satellite, Redhat Satellite Capsule.

## How do I fix CVE-2017-5929?

Upgrade ch.qos.logback:logback-classic to 1.2.0 or later.

## Is CVE-2017-5929 being exploited?

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

## Other vulnerabilities in Redhat Satellite

- [CVE-2023-6481](https://insights.sbomify.com/CVE-2023-6481/): Logback "receiver" DOS vulnerability CVE-2023-6378 incomplete fix (high 7.1)
- [CVE-2023-6378](https://insights.sbomify.com/CVE-2023-6378/): Logback "receiver" DOS vulnerability (high 7.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-5929 and fix it if it is affected.

What it is: CVE-2017-5929 is a critical unsafe deserialization vulnerability in Redhat Satellite, published on 13 Mar 2017. 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-2017-5929 in the wild and no public exploit code.

Affected packages and fixed versions:
- ch.qos.logback:logback-classic (Maven): affected all versions; fixed in 1.2.0
- ch.qos.logback:logback-classic (Maven): affected all versions; fixed in 1.2.0
- ch.qos.logback:logback-core (Maven): affected all versions; fixed in 1.2.0
- ch.qos.logback:logback-core (Maven): affected all versions; fixed in 1.2.0

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-2017-5929/ (Markdown: https://insights.sbomify.com/CVE-2017-5929/index.md)
```

## Sources

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

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