What is GHSA-J7C3-96RF-JRRP?

GHSA-J7C3-96RF-JRRP is a critical-severity security vulnerability in de.averbis.textanalysis:pear-archetype (maven), affecting versions = 2.0.0. It is fixed in 2.0.1.

Which versions of de.averbis.textanalysis:pear-archetype are affected by GHSA-J7C3-96RF-JRRP?

de.averbis.textanalysis:pear-archetype (maven) versions = 2.0.0 is affected.

Is there a fix for GHSA-J7C3-96RF-JRRP?

Yes. GHSA-J7C3-96RF-JRRP is fixed in 2.0.1. Upgrade to this version or later.

Is GHSA-J7C3-96RF-JRRP exploitable, and should I be worried?

Whether GHSA-J7C3-96RF-JRRP is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-J7C3-96RF-JRRP is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix GHSA-J7C3-96RF-JRRP?

Upgrade de.averbis.textanalysis:pear-archetype to 2.0.1 or later.

GHSA-J7C3-96RF-JRRP

Summary

Critical vulnerability in log4j may affect generated PEAR projects

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

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.

Affected versions

de.averbis.textanalysis:pear-archetype (= 2.0.0)

Security releases

de.averbis.textanalysis:pear-archetype → 2.0.1 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

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.

Frequently Asked Questions

What is GHSA-J7C3-96RF-JRRP? GHSA-J7C3-96RF-JRRP is a critical-severity security vulnerability in de.averbis.textanalysis:pear-archetype (maven), affecting versions = 2.0.0. It is fixed in 2.0.1.
Which versions of de.averbis.textanalysis:pear-archetype are affected by GHSA-J7C3-96RF-JRRP? de.averbis.textanalysis:pear-archetype (maven) versions = 2.0.0 is affected.
Is there a fix for GHSA-J7C3-96RF-JRRP? Yes. GHSA-J7C3-96RF-JRRP is fixed in 2.0.1. Upgrade to this version or later.
Is GHSA-J7C3-96RF-JRRP exploitable, and should I be worried? Whether GHSA-J7C3-96RF-JRRP is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-J7C3-96RF-JRRP is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-J7C3-96RF-JRRP? Upgrade de.averbis.textanalysis:pear-archetype to 2.0.1 or later.