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

GHSA-xgc9-9w4v-h33h

HIGH

High severity vulnerability that affects org.apache.syncope:syncope-core

Also known asCVE-2018-1321
Published
Nov 6, 2018
Updated
Mar 4, 2024
Affected
2 pkgs
Patched
2 / 2
Exploits
1 known

Blast Radius

2 pkgs affected
org.apache.syncope:syncope-coreorg.apache.syncope:syncope-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 administrator with report and template entitlements in Apache Syncope 1.2.x before 1.2.11 and 2.0.x before 2.0.8 can use XSL Transformations (XSLT) to perform malicious operations, including but not limited to file read, file write, and code execution.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
Mavenorg.apache.syncope:syncope-coreall versions1.2.11
Mavenorg.apache.syncope:syncope-core2.0.0&&< 2.0.82.0.8
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.

EDB-45400webappswindows

Apache Syncope 2.0.7 - Remote Code Execution

by Che-Chun Kuo · Sep 13, 2018

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.apache.syncope:syncope-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 org.apache.syncope:syncope-core to 1.2.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xgc9-9w4v-h33h 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 GHSA-xgc9-9w4v-h33h 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-xgc9-9w4v-h33h. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

An administrator with report and template entitlements in Apache Syncope 1.2.x before 1.2.11 and 2.0.x before 2.0.8 can use XSL Transformations (XSLT) to perform malicious operations, including but not limited to file read, file write, and code execution.
O3 Security · Impact-Aware SCA

Is GHSA-xgc9-9w4v-h33h in your dependencies?

O3 detects GHSA-xgc9-9w4v-h33h across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.