{"answers":{"affected":"","exploited":"There is no known exploitation of SUSE-SU-2018:2902-2 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"SUSE-SU-2018:2902-2 is a vulnerability in yast2-smt, published on 18 Oct 2018."},"fix_prompt":"Check this codebase for SUSE-SU-2018:2902-2 and fix it if it is affected.\n\nWhat it is: SUSE-SU-2018:2902-2 is a vulnerability in yast2-smt, published on 18 Oct 2018. \nExploitation: There is no known exploitation of SUSE-SU-2018:2902-2 in the wild and no public exploit code.\n\nAffected product: yast2-smt. 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-2018-2902-2/ (Markdown: https://insights.sbomify.com/SUSE-SU-2018-2902-2/index.md)","id":"SUSE-SU-2018:2902-2","markdown":"https://insights.sbomify.com/SUSE-SU-2018-2902-2/index.md","name":"SUSE-SU-2018:2902-2","record":{"aliases":[],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":[],"network_reachable":"unknown","non_default_config":false,"product_category":"SUSE SMT configuration","requires_auth":"unknown","summary":"This update addresses configuration and translation issues in yast2-smt, required for a separate SMT security fix.","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 in yast2-smt:\n\n- Explicitly mention 'Organization Credentials' (fate#321759)\n- Rearrange the SMT set-up dialog (bsc#977043)\n- Added missing translation marks (bsc#1037811)\n- Remove cron job rescheduling (bsc#1097560)\n\nThis update is a requirement for the security update for SMT. Because of that it is\ntagged as security to ensure that all users, even those that only install security updates,\ninstall it.","ecosystems":["SUSE:Linux Enterprise Server 12 SP2-BCL"],"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 yast2-smt","id":"SUSE-SU-2018:2902-2","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2018"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"SUSE:Linux Enterprise Server 12 SP2-BCL","fixed":["3.0.14-17.3.2"],"introduced":["0"],"last_affected":[],"package":"yast2-smt","purl":"pkg:rpm/suse/yast2-smt\u0026distro=SUSE%20Linux%20Enterprise%20Server%2012%20SP2-BCL","source":"SUSE-SU-2018:2902-2"}],"products":null,"published":"2018-10-18","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 addresses configuration and translation issues in yast2-smt, required for a separate SMT security fix.","url":"https://insights.sbomify.com/SUSE-SU-2018-2902-2/"}