{"answers":{"affected":"6 open source packages ship an affected version, including fish.payara.distributions:payara. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-45129 exists.","fix":"Upgrade fish.payara.distributions:payara to a fixed version for your release line: 5.2022.5 or 6.2022.2.","what":"CVE-2022-45129 is a high-severity vulnerability in n/a, published on 10 Nov 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-45129 and fix it if it is affected.\n\nWhat it is: CVE-2022-45129 is a high-severity vulnerability in n/a, published on 10 Nov 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-45129 exists.\n\nAffected packages and fixed versions:\n- fish.payara.distributions:payara (Maven): affected all versions up to 4.1.2.181; no fix listed\n- fish.payara.distributions:payara (Maven): affected all versions up to 4.1.2.181; no fix listed\n- fish.payara.distributions:payara (Maven): affected from 5.0.0.Alpha1; fixed in 5.2022.5\n- fish.payara.distributions:payara (Maven): affected from 5.0.0.Alpha1; fixed in 5.2022.5\n- fish.payara.distributions:payara (Maven): affected from 6.2021.1.Alpha1; fixed in 6.2022.2\n- fish.payara.distributions:payara (Maven): affected from 6.2021.1.Alpha1; fixed in 6.2022.2\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/CVE-2022-45129/ (Markdown: https://insights.sbomify.com/CVE-2022-45129/index.md)","id":"CVE-2022-45129","markdown":"https://insights.sbomify.com/CVE-2022-45129/index.md","name":"CVE-2022-45129","record":{"aliases":["GHSA-q35w-85pq-rv3x"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Payara Application Server","requires_auth":"none","summary":"Attackers can access sensitive META-INF and WEB-INF directories when Payara is deployed to the root context, leading to information disclosure.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"payara","vendor":"payara"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-552","name":"Files or Directories Accessible to External Parties"}],"description":"Payara before 2022-11-04, when deployed to the root context, allows attackers to visit META-INF and WEB-INF, a different vulnerability than CVE-2022-37422. This affects Payara Platform Community before 4.1.2.191.38, 5.x before 5.2022.4, and 6.x before 6.2022.1, and Payara Platform Enterprise before 5.45.0.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Payara, when deployed to the root context, allows attackers to visit META-INF and WEB-INF","id":"CVE-2022-45129","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"information_disclosure","year":"2022"},"n_packages":6,"n_references":7,"next":{"headline":"Cross-site request forgery in n/a","id":"CVE-2022-45130"},"packages":[{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["4.1.2.181"],"package":"fish.payara.distributions:payara","purl":null,"source":"GHSA-q35w-85pq-rv3x"},{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["4.1.2.181"],"package":"fish.payara.distributions:payara","purl":"pkg:maven/fish.payara.distributions/payara","source":"GHSA-q35w-85pq-rv3x"},{"ecosystem":"Maven","fixed":["5.2022.5"],"introduced":["5.0.0.Alpha1"],"last_affected":[],"package":"fish.payara.distributions:payara","purl":null,"source":"GHSA-q35w-85pq-rv3x"},{"ecosystem":"Maven","fixed":["5.2022.5"],"introduced":["5.0.0.Alpha1"],"last_affected":[],"package":"fish.payara.distributions:payara","purl":"pkg:maven/fish.payara.distributions/payara","source":"GHSA-q35w-85pq-rv3x"},{"ecosystem":"Maven","fixed":["6.2022.2"],"introduced":["6.2021.1.Alpha1"],"last_affected":[],"package":"fish.payara.distributions:payara","purl":null,"source":"GHSA-q35w-85pq-rv3x"},{"ecosystem":"Maven","fixed":["6.2022.2"],"introduced":["6.2021.1.Alpha1"],"last_affected":[],"package":"fish.payara.distributions:payara","purl":"pkg:maven/fish.payara.distributions/payara","source":"GHSA-q35w-85pq-rv3x"}],"prev":{"headline":"Missing authorization in Intel(R) EMA software","id":"CVE-2022-45128"},"products":["n/a"],"published":"2022-11-10","related":[{"cvss_score":8.7,"headline":"Payload Injection Attack via Management REST interface","id":"CVE-2024-8215","kev_date_added":null,"published":"2024-10-08"},{"cvss_score":7.5,"headline":"Path Traversal in Payara","id":"CVE-2022-37422","kev_date_added":null,"published":"2022-08-18"},{"cvss_score":7,"headline":"REST Interface Link Redirection via Host parameter","id":"CVE-2024-7312","kev_date_added":null,"published":"2024-09-11"},{"cvss_score":6.8,"headline":"Cross-site Scripting (Stored)","id":"CVE-2025-1534","kev_date_added":null,"published":"2025-04-01"},{"cvss_score":6.1,"headline":"Payara Platform: URL Redirection to untrusted site using FORM authentication","id":"CVE-2023-41699","kev_date_added":null,"published":"2023-11-15"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-05-01","vendors":["n/a"]},"summary":"Attackers can access sensitive META-INF and WEB-INF directories when Payara is deployed to the root context, leading to information disclosure.","url":"https://insights.sbomify.com/CVE-2022-45129/"}