Apache Syncope Vulnerable to Exposure of Sensitive Information Through Data QueriesGHSA-vr35-jm2f-8wg2
MEDIUMGHSA-vr35-jm2f-8wg2 is a medium-severity (CVSS 4.9) CWE-202 vulnerability in org.apache.syncope.core:syncope-core-provisioning-api. A fix is available for org.apache.syncope.core:syncope-core-provisioning-api — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-vr35-jm2f-8wg2.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-vr35-jm2f-8wg2 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 384,189 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
org.apache.syncope.core:syncope-core-provisioning-api☕org.apache.syncope.core:syncope-core-provisioning-api☕org.apache.syncope.core:syncope-core-provisioning-apiReal-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
Exposure of Sensitive Information Through Data Queries vulnerability in Apache Syncope.
An administrator with adequate entitlements for Derived Schemas can create a malicious JEXL expression which allows any administrator with sufficient entitlements for User read to access User-related security-sensitive information.
This issue affects Apache Syncope: 3.0 through 3.0.16, 4.0 through 4.0.5, 4.1.0.
Users are recommended to upgrade to version 4.0.6 / 4.1.1, which fix this issue by further restricting the JEXL expression definition.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.syncope.core:syncope-core-provisioning-api | ≥ 3.0.0-M0 | No fix |
| ☕Maven | org.apache.syncope.core:syncope-core-provisioning-api | ≥ 4.0.0-M0&&< 4.0.6 | 4.0.6org.apache.syncope.core:syncope-core-provisioning-api:4.0.6 |
| ☕Maven | org.apache.syncope.core:syncope-core-provisioning-api | ≥ 4.1.0-M0&&< 4.1.1 | 4.1.1org.apache.syncope.core:syncope-core-provisioning-api:4.1.1 |
Affected Products
syncopeapacheDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.syncope.core:syncope-core-provisioning-api, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
No patched version of org.apache.syncope.core:syncope-core-provisioning-api has shipped for GHSA-vr35-jm2f-8wg2 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
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.
Frequently Asked Questions
Is GHSA-vr35-jm2f-8wg2 in your dependencies?
Find it across Maven, including transitive dependencies.