Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 9.8

Deserialization of Untrusted Data in Log4j

CVE-2019-17571GHSA-2qrg-x229-3v8q

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Maven org.zenframework.z8.dependencies.commons:log4j-1.2.17

    Affected
    >= 2.0, <= 2.0
    Fixed in
    no fixed version recorded

  • Maven log4j:log4j

    Affected
    >= 1.2, <= 1.2.17
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
9.8 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
  • CVE-2019-17571: 69.98% estimated exploitation activity in the next 30 days; percentile 99.38 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Included in Log4j 1.2 is a SocketServer class that is vulnerable to deserialization of untrusted data which can be exploited to remotely execute arbitrary code when combined with a deserialization gadget when listening to untrusted network traffic for log data. This affects Log4j versions 1.2 up to 1.2.17. Users are advised to migrate to org.apache.logging.log4j:log4j-core.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-2qrg-x229-3v8q

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2019-17571

Advisory: Deserialization of Untrusted Data in Log4j
IDs: CVE-2019-17571, GHSA-2qrg-x229-3v8q
Record: https://patchnext.com/advisories/cve-2019-17571 (revision 1, source checked 26 Oct 2026, 16:45 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.zenframework.z8.dependencies.commons:log4j-1.2.17: affected >= 2.0, <= 2.0
- Maven log4j:log4j: affected >= 1.2, <= 1.2.17

## Suggested inspection (read-only)
- Maven org.zenframework.z8.dependencies.commons:log4j-1.2.17: check the installed version with your package manager.
- Maven log4j:log4j: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.zenframework.z8.dependencies.commons:log4j-1.2.17, log4j:log4j.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-2qrg-x229-3v8q (GitHub-reviewed advisory GHSA-2qrg-x229-3v8q lists affected ranges: Maven log4j:log4j >=1.2 =2.0 <=2.0)

Commands are suggestions: review each one before running it.

Loading voting…