{"answers":{"affected":"4 open source packages ship an affected version, including org.ops4j.pax.logging:pax-logging-log4j2.","exploited":"There is no known exploitation of GHSA-xxfh-x98p-j8fr in the wild and no public exploit code.","fix":"Upgrade org.ops4j.pax.logging:pax-logging-log4j2 to a fixed version for your release line: 1.11.10 or 2.0.11.","what":"GHSA-xxfh-x98p-j8fr is a code injection vulnerability in org.ops4j.pax.logging:pax-logging-log4j2, published on 10 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-xxfh-x98p-j8fr and fix it if it is affected.\n\nWhat it is: GHSA-xxfh-x98p-j8fr is a code injection vulnerability in org.ops4j.pax.logging:pax-logging-log4j2, published on 10 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-xxfh-x98p-j8fr in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.ops4j.pax.logging:pax-logging-log4j2 (Maven): affected all versions; fixed in 1.11.10\n- org.ops4j.pax.logging:pax-logging-log4j2 (Maven): affected all versions; fixed in 1.11.10\n- org.ops4j.pax.logging:pax-logging-log4j2 (Maven): affected from 2.0.0; fixed in 2.0.11\n- org.ops4j.pax.logging:pax-logging-log4j2 (Maven): affected from 2.0.0; fixed in 2.0.11\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-xxfh-x98p-j8fr/ (Markdown: https://insights.sbomify.com/GHSA-xxfh-x98p-j8fr/index.md)","id":"GHSA-xxfh-x98p-j8fr","markdown":"https://insights.sbomify.com/GHSA-xxfh-x98p-j8fr/index.md","name":"GHSA-xxfh-x98p-j8fr","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 remotely via Log4j injection in pax-logging, requiring immediate library upgrades.","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\nRemote Code Execution.\n\n### Patches\nUsers of pax-logging 1.11.9 should update to 1.11.10.\nUsers of pax-logging 2.0.10 should update to 2.0.11.\n\n### Workarounds\nSet system property `-Dlog4j2.formatMsgNoLookups=true`\n\n### References\nhttps://github.com/advisories/GHSA-jfh8-c2jp-5v3q","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":"Remote code injection in Log4j (through pax-logging-log4j2)","id":"GHSA-xxfh-x98p-j8fr","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Maven","product":null,"products":[],"type":"code_injection","year":"2021"},"n_packages":4,"n_references":null,"packages":[{"ecosystem":"Maven","fixed":["1.11.10"],"introduced":["0"],"last_affected":[],"package":"org.ops4j.pax.logging:pax-logging-log4j2","purl":null,"source":"GHSA-xxfh-x98p-j8fr"},{"ecosystem":"Maven","fixed":["1.11.10"],"introduced":["0"],"last_affected":[],"package":"org.ops4j.pax.logging:pax-logging-log4j2","purl":"pkg:maven/org.ops4j.pax.logging/pax-logging-log4j2","source":"GHSA-xxfh-x98p-j8fr"},{"ecosystem":"Maven","fixed":["2.0.11"],"introduced":["2.0.0"],"last_affected":[],"package":"org.ops4j.pax.logging:pax-logging-log4j2","purl":null,"source":"GHSA-xxfh-x98p-j8fr"},{"ecosystem":"Maven","fixed":["2.0.11"],"introduced":["2.0.0"],"last_affected":[],"package":"org.ops4j.pax.logging:pax-logging-log4j2","purl":"pkg:maven/org.ops4j.pax.logging/pax-logging-log4j2","source":"GHSA-xxfh-x98p-j8fr"}],"products":null,"published":"2021-12-10","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 remotely via Log4j injection in pax-logging, requiring immediate library upgrades.","url":"https://insights.sbomify.com/GHSA-xxfh-x98p-j8fr/"}