{"answers":{"affected":"","exploited":"There is no known exploitation of openSUSE-SU-2022:0095-1 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"openSUSE-SU-2022:0095-1 is a vulnerability in openSUSE-build-key, published on 30 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for openSUSE-SU-2022:0095-1 and fix it if it is affected.\n\nWhat it is: openSUSE-SU-2022:0095-1 is a vulnerability in openSUSE-build-key, published on 30 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of openSUSE-SU-2022:0095-1 in the wild and no public exploit code.\n\nAffected product: openSUSE-build-key. No package-level version data is available, so check the vendor advisory linked from the reference page.\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/openSUSE-SU-2022-0095-1/ (Markdown: https://insights.sbomify.com/openSUSE-SU-2022-0095-1/index.md)","id":"openSUSE-SU-2022:0095-1","markdown":"https://insights.sbomify.com/openSUSE-SU-2022-0095-1/index.md","name":"openSUSE-SU-2022:0095-1","record":{"aliases":[],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"openSUSE build key","requires_auth":"none","summary":"An update disables a weak 1024-bit RSA build key for the end-of-life SLE11 distribution to prevent potential trust issues.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"This update for openSUSE-build-key fixes the following issues:\n\n- Disabled the SLE11 build key as SLE11 is EOL now, also key was\n  1024bit RSA (removed gpg-pubkey-307e3d54-5aaa90a5.asc)\n  Also obsolete old build key.","ecosystems":["openSUSE:Leap 15.3"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Security update for openSUSE-build-key","id":"openSUSE-SU-2022:0095-1","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2022"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"openSUSE:Leap 15.3","fixed":["1.0-lp153.4.8.1"],"introduced":["0"],"last_affected":[],"package":"openSUSE-build-key","purl":"pkg:rpm/opensuse/openSUSE-build-key\u0026distro=openSUSE%20Leap%2015.3","source":"openSUSE-SU-2022:0095-1"}],"products":null,"published":"2022-03-30","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"SUSE","prefix":"openSUSE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"An update disables a weak 1024-bit RSA build key for the end-of-life SLE11 distribution to prevent potential trust issues.","url":"https://insights.sbomify.com/openSUSE-SU-2022-0095-1/"}