dbcve.org
LogbackApplication · Qos

CVE-2023-6378

HIGH · 7.5 CVSS v3.1 Published 2023-11-29
Fix available
A fix is available. Upgrade to 1.2.13 / 1.3.12 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A serialization vulnerability in logback receiver component part of logback version 1.4.11 allows an attacker to mount a Denial-Of-Service attack by sending poisoned data.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A serialization vulnerability exists in the logback receiver component (version 1.4.11) that allows remote attackers to cause a Denial of Service condition by sending specially crafted poisoned serialized data to the receiver, triggering uncontrolled resource consumption or processing of malicious payload.

MitigationUpgrade logback to the latest patched version (1.4.12 or later) that addresses the serialization vulnerability, and implement network-level controls to restrict access to the logback receiver to trusted sources only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
LogbackApplication
Affected:>= 1.2.0, < 1.2.13>= 1.3.0, < 1.3.12>= 1.4.0, < 1.4.12

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify logback version
    Inspect the logback JAR file in your classpath or examine your dependency management file (Maven pom.xml, Gradle build.gradle) for the logback-core or logback-classic version
    Affected if The version falls within >= 1.2.0 and < 1.2.13, >= 1.3.0 and < 1.3.12, or >= 1.4.0 and < 1.4.12
  2. Locate logback configuration files
    Search for logback.xml, logback-test.xml, or logback.groovy files in your application classpath, config directory, or working directory
    Affected if A configuration file exists and contains a <receiver> element inside the <appender> section defining a network-based log receiver
  3. Verify receiver is bound to network
    In the logback configuration, examine the <serverSocket> or <remoteAppender> element within the receiver to see which network interface it binds to
    Affected if The receiver is configured with a <serverSocket> element and bound to a non-loopback interface (0.0.0.0 or external IP) rather than localhost/127.0.0.1, making it network-accessible
  4. Check runtime exposure
    At runtime, inspect listening network ports on the host running the logback receiver using netstat or similar tools, looking for ports configured in the logback receiver
    Affected if The application has a listening socket accepting remote connections for the logback receiver and is exposed to untrusted networks

You are affected if you are running a logback version within the vulnerable ranges AND have the logback receiver component configured and exposed to network access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.2.13 / 1.3.12 / 1.4.12 or later
Fixed in 1.2.131.3.121.4.12
Interim mitigation

Upgrade logback to the latest patched version (1.4.12 or later) that addresses the serialization vulnerability, and implement network-level controls to restrict access to the logback receiver to trusted sources only.

Recommended fix High confidence

Logback 1.2.13, 1.3.12, or 1.4.12 (depending on your current branch)

  1. 1. Identify the current Logback version in use by checking your project's dependency management (Maven pom.xml, Gradle build.gradle, or JAR manifest)
  2. 2. Based on your current version branch, upgrade to the corresponding fixed release: For 1.2.x line, upgrade to 1.2.13; For 1.3.x line, upgrade to 1.3.12; For 1.4.x line, upgrade to 1.4.12
  3. 3. Update the dependency in your build configuration: For Maven, update the <version> tag in pom.xml; For Gradle, update the version in build.gradle (e.g., implementation 'ch.qos.logback:logback-classic:1.4.12')
  4. 4. Rebuild and test your application to ensure the upgrade does not introduce regressions
  5. 5. If using Logback's receiver component (socket appender), verify that the deserialization vulnerability is mitigated after the upgrade
Caveat Generally minimal risk; Logback maintains backward compatibility within minor version bumps. However, review release notes for any behavioral changes between your current version and the target fixed version.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Logback Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-6378 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-6378 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data