Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven

CVE-2021-42550

MEDIUM

CVE-2021-42550 is a medium-severity (CVSS 6.6) Deserialization of Untrusted Data vulnerability in ch.qos.logback:logback-core. 3 public exploit references exist, so weaponization risk is real. O3 Security confirms whether CVE-2021-42550 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Deserialization of Untrusted Data in logback

Also known asGHSA-668q-qrv7-99fm
Published
Dec 16, 2021
Updated
Jul 8, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
3 known

Blast Radius

1 pkg affected
ch.qos.logback:logback-core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

In logback version 1.2.7 and prior versions, an attacker with the required privileges to edit configurations files could craft a malicious configuration allowing to execute arbitrary code loaded from LDAP servers.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
Mavench.qos.logback:logback-coreall versions1.2.9
Exploits & PoCs
3

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ch.qos.logback:logback-core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update ch.qos.logback:logback-core to 1.2.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-42550 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2021-42550 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2021-42550. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

In logback version 1.2.7 and prior versions, an attacker with the required privileges to edit configurations files could craft a malicious configuration allowing to execute arbitrary code loaded from LDAP servers.
O3 Security · Impact-Aware SCA

Is CVE-2021-42550 in your dependencies?

O3 detects CVE-2021-42550 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.