{"answers":{"affected":"","exploited":"There is no known exploitation of SUSE-SU-2022:2547-2 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"SUSE-SU-2022:2547-2 is a vulnerability in logrotate, published on 25 Jul 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 SUSE-SU-2022:2547-2 and fix it if it is affected.\n\nWhat it is: SUSE-SU-2022:2547-2 is a vulnerability in logrotate, published on 25 Jul 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 SUSE-SU-2022:2547-2 in the wild and no public exploit code.\n\nAffected product: logrotate. 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-2022-2547-2/ (Markdown: https://insights.sbomify.com/SUSE-SU-2022-2547-2/index.md)","id":"SUSE-SU-2022:2547-2","markdown":"https://insights.sbomify.com/SUSE-SU-2022-2547-2/index.md","name":"SUSE-SU-2022:2547-2","record":{"aliases":[],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux log rotation","requires_auth":"none","summary":"Attackers can exploit improper coredump handling in SUID binaries to escalate privileges on affected Linux systems.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"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 logrotate fixes the following issues:\n\nSecurity issues fixed:\n\n- Improved coredump handing for SUID binaries (bsc#1192449).\n\nNon-security issues fixed:\n\n- Fixed 'logrotate emits unintended warning: keyword size not properly separated, found 0x3d' (bsc#1200278, bsc#1200802).","ecosystems":["openSUSE:Leap Micro 5.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":"Security update for logrotate","id":"SUSE-SU-2022:2547-2","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2022"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"openSUSE:Leap Micro 5.2","fixed":["3.13.0-150000.4.7.1"],"introduced":["0"],"last_affected":[],"package":"logrotate","purl":"pkg:rpm/opensuse/logrotate\u0026distro=openSUSE%20Leap%20Micro%205.2","source":"SUSE-SU-2022:2547-2"}],"products":null,"published":"2022-07-25","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":"Attackers can exploit improper coredump handling in SUID binaries to escalate privileges on affected Linux systems.","url":"https://insights.sbomify.com/SUSE-SU-2022-2547-2/"}