NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
MEDIUM severity

Exposure of Sensitive Information to an Unauthorized Actor in Apache syncope-copeGHSA-v3vf-2r98-xw8w

MEDIUMFix: apache/syncope@44a5ca0

GHSA-v3vf-2r98-xw8w is a medium-severity (CVSS 4.9) Information Exposure vulnerability in org.apache.syncope:syncope-core. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for org.apache.syncope:syncope-core — see the affected versions and patch details below.

Also known asCVE-2018-1322
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
1 known
Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
19.9%probability of exploitation in next 30 days
Moderate Risk0.00%
Lower risk than most CVEs97th percentile — riskier than 97% of all scored CVEsHighest risk
2.60%9.94%17.3%24.6%6.7%19.9%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected
☕org.apache.syncope:syncope-core☕org.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 user search entitlements in Apache Syncope 1.2.x before 1.2.11, 2.0.x before 2.0.8, and unsupported releases 1.0.x and 1.1.x which may be also affected, can recover sensitive security values using the fiql and orderby parameters.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.apache.syncope:syncope-coreall versions1.2.11org.apache.syncope:syncope-core:1.2.11
☕Mavenorg.apache.syncope:syncope-core≥ 2.0.0&&< 2.0.82.0.8org.apache.syncope:syncope-core:2.0.8

Affected Products

1 product · 19 configurations
Application
syncopeapache
≥ 2.0.0 && < 2.0.8
17 versions
1.0.01.0.31.0.41.0.51.0.61.0.71.0.81.0.91.1.01.1.11.1.21.1.3
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

Exploit-DB Source

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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  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-v3vf-2r98-xw8w is resolved across your whole dependency graph.

  3. Workarounds

    Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

An administrator with user search entitlements in Apache Syncope 1.2.x before 1.2.11 and 2.0.x before 2.0.8 can recover sensitive security values using the fiql and orderby parameters.
O3 Security · Impact-Aware SCA

Is GHSA-v3vf-2r98-xw8w in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
Exposure of Sensitive Information to an Unauthorized…