Vulnerability in logback - Arbitrary Code Execution

logback Updated 02 Oct 2025

Summary

07/04/2017
N/A
Yes i
Unrated
Not published

DLA-888-1: logback - security update. Affects logback versions < 1:1.0.4-1+deb7u1. Fixed in 1:1.0.4-1+deb7u1. How to fix ↓

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

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

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

logback is a flexible logging library for Java that allows developers to easily integrate logging into their applications. It provides various features such as logging levels, log formatting, and log rotation. However, a vulnerability has been discovered in logback that allows for the execution of arbitrary code.

Vulnerability Detail

The vulnerability in logback arises from its deserialization of data from untrusted sockets. This means that an attacker can send malicious data to a logback-enabled application, which can then lead to the execution of arbitrary code. By exploiting this vulnerability, an attacker can potentially gain unauthorized access to the system, manipulate data, or perform other malicious actions.

How To Fix

Minimum fixed version

1:1.0.4-1+deb7u1

This is the first release that contains the fix.

sudo apt-get install --only-upgrade logback

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no known workaround for this vulnerability. It is crucial to update logback to the fixed version to ensure the security of the application.

Conclusion

The vulnerability in logback that allows for arbitrary code execution can be mitigated by upgrading to version 1.0.4-1+deb7u1 or later. It is crucial to promptly update logback to ensure the security of your application. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for logback →

Share this vulnerability

FAQ

logback is a logging library for Java that provides flexible and customizable logging capabilities for applications.

This vulnerability allows an attacker to execute arbitrary code, potentially leading to unauthorized access, data manipulation, or other malicious actions.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability. Simply upload your manifest file (e.g., package-lock.json) and Vulert will analyze it for vulnerabilities in real-time.

No, there is no known workaround for this vulnerability. It is essential to update logback to the fixed version.

You can find more information about this vulnerability in the Debian LTS security advisory DLA-888-1 at https://wiki.debian.org/LTS.

Related vulnerabilities

Recent vulnerabilities recorded for logback.

How To Fix

Minimum fixed version

1:1.0.4-1+deb7u1

This is the first release that contains the fix.

sudo apt-get install --only-upgrade logback

Tip — Not sure which version your app runs? Vulert can match this fix to it. 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