{"answers":{"affected":"","exploited":"There is no known exploitation of SUSE-SU-2018:0409-1 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"SUSE-SU-2018:0409-1 is a vulnerability in libdb-4_5, published on 9 Feb 2018. 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-2018:0409-1 and fix it if it is affected.\n\nWhat it is: SUSE-SU-2018:0409-1 is a vulnerability in libdb-4_5, published on 9 Feb 2018. 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-2018:0409-1 in the wild and no public exploit code.\n\nAffected product: libdb-4_5. 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-0409-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2018-0409-1/index.md)","id":"SUSE-SU-2018:0409-1","markdown":"https://insights.sbomify.com/SUSE-SU-2018-0409-1/index.md","name":"SUSE-SU-2018:0409-1","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Berkeley DB library","requires_auth":"low_privilege","summary":"Local attackers can exploit symlink attacks in setuid applications to read sensitive information via the libdb-4_5 library.","user_interaction":"not_required","vuln_class":"information_disclosure"},"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 libdb-4_5 fixes the following issues:\n\n- A DB_CONFIG file in the current working directory allowed local\n  users to obtain sensitive information via a symlink attack\n  involving a setgid or setuid application using libdb-4_8. (bsc#1043886)","ecosystems":["SUSE:Linux Enterprise Server 11 SP4","SUSE:Linux Enterprise Server for SAP Applications 11 SP4","SUSE:Linux Enterprise Software Development Kit 11 SP4","SUSE:Studio Onsite 1.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 libdb-4_5","id":"SUSE-SU-2018:0409-1","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2018"},"n_packages":5,"n_references":null,"packages":[{"ecosystem":"SUSE:Linux Enterprise Server 11 SP4","fixed":["4.5.20-97.5"],"introduced":["0"],"last_affected":[],"package":"libdb-4_5","purl":"pkg:rpm/suse/libdb-4_5\u0026distro=SUSE%20Linux%20Enterprise%20Server%2011%20SP4","source":"SUSE-SU-2018:0409-1"},{"ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 11 SP4","fixed":["4.5.20-97.5"],"introduced":["0"],"last_affected":[],"package":"libdb-4_5","purl":"pkg:rpm/suse/libdb-4_5\u0026distro=SUSE%20Linux%20Enterprise%20Server%20for%20SAP%20Applications%2011%20SP4","source":"SUSE-SU-2018:0409-1"},{"ecosystem":"SUSE:Linux Enterprise Software Development Kit 11 SP4","fixed":["4.5.20-97.5"],"introduced":["0"],"last_affected":[],"package":"libdb-4_5","purl":"pkg:rpm/suse/libdb-4_5\u0026distro=SUSE%20Linux%20Enterprise%20Software%20Development%20Kit%2011%20SP4","source":"SUSE-SU-2018:0409-1"},{"ecosystem":"SUSE:Linux Enterprise Software Development Kit 11 SP4","fixed":["4.5.20-97.7"],"introduced":["0"],"last_affected":[],"package":"libdb_java-4_5","purl":"pkg:rpm/suse/libdb_java-4_5\u0026distro=SUSE%20Linux%20Enterprise%20Software%20Development%20Kit%2011%20SP4","source":"SUSE-SU-2018:0409-1"},{"ecosystem":"SUSE:Studio Onsite 1.3","fixed":["4.5.20-97.5"],"introduced":["0"],"last_affected":[],"package":"libdb-4_5","purl":"pkg:rpm/suse/libdb-4_5\u0026distro=SUSE%20Studio%20Onsite%201.3","source":"SUSE-SU-2018:0409-1"}],"products":null,"published":"2018-02-09","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":"Local attackers can exploit symlink attacks in setuid applications to read sensitive information via the libdb-4_5 library.","url":"https://insights.sbomify.com/SUSE-SU-2018-0409-1/"}