dbcve.org
SatelliteApplication · Redhat

CVE-2017-5929

CRITICAL · 9.8 CVSS v3.1 Published 2017-03-13
Fix available
A fix is available. Upgrade to 1.2.0 or later.
See remediation →
100/100
Remediation priority · Urgent
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
QOS.ch Logback before 1.2.0 has a serialization vulnerability affecting the SocketServer and ServerSocketReceiver components.

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 · high confidence

Logback versions before 1.2.0 contain a deserialization vulnerability in the SocketServer and ServerSocketReceiver components that accept serialized Java objects over network connections. An unauthenticated remote attacker can send specially crafted serialized payloads to achieve remote code execution.

MitigationUpgrade Logback to version 1.2.0 or later; if immediate upgrade is not feasible, disable SocketServer and ServerSocketReceiver network listeners and ensure they are not exposed to untrusted networks.

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
SatelliteApplication
Affected:= 6.4
Satellite CapsuleApplication
Affected:= 6.4
LogbackApplication
Affected:< 1.2.0

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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
    Locate the logback-core.jar or logback-classic.jar file in your application classpath or dependencies directory, then check its MANIFEST.MF or filename for the version number. In Maven/Gradle projects, run 'mvn dependency:tree' or 'gradle dependencies' and filter for logback to see the resolved version.
    Affected if The installed Logback version is lower than 1.2.0
  2. Locate SocketServer or ServerSocketReceiver configuration
    Search all logback.xml, logback.xml.groovy, logback-test.xml, and any custom configuration files in your application for the <serverSocket> or <server> elements, or for classes 'ch.qos.logback.server.SocketServer' or 'ch.qos.logback.server.ServerSocketReceiver' in <appender> or <listener> definitions.
    Affected if SocketServer or ServerSocketReceiver is explicitly configured in any Logback configuration file
  3. Verify network listener status
    If SocketServer or ServerSocketReceiver is configured, check the configuration for the <port> element and determine which network interface it binds to (0.0.0.0 for all interfaces vs 127.0.0.1 for localhost only). Use 'netstat -an | grep <port>' or 'ss -tlnp | grep <port>' to confirm the port is in LISTEN state.
    Affected if The SocketServer or ServerSocketReceiver is enabled and listening on a non-loopback interface (0.0.0.0 or external IP)
  4. Check Redhat Satellite version
    If running Redhat Satellite or Capsule, run 'satellite-installer --version' or check /usr/share/foreman/lib/satellite/version and compare to 6.4.
    Affected if Redhat Satellite or Capsule version equals exactly 6.4

You are affected if Logback version is below 1.2.0 AND SocketServer or ServerSocketReceiver is configured and listening on a network interface accessible to untrusted users (or Redhat Satellite/Capsule version equals 6.4).

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.0 or later
Fixed in 1.2.0
Interim mitigation

Upgrade Logback to version 1.2.0 or later; if immediate upgrade is not feasible, disable SocketServer and ServerSocketReceiver network listeners and ensure they are not exposed to untrusted networks.

Recommended fix High confidence

Logback 1.2.0 or later (or corresponding Red Hat Satellite 6.4 errata update)

  1. Upgrade Logback library to version 1.2.0 or later in the affected Satellite/Capsule deployment
  2. For Red Hat Satellite 6.4, apply the errata or update that addresses this CVE (RHSA-2017:XXXX or subsequent)
  3. Restart affected services/components (SocketServer, ServerSocketReceiver) after the upgrade to ensure the new Logback version is loaded
  4. Verify the fix by confirming the Logback version in use is 1.2.0 or later: check bundled libraries or runtime classpath for logback-core and logback-classic
Caveat Review release notes for Logback 1.2.0 to check for API compatibility changes; minor version upgrades typically maintain backward compatibility but verify in testing environment first

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

Fix this in Satellite Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-5929 — 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-2017-5929 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