{"answers":{"affected":"2 open source packages ship an affected version, including org.bouncycastle:bc-fips. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-45146 in the wild and no public exploit code.","fix":"Upgrade org.bouncycastle:bc-fips to 1.0.2.4 or later.","what":"CVE-2022-45146 is a medium-severity use after free vulnerability in n/a, published on 21 Nov 2022. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-45146 and fix it if it is affected.\n\nWhat it is: CVE-2022-45146 is a medium-severity use after free vulnerability in n/a, published on 21 Nov 2022. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-45146 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.bouncycastle:bc-fips (Maven): affected all versions; fixed in 1.0.2.4\n- org.bouncycastle:bc-fips (Maven): affected all versions; fixed in 1.0.2.4\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-45146/ (Markdown: https://insights.sbomify.com/CVE-2022-45146/index.md)","id":"CVE-2022-45146","markdown":"https://insights.sbomify.com/CVE-2022-45146/index.md","name":"CVE-2022-45146","record":{"aliases":["GHSA-68m8-v89j-7j2p"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Java cryptography library","requires_auth":"low_privilege","summary":"A use-after-free vulnerability in Bouncy Castle FIPS Java API allows temporary keys to be zeroed while in use, potentially causing errors or information loss.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"fips_java_api","vendor":"bouncycastle"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-416","name":"Use After Free"}],"description":"An issue was discovered in the FIPS Java API of Bouncy Castle BC-FJA before 1.0.2.4. Changes to the JVM garbage collector in Java 13 and later trigger an issue in the BC-FJA FIPS modules where it is possible for temporary keys used by the module to be zeroed out while still in use by the module, resulting in errors or potential information loss. NOTE: FIPS compliant users are unaffected because the FIPS certification is only for Java 7, 8, and 11.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Garbage collection issue in BC-FJA in Java 13 and later","id":"CVE-2022-45146","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"use_after_free","year":"2022"},"n_packages":2,"n_references":3,"next":{"headline":"Deserialization in SIMATIC PCS neo V4.0","id":"CVE-2022-45147"},"packages":[{"ecosystem":"Maven","fixed":["1.0.2.4"],"introduced":["0"],"last_affected":[],"package":"org.bouncycastle:bc-fips","purl":null,"source":"GHSA-68m8-v89j-7j2p"},{"ecosystem":"Maven","fixed":["1.0.2.4"],"introduced":["0"],"last_affected":[],"package":"org.bouncycastle:bc-fips","purl":"pkg:maven/org.bouncycastle/bc-fips","source":"GHSA-68m8-v89j-7j2p"}],"prev":{"headline":"Command injection in n/a","id":"CVE-2022-45145"},"products":["n/a"],"published":"2022-11-21","related":[{"cvss_score":5.3,"headline":"Observable Differences in Behavior to Error Inputs in Bouncy Castle","id":"CVE-2020-26939","kev_date_added":null,"published":"2020-11-02"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["n/a"]},"summary":"A use-after-free vulnerability in Bouncy Castle FIPS Java API allows temporary keys to be zeroed while in use, potentially causing errors or information loss.","url":"https://insights.sbomify.com/CVE-2022-45146/"}