{"answers":{"affected":"2 open source packages ship an affected version, including de.averbis.textanalysis:pear-archetype.","exploited":"There is no known exploitation of GHSA-j7c3-96rf-jrrp in the wild and no public exploit code.","fix":"Upgrade de.averbis.textanalysis:pear-archetype to 2.0.1 or later.","what":"GHSA-j7c3-96rf-jrrp is a code injection vulnerability in de.averbis.textanalysis:pear-archetype, published on 16 Dec 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-j7c3-96rf-jrrp and fix it if it is affected.\n\nWhat it is: GHSA-j7c3-96rf-jrrp is a code injection vulnerability in de.averbis.textanalysis:pear-archetype, published on 16 Dec 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-j7c3-96rf-jrrp in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- de.averbis.textanalysis:pear-archetype (Maven): affected from 2.0.0; fixed in 2.0.1\n- de.averbis.textanalysis:pear-archetype (Maven): affected from 2.0.0; fixed in 2.0.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/GHSA-j7c3-96rf-jrrp/ (Markdown: https://insights.sbomify.com/GHSA-j7c3-96rf-jrrp/index.md)","id":"GHSA-j7c3-96rf-jrrp","markdown":"https://insights.sbomify.com/GHSA-j7c3-96rf-jrrp/index.md","name":"GHSA-j7c3-96rf-jrrp","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Java logging library","requires_auth":"none","summary":"Attackers can execute arbitrary code via Log4j in generated PEAR projects, requiring developers to upgrade the archetype or Log4j dependency.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"### Impact\nUIMA 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.\n\n### Patches\n- 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 \u003e= `2.0.1` for generating new PEAR projects.\n\n- Existing maven PEAR projects can be patched by manually upgrading to `log4j` \u003e= `2.16.0` in `pom.xml`.\n\n### References\nhttps://www.lunasec.io/docs/blog/log4j-zero-day/\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in https://github.com/averbis/pear-archetype/issues","ecosystems":["Maven"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Critical vulnerability in log4j may affect generated PEAR projects","id":"GHSA-j7c3-96rf-jrrp","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Maven","product":null,"products":[],"type":"code_injection","year":"2021"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"Maven","fixed":["2.0.1"],"introduced":["2.0.0"],"last_affected":[],"package":"de.averbis.textanalysis:pear-archetype","purl":null,"source":"GHSA-j7c3-96rf-jrrp"},{"ecosystem":"Maven","fixed":["2.0.1"],"introduced":["2.0.0"],"last_affected":[],"package":"de.averbis.textanalysis:pear-archetype","purl":"pkg:maven/de.averbis.textanalysis/pear-archetype","source":"GHSA-j7c3-96rf-jrrp"}],"products":null,"published":"2021-12-16","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Attackers can execute arbitrary code via Log4j in generated PEAR projects, requiring developers to upgrade the archetype or Log4j dependency.","url":"https://insights.sbomify.com/GHSA-j7c3-96rf-jrrp/"}