How severe is GHSA-p2rp-cmjq-r7wm?

GHSA-p2rp-cmjq-r7wm has a CVSS score of 7.2/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-p2rp-cmjq-r7wm?

GHSA-p2rp-cmjq-r7wm affects the following packages: org.apache.syncope:syncope (Maven). Ecosystems affected: Maven.

How do I fix GHSA-p2rp-cmjq-r7wm?

Update org.apache.syncope:syncope to 2.1.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p2rp-cmjq-r7wm is resolved across your whole dependency graph.

How do I detect GHSA-p2rp-cmjq-r7wm in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.syncope:syncope. 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.

How do I mitigate GHSA-p2rp-cmjq-r7wm if there is no patch (or I can't update yet)?

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 does O3 Security protect against GHSA-p2rp-cmjq-r7wm?

O3 pinpoints whether GHSA-p2rp-cmjq-r7wm is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-p2rp-cmjq-r7wm actively exploited in the wild?

No public exploit code has been indexed for GHSA-p2rp-cmjq-r7wm yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-p2rp-cmjq-r7wm published, and has it been updated?

GHSA-p2rp-cmjq-r7wm was published on June 16, 2021 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

GHSA-p2rp-cmjq-r7wm

HIGH

GHSA-p2rp-cmjq-r7wm is a high-severity (CVSS 7.2) remote code execution vulnerability in org.apache.syncope:syncope. O3 Security confirms whether GHSA-p2rp-cmjq-r7wm is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Shell command injection in Apache Syncope

Also known asCVE-2020-11977

Published

Jun 16, 2021

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 8, 2023 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

☕org.apache.syncope:syncope

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

In Apache Syncope 2.1.X releases prior to 2.1.7, when the Flowable extension is enabled, an administrator with workflow entitlements can use Shell Service Tasks to perform malicious operations, including but not limited to file read, file write, and code execution.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.syncope:syncope`	≥ 2.1.0&&< 2.1.7	2.1.7

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.syncope:syncope. 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:syncope to 2.1.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p2rp-cmjq-r7wm 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-p2rp-cmjq-r7wm 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-p2rp-cmjq-r7wm. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-p2rp-cmjq-r7wm in your dependencies?

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

Scan my dependencies How O3 SCA works