How severe is GHSA-j7c3-96rf-jrrp?

No CVSS score has been assigned to GHSA-j7c3-96rf-jrrp yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-j7c3-96rf-jrrp?

GHSA-j7c3-96rf-jrrp affects the following packages: de.averbis.textanalysis:pear-archetype (Maven). Ecosystems affected: Maven.

How do I fix GHSA-j7c3-96rf-jrrp?

Update de.averbis.textanalysis:pear-archetype to 2.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j7c3-96rf-jrrp is resolved across your whole dependency graph.

How do I detect GHSA-j7c3-96rf-jrrp in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for de.averbis.textanalysis:pear-archetype. 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-j7c3-96rf-jrrp 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-j7c3-96rf-jrrp?

O3 pinpoints whether GHSA-j7c3-96rf-jrrp 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-j7c3-96rf-jrrp actively exploited in the wild?

No public exploit code has been indexed for GHSA-j7c3-96rf-jrrp 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-j7c3-96rf-jrrp published, and has it been updated?

GHSA-j7c3-96rf-jrrp was published on December 16, 2021 and was last updated on December 16, 2021. 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

GHSA-j7c3-96rf-jrrp

Fix: averbis/pear-archetype@6815f59

GHSA-j7c3-96rf-jrrp is a security vulnerability in de.averbis.textanalysis:pear-archetype. O3 Security confirms whether GHSA-j7c3-96rf-jrrp is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Critical vulnerability in log4j may affect generated PEAR projects

Published

Dec 16, 2021

Updated

Dec 16, 2021

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Dec 16, 2021 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

☕de.averbis.textanalysis:pear-archetype

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

Impact

UIMA PEAR projects that have been generated with the de.averbis.textanalysis:pear-archetype version 2.0.0 have a maven dependency with scope test to log4j 2.8.2 and might be affected by CVE-2021-44228.

Patches

The issue has been resolved in de.averbis.textanalysis:pear-archetype version 2.0.1. Please make sure to use de.averbis.textanalysis:pear-archetype version >= 2.0.1 for generating new PEAR projects.
Existing maven PEAR projects can be patched by manually upgrading to log4j >= 2.16.0 in pom.xml.

References

https://www.lunasec.io/docs/blog/log4j-zero-day/

For more information

If you have any questions or comments about this advisory:

Open an issue in https://github.com/averbis/pear-archetype/issues

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`de.averbis.textanalysis:pear-archetype`	≥ 2.0.0&&< 2.0.1	2.0.1

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for de.averbis.textanalysis:pear-archetype. 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 de.averbis.textanalysis:pear-archetype to 2.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j7c3-96rf-jrrp 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-j7c3-96rf-jrrp 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-j7c3-96rf-jrrp. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact UIMA PEAR projects that have been generated with the `de.averbis.textanalysis:pear-archetype ` version `2.0.0` have a maven dependency with scope `test` to` log4j 2.8.2` and might be affected by CVE-2021-44228. ### Patches - The issue has been resolved in `de.averbis.textanalysis:pear-archetype ` version `2.0.1`. Please make sure to use `de.averbis.textanalysis:pear-archetype ` version >= `2.0.1` for generating new PEAR projects. - Existing maven PEAR projects can be patched by manually upgrading to `log4j` >= `2.16.0` in `pom.xml`. ### References https://www.lunasec.io/docs/blo

O3 Security · Impact-Aware SCA

Is GHSA-j7c3-96rf-jrrp in your dependencies?

O3 detects GHSA-j7c3-96rf-jrrp 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