{"answers":{"affected":"","exploited":"There is no known exploitation of SUSE-SU-2020:0670-1 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"SUSE-SU-2020:0670-1 is a vulnerability in spacewalk-setup, published on 13 Mar 2020."},"fix_prompt":"Check this codebase for SUSE-SU-2020:0670-1 and fix it if it is affected.\n\nWhat it is: SUSE-SU-2020:0670-1 is a vulnerability in spacewalk-setup, published on 13 Mar 2020. \nExploitation: There is no known exploitation of SUSE-SU-2020:0670-1 in the wild and no public exploit code.\n\nAffected product: spacewalk-setup. 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/SUSE-SU-2020-0670-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2020-0670-1/index.md)","id":"SUSE-SU-2020:0670-1","markdown":"https://insights.sbomify.com/SUSE-SU-2020-0670-1/index.md","name":"SUSE-SU-2020:0670-1","record":{"aliases":[],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["other"],"network_reachable":"unknown","non_default_config":false,"product_category":"SUSE Manager Server","requires_auth":"unknown","summary":"This update fixes an issue where the AJP connector for Tomcat was not created if missing, ensuring proper service configuration.","user_interaction":"unknown","vuln_class":"other"},"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 fixes the following issues:\n\nspacewalk-setup:\n\n- Create AJP connector for tomcat if it does not exist\n  (bsc#1165927, bsc#1166388)\n\nHow to apply this update:\n1. Log in as root user to the SUSE Manager server.\n2. Stop the Spacewalk service:\nspacewalk-service stop\n3. Apply the patch using either zypper patch or YaST Online Update.\n4. Upgrade the database schema:\nspacewalk-schema-upgrade\n5. Start the Spacewalk service:\nspacewalk-service start","ecosystems":["SUSE:Manager Server 3.2"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Recommended update for SUSE Manager Server 3.2","id":"SUSE-SU-2020:0670-1","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2020"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"SUSE:Manager Server 3.2","fixed":["2.8.7.9-3.22.1"],"introduced":["0"],"last_affected":[],"package":"spacewalk-setup","purl":"pkg:rpm/suse/spacewalk-setup\u0026distro=SUSE%20Manager%20Server%203.2","source":"SUSE-SU-2020:0670-1"}],"products":null,"published":"2020-03-13","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"SUSE","prefix":"SUSE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"This update fixes an issue where the AJP connector for Tomcat was not created if missing, ensuring proper service configuration.","url":"https://insights.sbomify.com/SUSE-SU-2020-0670-1/"}