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

GHSA-c438-6f6r-pg8w

HIGH

GHSA-c438-6f6r-pg8w is a high-severity (CVSS 7.5) Server-Side Request Forgery (SSRF) vulnerability in org.fourthline.cling:cling-core. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-c438-6f6r-pg8w is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

4thline cling uPnP protocol issue can lead to denial of service

Also known asCVE-2020-23622
Published
Aug 16, 2022
Updated
Nov 8, 2023
Affected
1 pkg
Patched
None yet
Exploits
1 known

Blast Radius

1 pkg affected
org.fourthline.cling:cling-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

An issue in the UPnP protocol in 4thline cling 2.0.0 through 2.1.2 allows remote attackers to cause a denial of service via an unchecked CALLBACK parameter in the request header. As of 2022, 4thline cling is no longer supported by the maintainers.

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
Mavenorg.fourthline.cling:cling-core2.0.0No fix
Exploits & PoCs
1

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 org.fourthline.cling:cling-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. Remediation status

    No patched version of org.fourthline.cling:cling-core has shipped for GHSA-c438-6f6r-pg8w yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Mitigate without a patch

    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 GHSA-c438-6f6r-pg8w 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 GHSA-c438-6f6r-pg8w. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

An issue in the UPnP protocol in 4thline cling 2.0.0 through 2.1.2 allows remote attackers to cause a denial of service via an unchecked `CALLBACK` parameter in the request header. As of 2022, 4thline cling is no longer supported by the maintainers.
O3 Security · Impact-Aware SCA

Is GHSA-c438-6f6r-pg8w in your dependencies?

O3 detects GHSA-c438-6f6r-pg8w across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.