{"answers":{"affected":"","exploited":"There is no known exploitation of openSUSE-SU-2019:2607-1 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"openSUSE-SU-2019:2607-1 is a memory corruption vulnerability in openafs, published on 1 Dec 2019. It can be exploited over the network, with no action from the victim."},"fix_prompt":"Check this codebase for openSUSE-SU-2019:2607-1 and fix it if it is affected.\n\nWhat it is: openSUSE-SU-2019:2607-1 is a memory corruption vulnerability in openafs, published on 1 Dec 2019. It can be exploited over the network, with no action from the victim.\nExploitation: There is no known exploitation of openSUSE-SU-2019:2607-1 in the wild and no public exploit code.\n\nAffected product: openafs. 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-2019-2607-1/ (Markdown: https://insights.sbomify.com/openSUSE-SU-2019-2607-1/index.md)","id":"openSUSE-SU-2019:2607-1","markdown":"https://insights.sbomify.com/openSUSE-SU-2019-2607-1/index.md","name":"openSUSE-SU-2019:2607-1","record":{"aliases":[],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"OpenAFS file system","requires_auth":"unknown","summary":"OpenAFS server RPC handling flaws allow attackers to cause memory corruption, potentially leading to code execution or denial of service.","user_interaction":"not_required","vuln_class":"memory_corruption"},"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 openafs fixes the following issues:\n\nUpdate to security-release 1.8.5, adresses:\n\n* OPENAFS-SA-2019-001: Skip server OUT args on error \n* OPENAFS-SA-2019-002: Zero all server RPC args\n* OPENAFS-SA-2019-003: ubik: Avoid unlocked ubik_currentTrans deref\n\nupdate to official version 1.8.4 \n\n* support Linux-kernel 5.3\n* Avoid non-dir ENOENT errors in afs_lookup\n* fix parsing of fileservers with -vlruthresh, etc.\n* other bugfixes  \n\nupdate to pre-release 1.8.4pre2\n\n* fix builds for Linux-kernels 5.3\n\nupdate to 1.8.3\n\n- fix broken directory layout\n- allow crypt to be set/unset on startup of client\n\nupdate to pre-release 1.8.3pre1\n\n* fix builds for Linux-kernels 4.20 and 5.0 \n* other fixes, see RELNOTES-1.8.3pre1","ecosystems":["openSUSE:Leap 15.1"],"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 openafs","id":"openSUSE-SU-2019:2607-1","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2019"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"openSUSE:Leap 15.1","fixed":["1.8.5-lp151.2.3.1"],"introduced":["0"],"last_affected":[],"package":"openafs","purl":"pkg:rpm/opensuse/openafs\u0026distro=openSUSE%20Leap%2015.1","source":"openSUSE-SU-2019:2607-1"}],"products":null,"published":"2019-12-01","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":"OpenAFS server RPC handling flaws allow attackers to cause memory corruption, potentially leading to code execution or denial of service.","url":"https://insights.sbomify.com/openSUSE-SU-2019-2607-1/"}