GHSA-73f3-rqqf-2j54
MEDIUMGHSA-73f3-rqqf-2j54 is a medium-severity (CVSS 4.9) XML External Entity (XXE) vulnerability in org.apache.syncope.client.idrepo:syncope-client-idrepo-console. O3 Security confirms whether GHSA-73f3-rqqf-2j54 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Apache Syncope: Console XXE on Keymaster parameters
Real-World Exposure
org.apache.syncope.client.idrepo:syncope-client-idrepo-console☕org.apache.syncope.client.idrepo:syncope-client-idrepo-consoleReal-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
Improper Restriction of XML External Entity Reference vulnerability in Apache Syncope Console. An administrator with adequate entitlements to create or edit Keymaster parameters via Console can construct malicious XML text to launch an XXE attack, thereby causing sensitive data leakage occurs.
This issue affects Apache Syncope: from 3.0 through 3.0.15, from 4.0 through 4.0.3.
Users are recommended to upgrade to version 3.0.16 / 4.0.4, which fix this issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.syncope.client.idrepo:syncope-client-idrepo-console | ≥ 3.0.0&&< 3.0.16 | 3.0.16 |
| ☕Maven | org.apache.syncope.client.idrepo:syncope-client-idrepo-console | ≥ 4.0.0&&< 4.0.4 | 4.0.4 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.syncope.client.idrepo:syncope-client-idrepo-console. 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.
Fix
Update org.apache.syncope.client.idrepo:syncope-client-idrepo-console to 3.0.16 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-73f3-rqqf-2j54 is resolved across your whole dependency graph.
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.
How O3 protects you
O3 pinpoints whether GHSA-73f3-rqqf-2j54 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-73f3-rqqf-2j54. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-73f3-rqqf-2j54 in your dependencies?
O3 detects GHSA-73f3-rqqf-2j54 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.